Hello everyone!
I have problems using LDAP user synchronization. The systemd timer pmg-hourly.timer periodically loses the trigger. It stops running pmg-hourly.service on schedule.
systemctl status pmg-hourly.timer
● pmg-hourly.timer - Hourly Proxmox Mail Gateway activities
Loaded: loaded (/lib/systemd/system/pmg-hourly.timer; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-08-28 15:28:31 MSK; 1 months 11 days ago
Trigger: n/a
Triggers: ● pmg-hourly.service
systemctl status pmg-hourly.service
● pmg-hourly.service - Hourly Proxmox Mail Gateway activities
Loaded: loaded (/lib/systemd/system/pmg-hourly.service; static)
Active: activating (start) since Sun 2024-10-06 19:00:04 MSK; 2 days ago
TriggeredBy: ● pmg-hourly.timer
Main PID: 805272 (pmg-hourly)
Tasks: 1 (limit: 7026)
Memory: 78.4M
CPU: 1.972s
CGroup: /system.slice/pmg-hourly.service
└─805272 /usr/bin/perl -T /usr/lib/pmg/bin/pmg-hourly
pmgversion -v
proxmox-mailgateway: 7.3-2 (API: 7.3-11/86dae94d, running kernel: 5.15.158-2-pve)
pmg-api: 7.3-11
pmg-gui: 3.3-3
pve-kernel-5.15: 7.4-15
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.15.126-1-pve: 5.15.126-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-1-pve: 5.11.22-2
clamav-daemon: 0.103.10+dfsg-0+deb11u1
ifupdown2: 3.1.0-1+pmx4
libarchive-perl: 3.4.0-1
libjs-extjs: 7.0.0-1
libjs-framework7: 4.4.7-1
libproxmox-acme-perl: 1.4.4
libproxmox-acme-plugins: 1.4.4
libpve-apiclient-perl: 3.2-2
libpve-common-perl: 7.4-2
libpve-http-server-perl: 4.2-3
libxdgmime-perl: 1.0-1
lvm2: 2.03.11-2.1
pmg-docs: 7.3-3
pmg-i18n: 2.12-1
pmg-log-tracker: 2.3.2-1
postgresql-13: 13.16-0+deb11u1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-spamassassin: 4.0.0-2
proxmox-widget-toolkit: 3.7.4
pve-firmware: 3.6-6
pve-xtermjs: 4.16.0-2
zfsutils-linux: 2.1.15-pve1
Workaround:
restart pmg-hourly.service
I also noticed that the execution process freezes, apparently because of this the timer trigger goes into the n/a state.
journalctl -u pmg-hourly.service -n 7
Oct 06 18:00:04 mx01 systemd[1]: Starting Hourly Proxmox Mail Gateway activities...
Oct 06 18:00:04 mx01 pmg-hourly[800839]: start syncing ldap profile 'ldap' (myldapserver)
Oct 06 18:00:08 mx01 pmg-hourly[800839]: finished syncing ldap profile 'ldap' (myldapserver): found 1849 accounts, 1868 addresses, 124 groups
Oct 06 18:00:11 mx01 systemd[1]: pmg-hourly.service: Succeeded.
Oct 06 18:00:11 mx01 systemd[1]: Finished Hourly Proxmox Mail Gateway activities.
Oct 06 18:00:11 mx01 systemd[1]: pmg-hourly.service: Consumed 5.995s CPU time.
Oct 06 19:00:04 mx01 systemd[1]: Starting Hourly Proxmox Mail Gateway activities...
Any suggestions to solve the synchronization problem?
I have problems using LDAP user synchronization. The systemd timer pmg-hourly.timer periodically loses the trigger. It stops running pmg-hourly.service on schedule.
systemctl status pmg-hourly.timer
● pmg-hourly.timer - Hourly Proxmox Mail Gateway activities
Loaded: loaded (/lib/systemd/system/pmg-hourly.timer; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-08-28 15:28:31 MSK; 1 months 11 days ago
Trigger: n/a
Triggers: ● pmg-hourly.service
systemctl status pmg-hourly.service
● pmg-hourly.service - Hourly Proxmox Mail Gateway activities
Loaded: loaded (/lib/systemd/system/pmg-hourly.service; static)
Active: activating (start) since Sun 2024-10-06 19:00:04 MSK; 2 days ago
TriggeredBy: ● pmg-hourly.timer
Main PID: 805272 (pmg-hourly)
Tasks: 1 (limit: 7026)
Memory: 78.4M
CPU: 1.972s
CGroup: /system.slice/pmg-hourly.service
└─805272 /usr/bin/perl -T /usr/lib/pmg/bin/pmg-hourly
pmgversion -v
proxmox-mailgateway: 7.3-2 (API: 7.3-11/86dae94d, running kernel: 5.15.158-2-pve)
pmg-api: 7.3-11
pmg-gui: 3.3-3
pve-kernel-5.15: 7.4-15
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.15.126-1-pve: 5.15.126-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-1-pve: 5.11.22-2
clamav-daemon: 0.103.10+dfsg-0+deb11u1
ifupdown2: 3.1.0-1+pmx4
libarchive-perl: 3.4.0-1
libjs-extjs: 7.0.0-1
libjs-framework7: 4.4.7-1
libproxmox-acme-perl: 1.4.4
libproxmox-acme-plugins: 1.4.4
libpve-apiclient-perl: 3.2-2
libpve-common-perl: 7.4-2
libpve-http-server-perl: 4.2-3
libxdgmime-perl: 1.0-1
lvm2: 2.03.11-2.1
pmg-docs: 7.3-3
pmg-i18n: 2.12-1
pmg-log-tracker: 2.3.2-1
postgresql-13: 13.16-0+deb11u1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-spamassassin: 4.0.0-2
proxmox-widget-toolkit: 3.7.4
pve-firmware: 3.6-6
pve-xtermjs: 4.16.0-2
zfsutils-linux: 2.1.15-pve1
Workaround:
restart pmg-hourly.service
I also noticed that the execution process freezes, apparently because of this the timer trigger goes into the n/a state.
journalctl -u pmg-hourly.service -n 7
Oct 06 18:00:04 mx01 systemd[1]: Starting Hourly Proxmox Mail Gateway activities...
Oct 06 18:00:04 mx01 pmg-hourly[800839]: start syncing ldap profile 'ldap' (myldapserver)
Oct 06 18:00:08 mx01 pmg-hourly[800839]: finished syncing ldap profile 'ldap' (myldapserver): found 1849 accounts, 1868 addresses, 124 groups
Oct 06 18:00:11 mx01 systemd[1]: pmg-hourly.service: Succeeded.
Oct 06 18:00:11 mx01 systemd[1]: Finished Hourly Proxmox Mail Gateway activities.
Oct 06 18:00:11 mx01 systemd[1]: pmg-hourly.service: Consumed 5.995s CPU time.
Oct 06 19:00:04 mx01 systemd[1]: Starting Hourly Proxmox Mail Gateway activities...
Any suggestions to solve the synchronization problem?
