[SOLVED] Tracking Center suddenly stopped working

[nerdc0re]

SOLVED!​

Hello! After I installed two PMG nodes for testing purposes the tracking center suddenly stopped working after a certain point, the GUI outputs: No data in database.

pmgversion -v
proxmox-mailgateway: 9.0.0 (API: 9.0.6/0a1e7f1cf8f3, running kernel: 6.17.9-1-pve)
pmg-api: 9.0.6
pmg-gui: 5.0.5
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.9-1-pve-signed: 6.17.9-1
proxmox-kernel-6.17: 6.17.9-1
proxmox-kernel-6.17.4-2-pve-signed: 6.17.4-2
proxmox-kernel-6.14.11-5-pve-signed: 6.14.11-5
proxmox-kernel-6.14: 6.14.11-5
proxmox-kernel-6.14.11-3-pve-signed: 6.14.11-3
clamav-daemon: 1.4.3+dfsg-1
ifupdown2: 3.3.0-1+pmx12
libarchive-perl: 3.7.4.1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-acme-plugins: 1.7.0
libpve-apiclient-perl: 3.4.2
libpve-common-perl: 9.1.7
libpve-http-server-perl: 6.0.5
libxdgmime-perl: 1.2.0
lvm2: 2.03.31-2+pmx1
pmg-docs: 9.0.6
pmg-i18n: 3.6.6
pmg-log-tracker: 3.0.1
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-spamassassin: 4.0.2-1
proxmox-widget-toolkit: 5.1.5
pve-firmware: 3.17-2
pve-xtermjs: 5.5.0-3
zfsutils-linux: 2.4.0-pve1

The logs are written in /var/log/syslog, the naming fro the log-files is standard:

/var/log# ls -lsah | grep syslog
124M -rw-r-----   1 root     adm             124M Feb 19 15:27 syslog
188M -rw-r-----   1 root     adm             188M Feb 15 00:36 syslog.1
 16M -rw-r-----   1 root     adm              16M Feb  8 00:44 syslog.2.gz
 16M -rw-r-----   1 root     adm              16M Feb  1 00:23 syslog.3.gz
 16M -rw-r-----   1 root     adm              16M Jan 25 00:41 syslog.4.gz

Up to a certain point I can retrieve the logs via WebUI/Tracking Center and via CLI pmg-log-tracker --starttime "2026-01-26 00:00:00" --from ***.

Any hint how to debug this? For me it seems like the logs are not written into the database. The administration guide did not really tell me a lot how to approach this issue. Obviously I have no real clue why these logs are not retrievable via pmg-log-tracker... I can't recall any changes on the system matching the timestamp this stopped working.

 

[nerdc0re]

Maybe someone else is going to stumble over the same issue, finally I found the reason for my issue after checking the exact logs when the tracking center was still working:

A logforward via rsyslog had stop incorporated. This stopped the matching logs from being written into syslog, hence the parser had nothing to parse. This just did not really show up immediately due to some if not exceptions in the rsyslog forward configuration.