Tracking Center says "No data in database"

M

mcoa

Renowned Member
May 10, 2012
9
0
66
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).



Captura de pantalla 2026-01-09 a la(s) 08.39.14.png

But the sender and input email are ok in log:

Code: 
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:

Code: 
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

Code: 
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:~#

Code: 
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 said:
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
Click to expand...
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!
 
  • Like
Reactions: mcoa
This is a fairly common PMG gotcha, especially in clustered setups. The key point is that the Tracking Center does not search raw syslog files. It queries the PMG database (pmg-log / pmg-smtp-filter) which only retains data according to the database retention policy, not logrotate.

Your logs clearly exist on disk, but if the PMG log database was pruned, rebuilt, or never populated correctly on the master, Tracking Center will return “No data in database”. In clusters, only the master’s database is queried, and slaves don’t automatically backfill historical data.

Check Configuration → Mail Proxy → Log Database and verify retention settings. Also confirm pmg-log services were running back in November. Old data in syslog cannot be re-imported automatically.

In short: logs are there, database entries aren’t. Adjust retention going forward, but past tracking data is likely gone.
 
You must log in or register to reply here.
Top Bottom