Description of problem: while checking for log messages re plasma crashes, I found the log filled with tracker-extract messages. $ date Thu Sep 28 09:16:53 AM EDT 2023 $uptime 09:47:34 up 8 days, 14:34, 32 users, load average: 2.04, 1.82, 2.06 Yet, my journal logs only go back to 07:24 for 3.6GB of log files, each about 80MB... 3.6GB of logs in a mere 2 hours it NUTS! Let alone, that this volume wiped out all journal data beyond the latest 100 files. $ rpm -qa --last | grep tracker tracker-vala-3.6.0-1.mga10.noarch Wed 27 Sep 2023 05:30:59 PM EDT lib64tracker-devel-3.6.0-1.mga10.x86_64 Wed 27 Sep 2023 05:30:59 PM EDT tracker-3.6.0-1.mga10.x86_64 Wed 27 Sep 2023 05:30:58 PM EDT lib64tracker-gir3.0-3.6.0-1.mga10.x86_64 Wed 27 Sep 2023 05:30:58 PM EDT lib64tracker3.0_0-3.6.0-1.mga10.x86_64 Wed 27 Sep 2023 05:30:58 PM EDT lib64xatracker2-23.1.7-1.mga10.x86_64 Sat 09 Sep 2023 02:31:02 PM EDT Is a pretty good clue why my system & logs got swamped with (samples): --------------------------------------------- ep 28 07:21:15 tracker-extract[1984579]: Failed to update ignored file 'file:///[redacted]': Parser error at byte 0, expected one of 'base', 'prefix', 'constraint', 'load', 'clear', 'drop', 'add', 'move', 'copy', 'create', 'insert', 'delete', 'with': ‸ Sep 28 07:21:15 tracker-extract[1984579]: Could not get mimetype, Error when getting information for file “[redacted]”: No such file or directory Sep 28 07:21:15 tracker-extract[1984579]: Failed to update ignored file 'file:///[redacted]': Parser error at byte 0, expected one of 'base', 'prefix', 'constraint', 'load', 'clear', 'drop', 'add', 'move', 'copy', 'create', 'insert', 'delete', 'with': ‸ Sep 28 07:21:15 tracker-extract[1984579]: Task for 'file:///[redacted]' finished with error: Error when getting information for file “[redacted]”: No such file or directory Sep 28 07:21:15 tracker-extract[1984579]: Could not get mimetype, Error when getting information for file “[redacted]”: No such file or directory Sep 28 07:21:15 tracker-extract[1984579]: Failed to update ignored file 'file:///[redacted]': Parser error at byte 0, expected one of 'base', 'prefix', 'constraint', 'load', 'clear', 'drop', 'add', 'move', 'copy', 'create', 'insert', 'delete', 'with': ------------------------------------------------ Tried to uninstall tracker; but it would have uninstalled 753(!!!) other packages including 301 lib64* packages; at least uninstalling tracker-miners got my journal logging back down to a reasonable pace. # du -s / 33T / on 49TB (2TB + 4TB NVMe drives and 2TB, 17TB, 4x 6TB platters) So, NO, installing tracker on a server is not a good idea: $ uname -a Linux pf.pfortin.com 6.5.3-server-1.mga10 #1 SMP PREEMPT_DYNAMIC Sat Sep 16 00:04:28 UTC 2023 x86_64 GNU/Linux The user should be given the opportunity to decide on that sort of package. Even with 33T of files, I know what I have and where they are; no need for any trackers. I occasionally use "find" which never has to run more than a few seconds because, on a server, data is more organized than on a desktop. Version-Release number of selected component (if applicable): How reproducible: not sure. tracker should NOT be auto-installed on a server. Steps to Reproduce: 1. no step was used by me; other than applying updates. 2. 3. I hope there are no other "cool" packages burning cycles or storage that I wasn't first asked if it's OK to install... Oh... is there any valid reason that trying to uninstall tracker would flag 753 other packages for removal -- my guess is that could destroy a server; attaching list of packages it said need to be removed... Rating Major; considered Critical which reads "or causes you to lose data" -- I lost MUCH journal data that I was going to use to show that plasma crashes excessively...
Created attachment 14012 [details] list of 753 packages tracker wanted to also uninstall
What does # systemctl status|grep [t]racker say?
CC: (none) => zen25000
Nothing. tracker-miners is uninstalled.
(In reply to Pierre Fortin from comment #0) > > Oh... is there any valid reason that trying to uninstall tracker would flag > 753 other packages for removal -- my guess is that could destroy a server; > attaching list of packages it said need to be removed... > $ urpmq --whatrequires-recursive tracker | wc -l 2967 Since you're using Plasma... doesn't KDE'S Baloo do the same as tracker? Although intended to be desktop neutral, tracker is a Gnome tool. (In reply to Barry Jackson from comment #2) > What does > # systemctl status|grep [t]racker > say? (In reply to Pierre Fortin from comment #3) > Nothing. tracker-miners is uninstalled. I'll leave this report open in case someone else hits the same issue. But because you can't provide us with more information, I'll set the Status to UNCONFIRMED @ Anyone hitting this issue: Please provide us with more information. You might also want to look whether it is a known issue upstream https://gitlab.gnome.org/GNOME/tracker-miners/-/issues @ anyone hitting this issue: Please don't uninstall tracker-miners, but first try to supply us with
Ever confirmed: 1 => 0CC: (none) => marja11Status: NEW => UNCONFIRMED
$ urpmq --whatrequires-recursive tracker | wc -l 3006 $ ls -1 -R / | wc -l 4987525 Nearly 5M files (33TB) may be too much for tracker... A good start to figuring out what tracker was doing would be to understand the error messages that filled the journal. >Although intended to be desktop neutral, tracker is a Gnome tool. I've never used Gnome on this system. My opinion is that this type of tool should be the user's choice to install/use. tracker was not previously installed (that I know of), was it installed and/or enabled as part of an update?
FWIW I looked at my own M9 multi-desktop system. It has lots of tracker pkgs: lib64tracker3.0_0-3.5.3-1.mga9 lib64tracker-gir3.0-3.5.3-1.mga9 lib64xatracker2-23.1.7-1.mga9 tracker-3.5.3-1.mga9 tracker-miners-3.5.2-1.mga9 but happily it does not seem to be running: $ ps ax | grep tracker 8042 pts/0 S+ 0:00 grep --color tracker $ [the O/P line is for the grep command]
Pierre, is this still an issue?
CC: (none) => lewyssmith
No, I got rid of tracker; not the kind of tool I'm interested in.
OK, closing. If anyone else is using Tracker, they will complain similarly and it can be reopened.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => INVALID