/#pmgMailTracker Tracking Center: No data in database (Mail Gateway 7.1-1)

K

KatyComputer

Well-Known Member
Sep 26, 2019
193
16
58
62
St Louis
katycomputer.com
Our tracking center is showing no data in database. When I didn't find the data I sought, I tried searching our top 3 recipients as defined on the dash board.

Any idea how to solve this mystery?

I have used incognito mode, PMG is quite clear, no data:
1641474025947.png


We are using 1/3 of the disk space allotted PMG.

A few filtered syslog lines:

tail -n 300 /var/log/syslog | grep -vi "postfix" Jan 6 07:13:55 mx systemd[867]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied Jan 6 07:13:55 mx systemd[867]: systemd-logind.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-logind: Permission denied Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Jan 6 07:13:55 mx systemd[1]: Failed to start User Login Management. Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1. Jan 6 07:13:55 mx systemd[1]: Stopped User Login Management. Jan 6 07:13:55 mx systemd[1]: Starting Load Kernel Module drm... Jan 6 07:13:55 mx systemd[1]: modprobe@drm.service: Succeeded. Jan 6 07:13:55 mx systemd[1]: Finished Load Kernel Module drm. Jan 6 07:13:55 mx systemd[1]: Starting User Login Management... Jan 6 07:13:55 mx systemd[871]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied Jan 6 07:13:55 mx systemd[871]: systemd-logind.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-logind: Permission denied Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Jan 6 07:13:55 mx systemd[1]: Failed to start User Login Management. Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 2. Jan 6 07:13:55 mx systemd[1]: Stopped User Login Management. Jan 6 07:13:55 mx systemd[1]: Starting Load Kernel Module drm... Jan 6 07:13:55 mx systemd[1]: modprobe@drm.service: Succeeded. Jan 6 07:13:55 mx systemd[1]: Finished Load Kernel Module drm. Jan 6 07:13:55 mx systemd[1]: Starting User Login Management... Jan 6 07:13:55 mx systemd[875]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied Jan 6 07:13:55 mx systemd[875]: systemd-logind.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-logind: Permission denied Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Jan 6 07:13:55 mx systemd[1]: Failed to start User Login Management. Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 3. Jan 6 07:13:55 mx systemd[1]: Stopped User Login Management. Jan 6 07:13:55 mx systemd[1]: Starting Load Kernel Module drm... Jan 6 07:13:55 mx systemd[1]: modprobe@drm.service: Succeeded. Jan 6 07:13:55 mx systemd[1]: Finished Load Kernel Module drm. Jan 6 07:13:55 mx systemd[1]: Starting User Login Management... Jan 6 07:13:55 mx systemd[879]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied Jan 6 07:13:55 mx systemd[879]: systemd-logind.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-logind: Permission denied Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE Jan 6 07:13:55 mx systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Jan 6 07:13:55 mx systemd[1]: Failed to start User Login Management. Jan 6 07:13:56 mx systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 4. Jan 6 07:13:56 mx systemd[1]: Stopped User Login Management. Jan 6 07:13:56 mx systemd[1]: Starting Load Kernel Module drm... Jan 6 07:13:56 mx systemd[1]: modprobe@drm.service: Succeeded. Jan 6 07:13:56 mx systemd[1]: Finished Load Kernel Module drm. Jan 6 07:13:56 mx systemd[1]: Starting User Login Management... Jan 6 07:13:56 mx systemd[883]: systemd-logind.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc: Permission denied Jan 6 07:13:56 mx systemd[883]: systemd-logind.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-logind: Permission denied Jan 6 07:13:56 mx systemd[1]: systemd-logind.service: Main process exited, code=exited, status=226/NAMESPACE Jan 6 07:13:56 mx systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Jan 6 07:13:56 mx systemd[1]: Failed to start User Login Management. Jan 6 07:13:56 mx systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 5. Jan 6 07:13:56 mx systemd[1]: Stopped User Login Management. Jan 6 07:13:56 mx systemd[1]: modprobe@drm.service: Start request repeated too quickly. Jan 6 07:13:56 mx systemd[1]: modprobe@drm.service: Failed with result 'start-limit-hit'. Jan 6 07:13:56 mx systemd[1]: Failed to start Load Kernel Module drm. Jan 6 07:13:56 mx systemd[1]: systemd-logind.service: Start request repeated too quickly. Jan 6 07:13:56 mx systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Jan 6 07:13:56 mx systemd[1]: Failed to start User Login Management. Jan 6 07:14:18 mx pmgpolicy[505]: starting policy database maintenance (greylist, rbl) Jan 6 07:14:18 mx pmgpolicy[505]: end policy database maintenance (27 ms, 0 ms)
 
KatyComputer said:
We don't have an urgent need for the tracking center.

Typically, how long does it take for things move from test to production?
Click to expand...
I expect the move next week.
 
You must log in or register to reply here.
Top Bottom