View previous topic :: View next topic |
Author |
Message |
salfter Tux's lil' helper
Joined: 02 Jan 2003 Posts: 89
|
Posted: Wed Jul 10, 2019 5:12 pm Post subject: |
|
|
In my case, I logged into my home desktop this morning to find / was full. I eventually tracked it down to ~/.local/share/sddm/xorg-session.log, which had grown to 90 GB. I truncated it with echo -n...it freed up lots of space on disk, but the indicated length was still a long way from zero. I found that it was getting spammed with these two messages repeatedly:
Code: | org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid |
pkill baloo put an end to that nonsense. |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2034 Location: United Kingdom
|
Posted: Mon Aug 19, 2019 2:56 pm Post subject: |
|
|
salfter wrote: | In my case, I logged into my home desktop this morning to find / was full. I eventually tracked it down to ~/.local/share/sddm/xorg-session.log, which had grown to 90 GB. I truncated it with echo -n...it freed up lots of space on disk, but the indicated length was still a long way from zero. I found that it was getting spammed with these two messages repeatedly:
Code: | org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid |
pkill baloo put an end to that nonsense. |
I discovered today that ~/.xsession-errors was full of these two error messages and growing continually. Baloo seems to be a perennial source of trouble. The best thing is simply to disable it:
Code: | $ balooctl disable
$ >~/.xsession-errors |
_________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
Back to top |
|
|
Naib Watchman
Joined: 21 May 2004 Posts: 6051 Location: Removed by Neddy
|
Posted: Mon Aug 19, 2019 3:51 pm Post subject: |
|
|
Honestly this is one major oversight here... There should be some warning to the user if this logfile grows above a certain size as most of the time it isn't checked.
I might add a simple zenity check at login ( if > ... Then...) _________________
Quote: | Removed by Chiitoo |
|
|
Back to top |
|
|
salfter Tux's lil' helper
Joined: 02 Jan 2003 Posts: 89
|
Posted: Mon Aug 19, 2019 7:07 pm Post subject: |
|
|
Fitzcarraldo wrote: | salfter wrote: | In my case, I logged into my home desktop this morning to find / was full. I eventually tracked it down to ~/.local/share/sddm/xorg-session.log, which had grown to 90 GB. I truncated it with echo -n...it freed up lots of space on disk, but the indicated length was still a long way from zero. I found that it was getting spammed with these two messages repeatedly:
Code: | org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid |
pkill baloo put an end to that nonsense. |
I discovered today that ~/.xsession-errors was full of these two error messages and growing continually. Baloo seems to be a perennial source of trouble. The best thing is simply to disable it:
Code: | $ balooctl disable
$ >~/.xsession-errors |
|
I've since gone a step further, as baloo was causing other issues:
Code: | $ sudo euse -D semantic-desktop && sudo emerge -uNDv @world && sudo emerge --depclean && sudo eclean-dist --deep |
It's now gone completely. Its absence hasn't affected functionality in any way that I can detect. |
|
Back to top |
|
|
don quixada l33t
Joined: 15 May 2003 Posts: 790
|
Posted: Tue Sep 03, 2019 3:06 pm Post subject: |
|
|
I just started having these issues and after only one day I had a 262Gig .~/.local/share/sddm/xorg-session.log file.
'balooctl disable' fixed it but is this a bug that should be reported?
dq
Last edited by don quixada on Wed Oct 02, 2019 12:16 am; edited 1 time in total |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Tue Sep 03, 2019 3:11 pm Post subject: |
|
|
what does man say about balooctl and logging, lots of times there's a quiet option? (I don't run kde so have no answer)
You don't need baloo, it just keeps metadata about files on the system, similar to windows file indexing. Can speed things up (especially on slow hdd, less useful for ssd, IMO) _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21623
|
Posted: Wed Sep 04, 2019 1:27 am Post subject: |
|
|
In my opinion, it is absolutely a bug that a program would go writing gigabytes of error logs without explicit instruction from the user. |
|
Back to top |
|
|
don quixada l33t
Joined: 15 May 2003 Posts: 790
|
Posted: Wed Sep 04, 2019 2:32 am Post subject: |
|
|
Anon-E-moose wrote: | what does man say about balooctl and logging, lots of times there's a quiet option? (I don't run kde so have no answer)
You don't need baloo, it just keeps metadata about files on the system, similar to windows file indexing. Can speed things up (especially on slow hdd, less useful for ssd, IMO) |
Code: | # man balooctl
No manual entry for balooctl
# man baloo
No manual entry for baloo |
Hey BTW, I've been messing with my RAID partitions (reference here). Do you think this is why baloo went wonky? I've never had this happen before to baloo.
dq |
|
Back to top |
|
|
don quixada l33t
Joined: 15 May 2003 Posts: 790
|
Posted: Wed Oct 02, 2019 12:19 am Post subject: |
|
|
Is there a way to permanently remove/disable balooctl? I rebooted and it quickly filled up my partition again... |
|
Back to top |
|
|
ct85711 Veteran
Joined: 27 Sep 2005 Posts: 1791
|
|
Back to top |
|
|
don quixada l33t
Joined: 15 May 2003 Posts: 790
|
Posted: Thu Oct 03, 2019 1:07 am Post subject: |
|
|
Thanks, I see that script. The funny thing is that if I use that script as-is it will check every 2 days but I can guarantee my 1TB (mostly empty) partition will fill up before then!
(obviously I will change the interval in the script...) Thanks again!
dq |
|
Back to top |
|
|
mrbassie l33t
Joined: 31 May 2013 Posts: 772 Location: over here
|
Posted: Thu Oct 03, 2019 3:01 pm Post subject: |
|
|
don quixada wrote: | Is there a way to permanently remove/disable balooctl? I rebooted and it quickly filled up my partition again... |
If you want to remove baloo altogether:
Code: | kde-plasma/plasma-desktop -semantic-desktop |
in package.use. |
|
Back to top |
|
|
ct85711 Veteran
Joined: 27 Sep 2005 Posts: 1791
|
Posted: Thu Oct 03, 2019 4:05 pm Post subject: |
|
|
The link I posted also told you which config file to change (and what part), to disable the file-indexing that baloo does. Once that is disabled, baloo shouldn't be filling up your hard drive. |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2034 Location: United Kingdom
|
Posted: Fri Oct 11, 2019 6:35 pm Post subject: |
|
|
Naib wrote: | Honestly this is one major oversight here... There should be some warning to the user if this logfile grows above a certain size as most of the time it isn't checked.
I might add a simple zenity check at login ( if > ... Then...) |
In the end I used crontab Example #2 from Daniel López Azaña's 2017 blog post How to prevent the .xsession-errors file from growing to a huge size to check every 15 minutes if the file size is greater than 5 GB and if so truncates it to the last 10,000 lines:
Code: | */15 * * * * [ $(du -k .xsession-errors | awk '{ print $1 }') -gt 5000000 ] && tail -10000 /home/$(whoami)/.xsession-errors > /home/$(whoami)/.xsession-errors |
_________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21623
|
Posted: Sat Oct 12, 2019 12:17 am Post subject: |
|
|
It looks like your solution may be a bit more effective than you intended. As I read that command, your shell will truncate the output file to be empty, then you will copy the last 10000 lines of the now empty file into the file. This leaves you with a zero line file, until the runaway logger starts adding to it again. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sat Oct 12, 2019 12:48 am Post subject: |
|
|
I would do it this way
tail -10000 /home/$(whoami)/.xsession-errors > /tmp/tmpname && mv /tmp/tmpname /home/$(whoami)/.xsession-errors
With the realization, that I might lose a message or two in the process.
Or if you really don't care about the errors (which most of the time you won't) then a simple >~/.xsession-errors will suffice. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2034 Location: United Kingdom
|
Posted: Sat Oct 12, 2019 1:32 am Post subject: |
|
|
Hu wrote: | It looks like your solution may be a bit more effective than you intended. As I read that command, your shell will truncate the output file to be empty, then you will copy the last 10000 lines of the now empty file into the file. This leaves you with a zero line file, until the runaway logger starts adding to it again. |
Doh. Well spotted! Thanks. I should have actually tested it. I have changed it to use sponge (from sys-apps/moreutils) rather than specify a temporary file:
Code: | */15 * * * * [ $(du -k /home/$(whoami)/.xsession-errors | awk '{ print $1 }') -gt 5000000 ] && tail -n 10000 /home/$(whoami)/.xsession-errors | sponge /home/$(whoami)/.xsession-errors |
A quick test shows sponge does the job:
Code: | $ du -k .xsession-errors | awk '{ print $1 }'
72
$ wc -l ~/.xsession-errors
779 /home/fitzcarraldo/.xsession-errors
$ [ $(du -k /home/$(whoami)/.xsession-errors | awk '{ print $1 }') -gt 70 ] && tail -n 100 /home/$(whoami)/.xsession-errors | sponge /home/$(whoami)/.xsession-errors
$ wc -l ~/.xsession-errors
100 /home/fitzcarraldo/.xsession-errors |
_________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
Back to top |
|
|
|