Tracker center is empty.

akong

Well-Known Member
Oct 15, 2018
87
1
48
46
Hello,
I installed mail gateway on debian 10.But it's can't show mail log.I make sure mail log have send or received data.But it's empty on tracker center.
How to check it?
pmgversion like follow:
root@pmg:~# pmgversion -v
proxmox-mailgateway: 6.2-2 (API: 6.3-5/40d25ec2, running kernel: 5.4.78-2-pve)
pmg-api: 6.3-5
pmg-gui: 2.3-1
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
clamav-daemon: 0.102.4+dfsg-0+deb10u1
libarchive-perl: 3.3.3-1
libjs-extjs: 6.0.1-10
libjs-framework7: 4.4.7-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-http-server-perl: 3.1-1
libxdgmime-perl: 0.01-5
lvm2: not correctly installed
pmg-docs: 6.3-1
pmg-log-tracker: 2.1.8-1
postgresql-11: 11.10-0+deb10u1
proxmox-mini-journalreader: 1.1-1
proxmox-spamassassin: 3.4.4-3
proxmox-widget-toolkit: 2.4-3
pve-firmware: 3.1-3
pve-xtermjs: 4.7.0-3
 
Last edited:
the pmg-log-tracker (which gathers the data for the tracking center) uses /var/log/syslog (and the rotated logs /var/log/syslog.1 /var/log/syslog.*.gz) to gather its information.

* Does your syslog contain all logs from the mail-system?
* maybe the default time filter (roughly 1 hour) is too restricted - set the start time to a timeframe where you are sure that you have got mails
* did you change anything about the syslog configuration? (pmg-log-tracker is quite senstive to the format)

if this does not help - please post parts of your syslog where mails were received
 
This is my syslog.
Jan 14 17:26:39 pmg systemd[1]: Reloading.
Jan 14 17:26:39 pmg systemd[1]: getty@tty1.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Jan 14 17:26:39 pmg systemd[1]: serial-getty@ttyS0.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Jan 14 17:26:39 pmg systemd[1]: Reloading.
Jan 14 17:26:39 pmg systemd[1]: Reloading.
Jan 14 17:26:43 pmg systemd[1]: Reloading.
Jan 14 17:26:44 pmg systemd[1]: pmg-daily.timer: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Daily Proxmox Mail Gateway activities.
Jan 14 17:26:44 pmg systemd[1]: Stopping Daily Proxmox Mail Gateway activities.
Jan 14 17:26:44 pmg systemd[1]: Started Daily Proxmox Mail Gateway activities.
Jan 14 17:26:44 pmg systemd[1]: pmg-hourly.timer: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Hourly Proxmox Mail Gateway activities.
Jan 14 17:26:44 pmg systemd[1]: Stopping Hourly Proxmox Mail Gateway activities.
Jan 14 17:26:44 pmg systemd[1]: Started Hourly Proxmox Mail Gateway activities.
Jan 14 17:26:44 pmg systemd[1]: pmgreport.timer: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Send Daily System Report Mail.
Jan 14 17:26:44 pmg systemd[1]: Stopping Send Daily System Report Mail.
Jan 14 17:26:44 pmg systemd[1]: Started Send Daily System Report Mail.
Jan 14 17:26:44 pmg systemd[1]: pmgspamreport.timer: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Send Daily Spam Report Mails.
Jan 14 17:26:44 pmg systemd[1]: Stopping Send Daily Spam Report Mails.
Jan 14 17:26:44 pmg systemd[1]: Started Send Daily Spam Report Mails.
Jan 14 17:26:44 pmg systemd[1]: Reloading.
Jan 14 17:26:44 pmg systemd[1]: pmgsync.service: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Sync Proxmox Configuration.
Jan 14 17:26:44 pmg systemd[1]: Stopping Sync Proxmox Configuration...
Jan 14 17:26:44 pmg systemd[1]: Starting Sync Proxmox Configuration...
Jan 14 17:26:44 pmg systemd[1]: pmgnetcommit.service: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Commit Proxmox network changes.
Jan 14 17:26:44 pmg systemd[1]: Stopping Commit Proxmox network changes...
Jan 14 17:26:44 pmg systemd[1]: Starting Commit Proxmox network changes...
Jan 14 17:26:44 pmg systemd[1]: pmgbanner.service: Succeeded.
Jan 14 17:26:44 pmg systemd[1]: Stopped Proxmox Mail Gateway Login Banner.
Jan 14 17:26:44 pmg systemd[1]: Stopping Proxmox Mail Gateway Login Banner...
Jan 14 17:26:44 pmg systemd[1]: Starting Proxmox Mail Gateway Login Banner...
Jan 14 17:26:44 pmg mv[1566]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory
Jan 14 17:26:44 pmg systemd[1]: Started Commit Proxmox network changes.
Jan 14 17:26:44 pmg systemd[1]: Started Proxmox Mail Gateway Login Banner.
Jan 14 17:26:44 pmg pmgdb[1565]: Analyzing/Upgrading existing Databases...done
Jan 14 17:26:46 pmg systemd[1]: Started Sync Proxmox Configuration.
Jan 14 17:26:46 pmg systemd[1]: Reloading.
Jan 14 17:26:46 pmg systemd[1]: Stopping Proxmox SMTP Filter Daemon...
Jan 14 17:26:46 pmg systemd[1]: Condition check resulted in Proxmox Mail Gateway Database Mirror Daemon being skipped.
Jan 14 17:26:46 pmg systemd[1]: Stopping Proxmox Mail Gateway Policy Daemon...
Jan 14 17:26:46 pmg systemd[1]: Condition check resulted in Proxmox Mail Gateway Cluster Tunnel Daemon being skipped.
Jan 14 17:26:46 pmg pmgpolicy[1063]: 2021/01/14-17:26:46 Server closing!
Jan 14 17:26:46 pmg pmg-smtp-filter[1074]: 2021/01/14-17:26:46 Server closing!
Jan 14 17:26:46 pmg systemd[1]: pmgpolicy.service: Succeeded.
Jan 14 17:26:46 pmg systemd[1]: Stopped Proxmox Mail Gateway Policy Daemon.
Jan 14 17:26:46 pmg systemd[1]: Starting Proxmox Mail Gateway Policy Daemon...
Jan 14 17:26:46 pmg systemd[1]: pmg-smtp-filter.service: Succeeded.
Jan 14 17:26:46 pmg systemd[1]: Stopped Proxmox SMTP Filter Daemon.
Jan 14 17:26:46 pmg systemd[1]: Starting Proxmox SMTP Filter Daemon...
Jan 14 17:26:47 pmg pmgpolicy[1760]: Process Backgrounded
Jan 14 17:26:47 pmg pmgpolicy[1760]: 2021/01/14-17:26:47 main (type Net::Server::PreForkSimple) starting! pid(1760)
Jan 14 17:26:47 pmg pmgpolicy[1760]: Binding to TCP port 10022 on host 127.0.0.1 with IPv4
Jan 14 17:26:47 pmg pmgpolicy[1760]: Group Not Defined. Defaulting to EGID '0'
Jan 14 17:26:47 pmg pmgpolicy[1760]: User Not Defined. Defaulting to EUID '0'
Jan 14 17:26:47 pmg pmgpolicy[1760]: Setting up serialization via flock
Jan 14 17:26:47 pmg pmgpolicy[1760]: Policy daemon (re)started
Jan 14 17:26:47 pmg pmgpolicy[1760]: Beginning prefork (5 processes)
Jan 14 17:26:47 pmg pmgpolicy[1760]: Starting "5" children
Jan 14 17:26:47 pmg systemd[1]: Started Proxmox Mail Gateway Policy Daemon.
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: Process Backgrounded
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: 2021/01/14-17:26:47 main (type Net::Server::PreFork) starting! pid(1771)
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: Binding to TCP port 10023 on host 127.0.0.1 with IPv4
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: Binding to TCP port 10024 on host 127.0.0.1 with IPv4
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: Group Not Defined. Defaulting to EGID '0'
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: User Not Defined. Defaulting to EUID '0'
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: Setting up serialization via flock
Jan 14 17:26:47 pmg pmg-smtp-filter[1771]: Filter daemon (re)started (max. 32 processes)
Jan 14 17:26:47 pmg systemd[1]: Started Proxmox SMTP Filter Daemon.
Jan 14 17:26:47 pmg systemd[1]: Reloading Proxmox Mail Gateway API Daemon.
Jan 14 17:26:48 pmg pmgdaemon[1775]: send HUP to 1079
Jan 14 17:26:48 pmg pmgdaemon[1079]: received signal HUP
Jan 14 17:26:48 pmg pmgdaemon[1079]: server closing
Jan 14 17:26:48 pmg pmgdaemon[1079]: server shutdown (restart)
Jan 14 17:26:48 pmg systemd[1]: Reloaded Proxmox Mail Gateway API Daemon.
Jan 14 17:26:48 pmg systemd[1]: Reloading Proxmox Mail Gateway API.
Jan 14 17:26:49 pmg pmgproxy[1781]: send HUP to 1086
Jan 14 17:26:49 pmg pmgproxy[1086]: received signal HUP
Jan 14 17:26:49 pmg pmgproxy[1086]: server closing
Jan 14 17:26:49 pmg pmgproxy[1086]: server shutdown (restart)
Jan 14 17:26:49 pmg systemd[1]: Reloaded Proxmox Mail Gateway API.
Jan 14 17:26:49 pmg pmgdaemon[1079]: restarting server
Jan 14 17:26:49 pmg pmgdaemon[1079]: starting 3 worker(s)
Jan 14 17:26:49 pmg pmgdaemon[1079]: worker 1788 started
Jan 14 17:26:49 pmg pmgdaemon[1079]: worker 1789 started
Jan 14 17:26:49 pmg pmgdaemon[1079]: worker 1790 started
Jan 14 17:26:49 pmg pmg-smtp-filter[1771]: Beginning prefork (2 processes)
Jan 14 17:26:49 pmg pmg-smtp-filter[1771]: Starting "2" children
Jan 14 17:26:50 pmg pmgproxy[1086]: restarting server
Jan 14 17:26:50 pmg pmgproxy[1086]: starting 3 worker(s)
Jan 14 17:26:50 pmg pmgproxy[1086]: worker 1864 started
Jan 14 17:26:50 pmg pmgproxy[1086]: worker 1865 started
Jan 14 17:26:50 pmg pmgproxy[1086]: worker 1866 started
Jan 14 17:26:54 pmg pmgdaemon[1082]: worker exit
Jan 14 17:26:54 pmg pmgdaemon[1079]: worker 1080 finished
Jan 14 17:26:54 pmg pmgdaemon[1079]: worker 1081 finished
Jan 14 17:26:54 pmg pmgdaemon[1079]: worker 1082 finished
Jan 14 17:26:55 pmg pmgproxy[1089]: worker exit
Jan 14 17:26:55 pmg pmgproxy[1087]: worker exit
Jan 14 17:26:55 pmg pmgproxy[1086]: worker 1089 finished
Jan 14 17:26:55 pmg pmgproxy[1086]: worker 1088 finished
Jan 14 17:26:55 pmg pmgproxy[1086]: worker 1087 finished
Jan 14 17:26:56 pmg pmgdaemon[1868]: got inotify poll request in wrong process - disabling inotify
Jan 14 17:26:57 pmg pmgproxy[1869]: got inotify poll request in wrong process - disabling inotify
Jan 14 17:26:57 pmg pmgdaemon[1868]: worker exit
Jan 14 17:26:59 pmg pmgproxy[1869]: worker exit
Jan 14 17:27:10 pmg postfix/postscreen[1871]: CONNECT from [220.130.148.52]:16167 to [172.20.35.55]:25
Jan 14 17:27:10 pmg postfix/postscreen[1871]: PASS OLD [220.130.148.52]:16167
Jan 14 17:27:10 pmg postfix/smtpd[1874]: connect from tw.linguitronics.com[220.130.148.52]
Jan 14 17:27:10 pmg pmgpolicy[1764]: reloading configuration Proxmox_ruledb
Jan 14 17:27:10 pmg pmgpolicy[1764]: SPF says pass
Jan 14 17:27:10 pmg postfix/smtpd[1874]: DEC421003E6: client=tw.linguitronics.com[220.130.148.52]
Jan 14 17:27:11 pmg postfix/cleanup[1880]: DEC421003E6: message-id=<e2c1b272-115e-99e8-51ca-56977711b411@linguitronics.com>
Jan 14 17:27:11 pmg postfix/qmgr[1060]: DEC421003E6: from=<akong@linguitronics.com>, size=94798, nrcpt=1 (queue active)
Jan 14 17:27:11 pmg postfix/smtpd[1874]: disconnect from tw.linguitronics.com[220.130.148.52] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jan 14 17:27:11 pmg pmg-smtp-filter[1796]: 2021/01/14-17:27:11 CONNECT TCP Peer: "[127.0.0.1]:52460" Local: "[127.0.0.1]:10024"
Jan 14 17:27:11 pmg pmg-smtp-filter[1796]: 10043D60000E6F30624: new mail message-id=<e2c1b272-115e-99e8-51ca-56977711b411@linguitronics.com>#012
Jan 14 17:27:12 pmg pmg-smtp-filter[1796]: 10043D60000E6F30624: SA score=0/5 time=1.721 bayes=undefined autolearn=ham autolearn_force=no hits=DKIM_SIGNED(0.1),DKIM_VALID(-0.1),DKIM_VALID_AU(-0.1),DKIM_VALID_EF(-0.1),FILL_THIS_FORM(0.001),HTML_FONT_FACE_BAD(0.001),HTML_IMAGE_ONLY_28(0.726),HTML_MESSAGE(0.001),RCVD_IN_DNSWL_MED(-2.3),SPF_HELO_NONE(0.001),SPF_PASS(-0.001),URIBL_BLOCKED(0.001)
Jan 14 17:27:12 pmg postfix/smtpd[1885]: connect from localhost[127.0.0.1]
Jan 14 17:27:12 pmg postfix/smtpd[1885]: E981A100BA8: client=localhost[127.0.0.1], orig_client=tw.linguitronics.com[220.130.148.52]
Jan 14 17:27:12 pmg postfix/cleanup[1880]: E981A100BA8: message-id=<e2c1b272-115e-99e8-51ca-56977711b411@linguitronics.com>
Jan 14 17:27:12 pmg postfix/qmgr[1060]: E981A100BA8: from=<akong@linguitronics.com>, size=96077, nrcpt=1 (queue active)
Jan 14 17:27:12 pmg pmg-smtp-filter[1796]: 10043D60000E6F30624: accept mail to <akong@flywaycdn.com> (E981A100BA8) (rule: default-accept)
Jan 14 17:27:12 pmg postfix/smtpd[1885]: disconnect from localhost[127.0.0.1] ehlo=1 xforward=1 mail=1 rcpt=1 data=1 commands=5
Jan 14 17:27:12 pmg pmg-smtp-filter[1796]: 10043D60000E6F30624: processing time: 1.763 seconds (1.721, 0.008, 0)
Jan 14 17:27:12 pmg postfix/lmtp[1881]: DEC421003E6: to=<akong@flywaycdn.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.1, delays=0.34/0.01/0/1.8, dsn=2.5.0, status=sent (250 2.5.0 OK (10043D60000E6F30624))
Jan 14 17:27:12 pmg postfix/qmgr[1060]: DEC421003E6: removed
Jan 14 17:27:13 pmg postfix/smtp[1886]: E981A100BA8: to=<akong@flywaycdn.com>, relay=172.20.35.54[172.20.35.54]:25, delay=0.05, delays=0.01/0.01/0.02/0.01, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 00E48C1D26)
Jan 14 17:27:13 pmg postfix/qmgr[1060]: E981A100BA8: removed
Jan 14 17:27:22 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:27:23 pmg pmg-smtp-filter[1771]: end database maintainance (123 ms)
Jan 14 17:28:57 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:28:57 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:29:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:29:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:30:31 pmg postfix/anvil[1876]: statistics: max connection rate 1/60s for (smtpd:220.130.148.52) at Jan 14 17:27:10
Jan 14 17:30:31 pmg postfix/anvil[1876]: statistics: max connection count 1 for (smtpd:220.130.148.52) at Jan 14 17:27:10
Jan 14 17:30:31 pmg postfix/anvil[1876]: statistics: max cache size 1 at Jan 14 17:27:10
Jan 14 17:31:07 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:31:07 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:31:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:31:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:33:17 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:33:17 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:33:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:33:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:35:01 pmg CRON[1949]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 14 17:35:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:35:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:35:27 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:35:27 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:36:38 pmg pmgdaemon[1790]: successful auth for user 'root@pam'
Jan 14 17:37:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:37:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:37:28 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:37:28 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:38:38 pmg systemd[1]: Starting Cleanup of Temporary Directories...
Jan 14 17:38:38 pmg systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jan 14 17:38:38 pmg systemd[1]: Started Cleanup of Temporary Directories.
Jan 14 17:39:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:39:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:39:38 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:39:38 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:41:23 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:41:23 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:41:48 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:41:48 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:43:24 pmg pmg-smtp-filter[1771]: starting database maintainance
Jan 14 17:43:24 pmg pmg-smtp-filter[1771]: end database maintainance (4 ms)
Jan 14 17:43:43 pmg systemd[1]: Started Session 5 of user root.
Jan 14 17:43:58 pmg pmgpolicy[1760]: starting policy database maintainance (greylist, rbl)
Jan 14 17:43:58 pmg pmgpolicy[1760]: end policy database maintainance (8 ms, 1 ms)
Jan 14 17:44:19 pmg systemd[1]: Started Session 6 of user root.
Please help me.
 
I just installed it.It's no too more mail incoming.And I don't edit syslog setup.
 
Last edited:
the log lines are from 14.01.2021 17:00 - depending on your timezone I would guess that the PMG has a problem with its clock (it's in the future)

I checked it here and if I set the end-time to 15.01.2021 it displays the mails correctly

I hope this helps!
 
OK,I found it's have data today.But I don't fix or edit anything.I don't know what's wrong.But I happy it's done.
Thanks a lot.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!