On 2024-11-15 09:17, Robert Webb via openSUSE Users wrote:
On Fri, 15 Nov 2024 01:24:27 +0100, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-11-14 15:11, Carlos E. R. wrote:
...
I had to kill the tracker-extract process.
The process gets restarted a while later and keeps complaining that the files were deleted:
The following errors, they are for the files that you deleted, right? So there must be an index somewhere telling Firefox to expect those files to exist. Maybe that is in the Firefox cache, and you could try deleting the cache (after quitting Firefox). Or instead, you could try putting the files back (from your tar archive) that you so "rudely" took from Firefox. ;-)
No, those files do not affect firefox. That's a single file originally downloaded by firefox, that somehow expanded into many. It is the download directory, not the cache directory. I downloaded the single file "cadenaser_hoyporhoy_20240919_100000_110000.mp3" then used audacity to extract a chunk out of it into another file. I'm guessing the directory "cadenaser_hoyporhoy_20240919_100000_110000_data/" was created by audacity. It is tracker, a search indexer, which has problems. It is not related at all to firefox, except in that it searches inside {home}. It expects to find audio files and finds text, so wrong format. It is not the first time I have problems with tracker and it spamming the logs: cer@Telcontar:~/Download/Firefox_downloads> l -lhtr /var/log/ | tail -rw-r----- 1 root root 6,7M Nov 15 12:48 pruned -rw-r----- 1 root root 68K Nov 15 12:48 mail.info -rw-r----- 1 root root 68K Nov 15 12:48 mail -rw-r----- 1 root root 870K Nov 15 13:01 snapper.log -rw-r----- 1 root root 2,1G Nov 15 13:14 warn -rw-r----- 1 root root 6,7M Nov 15 13:23 pruned.warn -rw-r--r-- 1 root root 54M Nov 15 13:24 xinetd.log -rw-r--r-- 1 root root 48K Nov 15 13:29 Xorg.0.log -rw-r----- 1 root root 2,1G Nov 15 13:30 messages <= -rw-r----- 1 root root 2,1G Nov 15 13:30 allmessages cer@Telcontar:~/Download/Firefox_downloads> Still not rotated, I see, despite the computer being up at 00 hours. Telcontar:~ # systemctl status logrotate ○ logrotate.service - Rotate log files Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static) Active: inactive (dead) since Fri 2024-11-15 00:03:56 CET; 13h ago TriggeredBy: ● logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) Process: 10737 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=0/SUCCESS) Main PID: 10737 (code=exited, status=0/SUCCESS) Nov 15 00:00:01 Telcontar systemd[1]: Starting Rotate log files... Nov 15 00:03:56 Telcontar systemd[1]: logrotate.service: Deactivated successfully. Nov 15 00:03:56 Telcontar systemd[1]: Finished Rotate log files. Telcontar:~ # Huh, rotate did run this night, but it did nothing with those two huge files. <3.6> 2024-11-15T00:03:55.423108+01:00 Telcontar systemd 1 - - Reloading System Logging Service... <3.6> 2024-11-15T00:03:55.424822+01:00 Telcontar systemd 1 - - Reloaded System Logging Service. <3.6> 2024-11-15T00:03:56.467781+01:00 Telcontar systemd 1 - - logrotate.service: Deactivated successfully. <3.6> 2024-11-15T00:03:56.468518+01:00 Telcontar systemd 1 - - Finished Rotate log files. Correction, the files were in fact rotated, they start logging at zero hours: <5.6> 2024-11-15T00:00:01.994722+01:00 Telcontar rsyslogd - - - message repeated 13 times: [-- MARK --] But as messages is 6407599 lines long, the spamming continued. -rw-r----- 1 root root 702K Nov 13 23:56 /var/log/mail-20241114.xz -rw-r----- 1 root root 1,5M Nov 14 00:00 /var/log/warn-20241114.xz -rw-r----- 1 root root 1,8M Nov 14 00:00 /var/log/messages-20241114.xz -rw-r----- 1 root root 2,4M Nov 14 00:00 /var/log/allmessages-20241114.xz -rw-r----- 1 root root 17M Nov 14 20:24 /var/log/warn-20241115.xz -rw-r----- 1 root root 17M Nov 15 00:00 /var/log/messages-20241115.xz -rw-r----- 1 root root 17M Nov 15 00:02 /var/log/allmessages-20241115.xz messages-20241115.xz is just 17M big, yet contains 3633030 lines. That compression ability is amazing! I think I might write a syslog rule to purge these tracker entries to a separate file. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)