Tracking Center says "No data in database"

[mcoa]

Hi guys,
I working with PMG 9.0.1 in cluster node (antispam01 master - antispam02 and antispam03 slaves) and have problem with tracking center and search old data. For example, when try search via "tracking center" old email (November month) the result is empty and say "No data in database" (attached screenshot for this).





But the sender and input email are ok in log:

2025-11-25T09:00:20.355892-03:00 antispam03 postfix/smtpd[580213]: 56D41A7779: client=mail-yx1-f50.google.com[74.125.224.50]
2025-11-25T09:00:20.357358-03:00 antispam03 postfix/cleanup[574453]: 56D41A7779: message-id=<CAHdRGOVUw_JHh5pPTuv+9BW+g=PsGJD51f_+V9M6DYOxSYUVaQ@mail.gmail.com>
2025-11-25T09:00:20.359369-03:00 antispam03 postfix/qmgr[30848]: 56D41A7779: from=<ignacio.hormazabal@external.com>, size=7381, nrcpt=1 (queue active)
2025-11-25T09:00:22.134146-03:00 antispam03 postfix/lmtp[574655]: 56D41A7779: to=<remates@mydomain.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.6, delays=0.78/0/0.09/1.7, dsn=2.5.0, status=sent (250 2.5.0 OK (A777C69259A546E72C))
2025-11-25T09:00:22.135044-03:00 antispam03 postfix/qmgr[30848]: 56D41A7779: removed
2025-11-25T09:00:22.134146-03:00 antispam03 postfix/lmtp[574655]: 56D41A7779: to=<remates@mydomain.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.6, delays=0.78/0/0.09/1.7, dsn=2.5.0, status=sent (250 2.5.0 OK (A777C69259A546E72C))
2025-11-25T09:00:22.135044-03:00 antispam03 postfix/qmgr[30848]: 56D41A7779: removed

My syslog are:

root@antispam01:~# cat /etc/logrotate.d/rsyslog

/var/log/syslog
/var/log/mail.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/cron.log

{
    rotate 900
    daily
    dateext
    missingok
    notifempty
    compress
    delaycompress
    sharedscripts
    postrotate
        /usr/lib/rsyslog/rsyslog-rotate
    endscript

}

The hourly and date sync

root@antispam01:~# for a in `cat ip`; do echo $a; ssh $a 'date' ;done
antispam01
Fri Jan  9 08:27:47 AM -03 2026

antispam02
Fri Jan  9 08:27:48 AM -03 2026

antispam03
Fri Jan  9 08:27:48 AM -03 2026
root@antispam01:~#

root@antispam01:~# ls /var/log/syslog-*
/var/log/syslog-20251029.gz  /var/log/syslog-20251117.gz  /var/log/syslog-20251206.gz  /var/log/syslog-20251225.gz
/var/log/syslog-20251030.gz  /var/log/syslog-20251118.gz  /var/log/syslog-20251207.gz  /var/log/syslog-20251226.gz
/var/log/syslog-20251031.gz  /var/log/syslog-20251119.gz  /var/log/syslog-20251208.gz  /var/log/syslog-20251227.gz
/var/log/syslog-20251101.gz  /var/log/syslog-20251120.gz  /var/log/syslog-20251209.gz  /var/log/syslog-20251228.gz
/var/log/syslog-20251102.gz  /var/log/syslog-20251121.gz  /var/log/syslog-20251210.gz  /var/log/syslog-20251229.gz
/var/log/syslog-20251103.gz  /var/log/syslog-20251122.gz  /var/log/syslog-20251211.gz  /var/log/syslog-20251230.gz
/var/log/syslog-20251104.gz  /var/log/syslog-20251123.gz  /var/log/syslog-20251212.gz  /var/log/syslog-20251231.gz
/var/log/syslog-20251105.gz  /var/log/syslog-20251124.gz  /var/log/syslog-20251213.gz  /var/log/syslog-20260101.gz
/var/log/syslog-20251106.gz  /var/log/syslog-20251125.gz  /var/log/syslog-20251214.gz  /var/log/syslog-20260102.gz
/var/log/syslog-20251107.gz  /var/log/syslog-20251126.gz  /var/log/syslog-20251215.gz  /var/log/syslog-20260103.gz
/var/log/syslog-20251108.gz  /var/log/syslog-20251127.gz  /var/log/syslog-20251216.gz  /var/log/syslog-20260104.gz
/var/log/syslog-20251109.gz  /var/log/syslog-20251128.gz  /var/log/syslog-20251217.gz  /var/log/syslog-20260105.gz
/var/log/syslog-20251110.gz  /var/log/syslog-20251129.gz  /var/log/syslog-20251218.gz  /var/log/syslog-20260106.gz
/var/log/syslog-20251111.gz  /var/log/syslog-20251130.gz  /var/log/syslog-20251219.gz  /var/log/syslog-20260107.gz
/var/log/syslog-20251112.gz  /var/log/syslog-20251201.gz  /var/log/syslog-20251220.gz  /var/log/syslog-20260108.gz
/var/log/syslog-20251113.gz  /var/log/syslog-20251202.gz  /var/log/syslog-20251221.gz  /var/log/syslog-20260109
/var/log/syslog-20251114.gz  /var/log/syslog-20251203.gz  /var/log/syslog-20251222.gz
/var/log/syslog-20251115.gz  /var/log/syslog-20251204.gz  /var/log/syslog-20251223.gz
/var/log/syslog-20251116.gz  /var/log/syslog-20251205.gz  /var/log/syslog-20251224.gz
root@antispam01:~#

Can you helpme?

Thanks.

 

[mcoa]

Hello,
any help, please.

Thanks

 

[Stoiko Ivanov]

root@antispam01:~# ls /var/log/syslog-* /var/log/syslog-20251029.gz /var/log/syslog-20251117.gz /var/log/syslog-20251206.gz /var/log/syslog-20251225.gz

the rotated syslog files have the wrong filenames - the log-tracker (which is the tool that reads, and parses the logs) has a hard-coded list it looks through:
https://git.proxmox.com/?p=pmg-log-...f5d3b3a025f78dd572f91a5a2d5a8e5;hb=HEAD#l2120
these are the only files that are considered.

-> Adapt your logrotate-config (I guess - remove the dateext...)

I hope this helps!

 

[mcoa]

the rotated syslog files have the wrong filenames - the log-tracker (which is the tool that reads, and parses the logs) has a hard-coded list it looks through:
https://git.proxmox.com/?p=pmg-log-...f5d3b3a025f78dd572f91a5a2d5a8e5;hb=HEAD#l2120
these are the only files that are considered.

-> Adapt your logrotate-config (I guess - remove the dateext...)

I hope this helps!

Hi Stoiko , yes the problem was the rotation name. Thks for your help.

 

[julienmore]

C’est un piège assez courant avec PMG, surtout dans des configurations en cluster. Le point clé est que le Tracking Center ne consulte pas les fichiers syslog bruts. Il interroge la base de données PMG (pmg-log / pmg-smtp-filter), qui ne conserve les données que selon la politique de rétention de la base, et non selon logrotate.

Tes journaux existent clairement sur le disque, mais si la base https://juliuss.fr/ de données des logs PMG a été purgée, reconstruite ou n’a jamais été correctement alimentée sur le nœud maître, le Tracking Center affichera « No data in database ». En environnement cluster, seule la base du maître est interrogée, et les nœuds esclaves ne réinjectent pas automatiquement les données historiques.

Vérifie Configuration → Mail Proxy → Log Database et confirme les paramètres de rétention. Vérifie aussi que les services pmg-log fonctionnaient bien en novembre. Les anciennes données présentes dans syslog ne peuvent pas être réimportées automatiquement.

En résumé : les logs sont là, mais pas les entrées dans la base de données. Ajuste la rétention pour l’avenir, mais les données de traçage passées sont très probablement perdues.