401 pmg ticket not read

tcsis

New Member
Oct 28, 2019
29
0
1
37
tail -f /var/log/syslog
Apr 9 15:45:02 mailgw2 ntpd[142]: Soliciting pool server 2a01:4f8:192:4022::2
Apr 9 15:45:04 mailgw2 pmgpolicy[505]: starting policy database maintainance (greylist, rbl)
Apr 9 15:45:04 mailgw2 pmgpolicy[505]: end policy database maintainance (7 ms, 1 ms)
Apr 9 15:45:14 mailgw2 pmg-smtp-filter[28668]: starting database maintainance
Apr 9 15:45:14 mailgw2 pmg-smtp-filter[28668]: end database maintainance (2 ms)
Apr 9 15:45:23 mailgw2 ntpd[142]: Soliciting pool server 217.145.111.106
Apr 9 15:45:25 mailgw2 ntpd[142]: Soliciting pool server 213.209.109.45
Apr 9 15:45:47 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 9 15:45:47 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 9 15:45:53 mailgw2 ntpd[142]: Soliciting pool server 213.251.53.187
Apr 9 15:46:09 mailgw2 ntpd[142]: Soliciting pool server 2a01:4f8:190:708b::2
Apr 9 15:46:28 mailgw2 ntpd[142]: Soliciting pool server 178.63.247.119
Apr 9 15:46:31 mailgw2 ntpd[142]: Soliciting pool server 91.202.42.84

the log for servermailgw2
 

tcsis

New Member
Oct 28, 2019
29
0
1
37
root@mailgw2:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mailgw2(3) 10.70.70.103 node S 5 days 23:54 0.07 14% 1%
mailgw(1) 144.76.166.57 master ERROR: 401 permission denied - invalid PMG ticket - - -% -%
root@mailgw2:~#


root@mailgw:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mailgw(1) 10.70.70.6 master A 6 days 00:18 0.05 26% 8%
mailgw2(3) 78.46.82.152 node ERROR: 401 permission denied - invalid PMG ticket
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
5,908
808
148
hmm - why do the ip-addresses change depending on where you check ? (mailgw2 has a private ip on itself but a public one on mailgw)
can you ssh between both nodes without password?
 

tcsis

New Member
Oct 28, 2019
29
0
1
37
node 1
oot@mailgw:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mailgw(1) 10.70.70.6 master A 6 days 01:11 0.53 26% 8%
mailgw2(3) 78.46.82.152 node ERROR: 401 permission denied - invalid PMG ticket - - -% -%
root@mailgw:~#
root@mailgw:~# journalctl -u pmgmirror
-- Logs begin at Fri 2020-04-03 15:29:54 CEST, end at Thu 2020-04-09 16:41:26 CEST. --
Apr 03 15:30:39 mailgw systemd[1]: Starting Proxmox Mail Gateway Database Mirror Daemon...
Apr 03 15:30:39 mailgw pmgmirror[541]: starting server
Apr 03 15:30:39 mailgw systemd[1]: Started Proxmox Mail Gateway Database Mirror Daemon.
Apr 03 15:32:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:32:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.35 seconds (files 0.23, database 0.12, config 0.00))
Apr 03 15:34:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:34:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.41 seconds (files 0.22, database 0.19, config 0.00))
Apr 03 15:36:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:36:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.24 seconds (files 0.17, database 0.07, config 0.00))
Apr 03 15:38:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:38:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.24 seconds (files 0.14, database 0.10, config 0.00))
Apr 03 15:40:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:40:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.24 seconds (files 0.16, database 0.08, config 0.00))
Apr 03 15:42:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:42:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:44:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:44:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.14, database 0.07, config 0.00))
Apr 03 15:46:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:46:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:48:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:48:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:50:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:50:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:52:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:52:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.23 seconds (files 0.14, database 0.08, config 0.00))
Apr 03 15:54:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:54:39 mailgw pmgmirror[541]: database sync 'mailgw2' failed - DBI connect('dbname=Proxmox_ruledb;host=/run/pmgtunnel;port=3;','root',...) fai
This probably means the server terminated abnormally
before or while processing the request. at /usr/share/perl5/PMG/DBTools.pm line 59.
Apr 03 15:54:39 mailgw pmgmirror[541]: cluster syncronization finished (1 errors, 0.01 seconds (files 0.00, database 0.01, config 0.00))
Apr 03 15:56:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:56:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.41 seconds (files 0.15, database 0.26, config 0.00))
Apr 03 15:58:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:58:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.21 seconds (files 0.15, database 0.06, config 0.00))
Apr 03 16:00:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 16:00:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.21 seconds (files 0.14, database 0.07, config 0.00))
Apr 03 16:02:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 16:02:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.56 seconds (files 0.14, database 0.42, config 0.00))
Apr 03 16:04:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 16:04:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.21 seconds (files 0.14, database 0.07, config 0.00))
Apr 03 16:06:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 16:06:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.25 seconds (files 0.15, database 0.11, config 0.00))
Apr 03 16:08:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 16:08:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 16:10:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 16:10:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.14, database 0.07, config 0.00))
Apr 03 16:11:38 mailgw systemd[1]: Stopping Proxmox Mail Gateway Database Mirror Daemon...
Apr 03 16:11:39 mailgw pmgmirror[541]: received signal TERM
Apr 03 16:11:39 mailgw pmgmirror[541]: server closing
Apr 03 16:11:39 mailgw pmgmirror[541]: server stopped
Apr 03 16:11:40 mailgw systemd[1]: pmgmirror.service: Succeeded.
Apr 03 16:11:40 mailgw systemd[1]: Stopped Proxmox Mail Gateway Database Mirror Daemon.
Apr 03 16:11:40 mailgw systemd[1]: Starting Proxmox Mail Gateway Database Mirror Daemon...
Apr 03 16:11:40 mailgw pmgmirror[2991]: starting server
Apr 03 16:11:40 mailgw systemd[1]: Started Proxmox Mail Gateway Database Mirror Daemon.
Apr 03 16:13:40 mailgw pmgmirror[2991]: starting cluster syncronization
Apr 03 16:13:41 mailgw pmgmirror[2991]: cluster syncronization finished (0 errors, 0.23 seconds (files 0.15, database 0.08, config 0.00))
Apr 03 16:15:40 mailgw pmgmirror[2991]: starting cluster syncronization
Apr 03 16:15:40 mailgw pmgmirror[2991]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.14, database 0.08, config 0.00))
Apr 03 16:17:40 mailgw pmgmirror[2991]: starting cluster syncronization
Apr 03 16:17:40 mailgw pmgmirror[2991]: cluster syncronization finished (0 errors, 0.21 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 16:19:40 mailgw pmgmirror[2991]: starting cluster syncronization
 

tcsis

New Member
Oct 28, 2019
29
0
1
37
conf :
Node 2
pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mailgw2(3) 10.70.70.103 node S 5 days 23:54 0.07 14% 1%
mailgw(1) 144.76.166.57 master ERROR: 401 permission denied - invalid PMG ticket - - -% -%
root@mailgw2:~#

journalctl -u pmgmirror
-- Logs begin at Fri 2020-04-03 15:53:14 CEST, end at Thu 2020-04-09 16:42:54 CEST. --
Apr 03 15:53:43 mailgw2 systemd[1]: Starting Proxmox Mail Gateway Database Mirror Daemon...
Apr 03 15:53:44 mailgw2 pmgmirror[504]: starting server
Apr 03 15:53:44 mailgw2 systemd[1]: Started Proxmox Mail Gateway Database Mirror Daemon.
Apr 03 15:55:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 15:55:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 15:57:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 15:57:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 15:59:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 15:59:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:01:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:01:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:03:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:03:45 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:05:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:05:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:07:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:07:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:09:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:09:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:11:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:11:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:13:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:13:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:15:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:15:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:17:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:17:45 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:19:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:19:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:21:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:21:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:23:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:23:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:25:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:25:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:27:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:27:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:29:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:29:45 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:31:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:31:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:33:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:33:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:35:44 mailgw2 pmgmirror[504]: starting cluster syncronization
Apr 03 16:35:44 mailgw2 pmgmirror[504]: sync error: host '144.76.166.57' is not cluster master
Apr 03 16:37:44 mailgw2 pmgmirror[504]: starting cluster syncronization

conf :

node: 3
fingerprint 09:27:D8:B5:5E:A8:FB:D8:33:FB:75:03:6C:8B:68:7E:AF:8D:C5:0F:9F:D7:CF:45:E0:2F:57:59:79:B6:93:C3
hostrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQDQnkNzQTSdNDC8V16oLqRdNTb/rtloP9u36E80stDyUD6wqIDP22MnyqoXnrwnNHsqTExgoQrhquy9nebumOguq5VnRRf4s1hSr
XjVEyEgRNDCGqCOtl2E0HEOxXO7RrQZd307W3BLNBGpFFGsN1Qor7LDuADgruJ4z3hc+1f4o9ku8fqhBeChs1xpWIC45qTopjlL3G8kmszDyc8s5PawGe2yZul24SOh3oaTBjhxAOVOH3oQXJ5TCnqC
3jrgV85S+FGzFAvRV/f3amWA3r0w9ZkIMqkVdveOIf87BeTrfFPI9MlaI2n8Nq25JBkYHYJ6Oaj682112GZ8XNZFXhWB
ip 10.70.70.103
name mailgw2
rootrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQCcu1yliMsMP3I8fxMVZ1M8InNuw5GMEXGSKCJ1dq9fpaweKMU3RPoq8/BHupcyRAynL5dMLulIBgeLrbvYsuGJxqAwZF/N76VUu
iCqjD+vcuYsWao3RhefH3lMOpAiWGtOcwxNgpWcr5L5407oKpGt2kpjeWci3FmFInypUAj2GwDl2gyZQhq1/7feZ9+DtyZduDVjazUsysZWwD/XWPwQ8APwkgg24YhguVqvVxJGpOeuwa7vI2h7+eB4
rmB6o0iaAJu96MOaEHrqkpv2Hma1NO/k1kT/y2+NTGRWcV3jpNskdWAERhnoUOJAshsmR0QceEQOLyu2+hRPL4p+I4FF

master: 1
fingerprint C6:BD:07:C7:26:40:62:C8:11:1A:1F:3A:73:57:CB:95:15:95:9F:C4:96:90:8A:03:4C:38:E9:96:7F:DE:58:CB
hostrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQDe6HojjGyI/5gxqfuruR5rNelF67V4CIIFfQz7Ph2daRCwHb+yXyiNlqji7dWR/9AzMqOY4UO0+ZgwmopEgrPymBCtbV2Og9c9J
yCpj6PVr8DozXO+5go1PjEpOzYGQTAABoesHHQJo9ZspBAR4PLqVhsQAymAHrLpgLsStYd/HNQ+hSI1Kv2aAQV10FIPb5U3swl23MZFgd2QFmaeVMZCqbNfc6zIViR4S4iMeQcayNBkxyIXf2xdLw0g
RIUxDB5fqbuqJ9wuXazYgZnM9pFUE+jdblveRdI4xlpWlmYJrcT/vlJMMZtKOR6vTwAG28CsmppD/8TUkz0yokB5TplZ
ip 144.76.166.57
maxcid 3
name mailgw
rootrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQDYx5cN2zXsseT7gkT7WWKkyHtJ3fjsEfZmmUgl23B8RkNjBTQlY1hsHD8MmfUlJoz3wzGvtSBVu29npam5sk6z2mVimW5R9IhrM
7pHXnMt4XlWzkcv5JZDSQzPMCz5s+MxHvAtC1o2hPKUQelVh462W9O85TlFIf2uxhCJCiiLhEzf6PxS7torGI25/3nimUsPt09q2pelp8cXLAlXr+DL0YPDfliV9DrB2RUTTGa87hBQKE4JcRYzDy8e
XHt/U39PoJyuUTftmbpGo3RMTI0RU/TOh7udEgzm7c8MTO6Lv7XQM2gKJ9mf0HN9BFaE3+zrZTsObgfowDArN3Dq9vcL


master: 1
fingerprint C6:BD:07:C7:26:40:62:C8:11:1A:1F:3A:73:57:CB:95:15:95:9F:C4:96:90:8A:03:4C:38:E9:96:7F:DE:58:CB
hostrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQDe6HojjGyI/5gxqfuruR5rNelF67V4CIIFfQz7Ph2daRCwHb+yXyiNlqji7dWR/9AzMqOY4UO0+ZgwmopEgrPymBCtbV2Og9c9J
yCpj6PVr8DozXO+5go1PjEpOzYGQTAABoesHHQJo9ZspBAR4PLqVhsQAymAHrLpgLsStYd/HNQ+hSI1Kv2aAQV10FIPb5U3swl23MZFgd2QFmaeVMZCqbNfc6zIViR4S4iMeQcayNBkxyIXf2xdLw0g
RIUxDB5fqbuqJ9wuXazYgZnM9pFUE+jdblveRdI4xlpWlmYJrcT/vlJMMZtKOR6vTwAG28CsmppD/8TUkz0yokB5TplZ
ip 10.70.70.6
maxcid 3
name mailgw
rootrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQDYx5cN2zXsseT7gkT7WWKkyHtJ3fjsEfZmmUgl23B8RkNjBTQlY1hsHD8MmfUlJoz3wzGvtSBVu29npam5sk6z2mVimW5R9IhrM
7pHXnMt4XlWzkcv5JZDSQzPMCz5s+MxHvAtC1o2hPKUQelVh462W9O85TlFIf2uxhCJCiiLhEzf6PxS7torGI25/3nimUsPt09q2pelp8cXLAlXr+DL0YPDfliV9DrB2RUTTGa87hBQKE4JcRYzDy8e
XHt/U39PoJyuUTftmbpGo3RMTI0RU/TOh7udEgzm7c8MTO6Lv7XQM2gKJ9mf0HN9BFaE3+zrZTsObgfowDArN3Dq9vcL

node: 3
fingerprint 09:27:D8:B5:5E:A8:FB:D8:33:FB:75:03:6C:8B:68:7E:AF:8D:C5:0F:9F:D7:CF:45:E0:2F:57:59:79:B6:93:C3
hostrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQDQnkNzQTSdNDC8V16oLqRdNTb/rtloP9u36E80stDyUD6wqIDP22MnyqoXnrwnNHsqTExgoQrhquy9nebumOguq5VnRRf4s1hSr
XjVEyEgRNDCGqCOtl2E0HEOxXO7RrQZd307W3BLNBGpFFGsN1Qor7LDuADgruJ4z3hc+1f4o9ku8fqhBeChs1xpWIC45qTopjlL3G8kmszDyc8s5PawGe2yZul24SOh3oaTBjhxAOVOH3oQXJ5TCnqC
3jrgV85S+FGzFAvRV/f3amWA3r0w9ZkIMqkVdveOIf87BeTrfFPI9MlaI2n8Nq25JBkYHYJ6Oaj682112GZ8XNZFXhWB
ip 78.46.82.152
name mailgw2
rootrsapubkey AAAAB3NzaC1yc2EAAAADAQABAAABAQCcu1yliMsMP3I8fxMVZ1M8InNuw5GMEXGSKCJ1dq9fpaweKMU3RPoq8/BHupcyRAynL5dMLulIBgeLrbvYsuGJxqAwZF/N76VUu
iCqjD+vcuYsWao3RhefH3lMOpAiWGtOcwxNgpWcr5L5407oKpGt2kpjeWci3FmFInypUAj2GwDl2gyZQhq1/7feZ9+DtyZduDVjazUsysZWwD/XWPwQ8APwkgg24YhguVqvVxJGpOeuwa7vI2h7+eB4
rmB6o0iaAJu96MOaEHrqkpv2Hma1NO/k1kT/y2+NTGRWcV3jpNskdWAERhnoUOJAshsmR0QceEQOLyu2+hRPL4p+I4FF
 

tcsis

New Member
Oct 28, 2019
29
0
1
37
NODE 1


root@mailgw:~# date
Thu 09 Apr 2020 03:40:22 PM CEST
root@mailgw:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mailgw(1) 10.70.70.6 master A 6 days 00:18 0.05 26% 8%
mailgw2(3) 78.46.82.152 node ERROR: 401 permission denied - invalid PMG ticket - - -% -%
root@mailgw:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mailgw(1) 10.70.70.6 master A 6 days 01:11 0.53 26% 8%
mailgw2(3) 78.46.82.152 node ERROR: 401 permission denied - invalid PMG ticket - - -% -%
root@mailgw:~# journalctl -u pmgmirror
-- Logs begin at Fri 2020-04-03 15:29:54 CEST, end at Thu 2020-04-09 16:41:26 CEST. --
Apr 03 15:30:39 mailgw systemd[1]: Starting Proxmox Mail Gateway Database Mirror Daemon...
Apr 03 15:30:39 mailgw pmgmirror[541]: starting server
Apr 03 15:30:39 mailgw systemd[1]: Started Proxmox Mail Gateway Database Mirror Daemon.
Apr 03 15:32:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:32:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.35 seconds (files 0.23, database 0.12, config 0.00))
Apr 03 15:34:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:34:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.41 seconds (files 0.22, database 0.19, config 0.00))
Apr 03 15:36:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:36:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.24 seconds (files 0.17, database 0.07, config 0.00))
Apr 03 15:38:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:38:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.24 seconds (files 0.14, database 0.10, config 0.00))
Apr 03 15:40:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:40:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.24 seconds (files 0.16, database 0.08, config 0.00))
Apr 03 15:42:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:42:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:44:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:44:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.14, database 0.07, config 0.00))
Apr 03 15:46:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:46:40 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:48:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:48:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:50:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:50:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.22 seconds (files 0.15, database 0.07, config 0.00))
Apr 03 15:52:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:52:39 mailgw pmgmirror[541]: cluster syncronization finished (0 errors, 0.23 seconds (files 0.14, database 0.08, config 0.00))
Apr 03 15:54:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr 03 15:54:39 mailgw pmgmirror[541]: database sync 'mailgw2' failed - DBI connect('dbname=Proxmox_ruledb;host=/run/pmgtunnel;port=3;','root',...) fai
This probably means the server terminated abnormally
before or while processing the request. at /usr/share/perl5/PMG/DBTools.pm line 59.
Apr 03 15:54:39 mailgw pmgmirror[541]: cluster syncronization finished (1 errors, 0.01 seconds (files 0.00, database 0.01, config 0.00))
Apr 03 15:56:39 mailgw pmgmirror[541]: starting cluster syncronization
Apr
 

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 your own in 60 seconds.

Buy now!