syslog spammed with "file not found" errors

[nomike]

I'm sometimes using `yt-dlp` to download videos from various websites.

It happened to me twice already, that my syslog got spammed with lines like this:

```plaintext
2025-05-07T01:19:33.098045+02:00 scrooge tracker-miner-fs-3[991717]: (tracker-extract-3:991717): Tracker-WARNING **: 01:19:33.097: Task for 'file:///home/nomike/Videos/Look%20Around%20You%20Module%200%20-%20Calcium%20%5Bx566nbi%5D.tmp.mp4' finished with error: Error when getting information for file “/home/nomike/Videos/Look Around You Module 0 - Calcium [x566nbi].tmp.mp4”: No such file or directory
2025-05-07T01:19:33.116188+02:00 scrooge tracker-miner-fs-3[991717]: (tracker-extract-3:991717): Tracker-WARNING **: 01:19:33.116: Could not get mimetype, Error when getting information for file “/home/nomike/Videos/Look Around You Module 0 - Calcium [x566nbi].tmp.mp4”: No such file or directory
```

This message repeats ~200 times per second.

My syslogs files are bloated and it costs a ton of performance:
```plaintext
$ du -h /var/log/syslog*
5,2G /var/log/syslog
7,5G /var/log/syslog.1
472M /var/log/syslog.2.gz
2,3M /var/log/syslog.3.gz
1,1G /var/log/syslog.4.gz
```

I was able to remedy this with

```bash
tracker3-reset -f /home/nomike/Videos/
killall tracker-miner-fs-3
```

and I thought that will be the end of it.

But today I noticed this again, thus I'm filing this bug.

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: tracker-miner-fs 3.7.3-1
ProcVersionSignature: Ubuntu 6.11.0-25.25-generic 6.11.11
Uname: Linux 6.11.0-25-generic x86_64
ApportVersion: 2.30.0-0ubuntu4.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 7 01:23:18 2025
InstallationDate: Installed on 2023-07-14 (663 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
SourcePackage: tracker-miners
UpgradeStatus: Upgraded to oracular on 2024-11-21 (166 days ago)

[nomike (michael-postmann)]

BTW:

I've just written a small shell-script which I'm executing as a user-cronjob once per hour, which alerts me in case this happens again:

```shell
#!/bin/bash

SYSLOG="/var/log/syslog"
MAX_GROWTH_LINES=100000 # Max allowed lines since last invocation
<email address hidden>"

# Store previous line count in a temp file
COUNT_FILE="/tmp/syslog_line_count.tmp"

if [ -f "$COUNT_FILE" ]; then
    PREV_COUNT=$(cat "$COUNT_FILE")
else
    PREV_COUNT=$(wc -l < "$SYSLOG")
    echo "$PREV_COUNT" > "$COUNT_FILE"
    exit 0
fi

CURRENT_COUNT=$(wc -l < "$SYSLOG")
GROWTH=$((CURRENT_COUNT - PREV_COUNT))

last_modified=$(date -r "$COUNT_FILE" +%s) # Get modification time in seconds
now=$(date +%s)
diff_seconds=$((now - last_modified))
human_readable=$(date -d "@$last_modified" +"%F %T") # Convert to readable datetime
time_ago=$(date -d "@$last_modified" +"%F %T was %A, %Y-%m-%d (%H:%M:%S)") # More verbose

if [ "$GROWTH" -gt "$MAX_GROWTH_LINES" ]; then
    echo "Warning: $SYSLOG grew by ${GROWTH} lines within $(date -d "@$diff_seconds" -u +"%H hours, %M minutes, %S seconds") (max allowed: ${MAX_GROWTH_LINES})" | \
    mail -s "Syslog Growth Alert" "$ALERT_EMAIL"
    notify-send -u critical "Syslog Alert" "Syslog grew by ${GROWTH} lines within $(date -d "@$diff_seconds" -u +"%H hours, %M minutes, %S seconds") (max allowed: ${MAX_GROWTH_LINES})"
fi

# Update the count file
echo "$CURRENT_COUNT" > "$COUNT_FILE"
```