Hi guys.
Do you see in your systems 'tracker-miner-fs-3' high CPU use and 'journalctl' shows constant repetition of: ... tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE tracker-miner-fs-3.service: Failed with result 'exit-code'. Failed to start tracker-miner-fs-3.service - Tracker file system data miner. tracker-miner-fs-3.service: Consumed 3.627s CPU time. tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 56. Stopped tracker-miner-fs-3.service - Tracker file system data miner. tracker-miner-fs-3.service: Consumed 3.627s CPU time. Starting tracker-miner-fs-3.service - Tracker file system data miner... ...
I wonder if this could be recent updates and if making it a BZ also is valid.
thanks, L.
On Fri, 22 Jul 2022 06:47:33 +0100 lejeczek via users users@lists.fedoraproject.org wrote:
Hi guys.
Do you see in your systems 'tracker-miner-fs-3' high CPU use and 'journalctl' shows constant repetition of: ... tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE tracker-miner-fs-3.service: Failed with result 'exit-code'. Failed to start tracker-miner-fs-3.service - Tracker file system data miner. tracker-miner-fs-3.service: Consumed 3.627s CPU time. tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 56. Stopped tracker-miner-fs-3.service - Tracker file system data miner. tracker-miner-fs-3.service: Consumed 3.627s CPU time. Starting tracker-miner-fs-3.service - Tracker file system data miner... ...
No, in rawhide, tracker-miners-3.4.0~alpha-1.fc37.x86_64
I wonder if this could be recent updates and if making it a BZ also is valid.
It looks like it is failing on your system for some reason. In the man page there is a way to run it manually in debug mode by passing it options. Maybe you should try some of those, man tracker-miner-fs to see if why it is failing before opening a bugzilla.