[SOLVED] PMG Tracking Blank ... again

[zolthar]

Currently for me my time is Feb 1, 2022 13:26 AEST when this was posted.

Tracking Centre is blank again as the same for the start of the year.


Did the following after 5:45pm as I can reboot and have minimal impact on clients:

I have restarted SysLog service and rebooted the server and not showing up, however I can definitely see those logs coming through not affecting mail deliver.

proxmox-mailgateway-container: 7.1-1
pmg-api: 7.1-1
pmg-gui: 3.1-1
clamav-daemon: 0.103.3+dfsg-0+deb11u1
ifupdown: 0.8.36
libarchive-perl: 3.4.0-1
libjs-extjs: 7.0.0-1
libjs-framework7: 4.4.7-1
libproxmox-acme-perl: 1.4.1
libproxmox-acme-plugins: 1.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-http-server-perl: 4.1-1
libxdgmime-perl: 1.0-1
lvm2: not correctly installed
pmg-docs: 7.1-1
pmg-i18n: 2.6-2
pmg-log-tracker: 2.3.0-1
postgresql-13: 13.5-0+deb11u1
proxmox-mini-journalreader: 1.3-1
proxmox-spamassassin: 3.4.6-4
proxmox-widget-toolkit: 3.4-5
pve-xtermjs: 4.12.0-1

Rotated logs without success:

logrotate -vf /etc/logrotate.d/rsyslog
/etc/init.d/rsyslog restart

SOLUTION
If you re reading this with future re-occurrences and you have v7, to fix this issue:

1. Wait for Admin to say a fix has been implemented
2. Configure/Add "No-Sub Repository" in GUI (Administration > Repositories > Add > Repositories = No Subscription)
3. Refresh Updates in GUI (Administration > Updates > Refresh)
4. If you ONLY want to update the fix:
   1. Open Console
   2. Type: apt-get install pmg-log-tracker
5. If you are lazy and just install everything cause you have absolute faith in the PMG team (ie. me)
   1. Upgrade everything from the No-Sub Repo
6. Disable the "No-Sub" Repo for Enterprise Users

If you are running v6, then you will have to manually add the repo and update/install in CLI.

 

[4920441]

The same here.
whats the problem with a monthly change?

 

[Stoiko Ivanov]

Thanks for the report - I'll look into it

 

[rl72]

Same here.
Rebooted, made manual logrotate - nothing worked.

 

[alphadark]

Yep, same issue here.
Reboot, manual logrotate - but nothing.

 

[halimofff]

+1

 

[hata_ph]

Just cannot view logs for 1/2/2022.

 

[compleetit]

Same here, the other pages seem fine

 

[Stoiko Ivanov]

sorry for the inconvenience.

A first preliminary patch was sent to the pmg-devel list - once this or an improved version is applied and made available in one of the public repositories I'll update this thread

https://lists.proxmox.com/pipermail/pmg-devel/2022-February/001974.html

EDIT: added reference to the mailing-list archive

 

[fhn1979]

Same here with my German Thread: https://forum.proxmox.com/threads/tracking-center-no-data-in-database.104093/
But i think this thread here is enought.

 

[ArchanfelHUN]

Same here, but i did figured out something.
This gets me results: pmg-log-tracker -v -l 1 -s '2022:02:01 12:00:00' -n -g
But this not: pmg-log-tracker -v -l 1 -s '2022-02-01 12:00:00' -n -g
Also executing pmg-log-tracker alone didnt get any results for obvious reason.
Proxmox tracking uses the second one, so i think there is something wrong with the date delimiter.

 

[fhn1979]

Same here, but i did figured out something.
This gets me results: pmg-log-tracker -v -l 1 -s '2022:02:01 12:00:00' -n -g
But this not: pmg-log-tracker -v -l 1 -s '2022-02-01 12:00:00' -n -g
Also executing pmg-log-tracker alone didnt get any results for obvious reason.
Proxmox tracking uses the second one, so i think there is something wrong with the date delimiter.

I think there is another problem to be seen with pmg-devel too. If it were the Delemiter, it shouldn't have worked the last few days either.

 

[Stoiko Ivanov]

This gets me results: pmg-log-tracker -v -l 1 -s '2022:02:01 12:00:00' -n -g

I think this might be a wrong lead - the arguments to -s ('2022:02:01') are parsed by strptime ( https://man7.org/linux/man-pages/man3/strptime.3.html) and since this is not interpreted as a date-time as 2022-02-01 12:00:00 would have been - it's taken as
unix-epoch (and thus only 2022 is used (as seconds since 1970-01-01 00:00:00 UTC)

Additionally the API (and thus also the GUI) pass the time as unix-epoch

 

[ArchanfelHUN]

We have a free and a paid version of the PMG. The paid version didnt have this issue.
The paid have this version: 2.2.0-1 (enterprise repo)
So the issue is something what got into the newer versions.

 

[tom]

See http://download.proxmox.com/debian/...inary-amd64/pmg-log-tracker_2.3.1-1.changelog

 

[fhn1979]

See http://download.proxmox.com/debian/...inary-amd64/pmg-log-tracker_2.3.1-1.changelog

It Worked! Perfect.

 

[ArchanfelHUN]

Yep, solved the issue.

 

[alphadark]

Yep, works perfect!
Thx!

 

[wwweiss]

Will this patch come to the normal repo soon? If not, what is the recommended way to update now?

 

[troycarpenter]

Will this patch come to the normal repo soon? If not, what is the recommended way to update now?

I just did an upgrade and the fix is there now. pmg-log-tracker_2.3.1-1