Cluster status with 3 nodes

KOSTAS TSIVERIOTIS

New Member
May 17, 2019
14
0
1
50
Hello everybody,

I have a 3 node cluster with 1 node as master and 2 slave nodes.

When i check configuration/Cluster page, the master node 1, is always in state "active" and the two other nodes, node 2 and node 3, are always in state "syncing".

On dashboard pages, the master node 1 is diplaying different top receiver numbers different than node 2 and 3,
Node 2 and 3 display the same numbers.

Is this normal behaviour?
 

Kenny Huynh

New Member
Dec 26, 2018
14
1
3
22
Hello,

Can you check the status of pmgmirror and pmgtunnel of node 2 and 3
Also Check the status cluster synchronization

upload_2019-8-3_17-5-34.png
 

KOSTAS TSIVERIOTIS

New Member
May 17, 2019
14
0
1
50
pmgtunnel on all nodes running

root@mx1:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DI SK
mx1(1) 77.xx.16.149 master A 3 days 02:13 0.11 71% 2%
mx2(2) 195.xx.74.61 node S 3 days 02:13 0.00 59% 2%
mx3(4) 195.xx.74.62 node S 7 days 00:32 0.16 30% 1%
 

KOSTAS TSIVERIOTIS

New Member
May 17, 2019
14
0
1
50
Aug 05 13:28:08 mx3 pmgmirror[845]: starting cluster syncronization
Aug 05 13:28:09 mx3 pmgmirror[845]: syncing deleted node 3 from master '77.xx.16.149'
Aug 05 13:28:09 mx3 pmgmirror[845]: database sync 'mx1' failed - command 'rsync '--rsh=ssh -l root -o BatchMode=yes -o HostKeyAlias=mx1' -q -aq --timeout 10 '[77.xx.16.149]:/var/spool/pmg/cluster/3/' /var/spool/pmg/cluster/3 --include spam/ --include 'spam/*' --include 'spam/*/*' --include virus/ --include 'virus/*' --include 'virus/*/*' --exclude '*'' failed: exit code 23
Aug 05 13:28:18 mx3 pmgpolicy[843]: starting policy database maintainance (greylist, rbl)
Aug 05 13:28:18 mx3 pmgpolicy[843]: end policy database maintainance (11 ms, 3 ms)
Aug 05 13:28:29 mx3 pmgmirror[845]: registering razor failed: command 'razor-admin -discover' failed: exit code 2
Aug 05 13:28:29 mx3 pmgmirror[845]: cluster syncronization finished (1 errors, 21.68 seconds (files 0.15, database 20.77, config 0.76))
Aug 05 13:28:37 mx3 pmg-smtp-filter[11388]: starting database maintainance
Aug 05 13:28:37 mx3 pmg-smtp-filter[11388]: end database maintainance (5 ms)
Aug 05 13:28:56 mx3 sshd[20466]: Accepted publickey for root from 77.xx.16.149 port 38360 ssh2: RSA SHA256:JGRaW9LK22iGvG/6uUjDD6XDhb2ft2wZbHOEHFDIwyg
Aug 05 13:28:56 mx3 sshd[20466]: pam_unix(sshd:session): session opened for user root by (uid=0)
Aug 05 13:28:56 mx3 sshd[20466]: Received disconnect from 77.xx.16.149 port 38360:11: disconnected by user
Aug 05 13:28:56 mx3 sshd[20466]: Disconnected from 77.xx.16.149 port 38360
Aug 05 13:28:56 mx3 sshd[20466]: pam_unix(sshd:session): session closed for user root
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
1,862
179
63
for the razor2 checks it should be enough to go in the GUI:
'Configuration'->'Spam Detector'->'Options'-> 'Use Razor2 checks' -> disable

afterwards check the clustersync again
 

KOSTAS TSIVERIOTIS

New Member
May 17, 2019
14
0
1
50
root@mx3:~# pmgcm sync
syncing master configuration from '77.xx.16.149'
nextserver: Bootstrap discovery failed. Giving up.
root@mx3:~#


root@mx2:~# pmgcm sync
syncing master configuration from '77.xx.16.149'
nextserver: Bootstrap discovery failed. Giving up.
root@mx2:~#
 

KOSTAS TSIVERIOTIS

New Member
May 17, 2019
14
0
1
50
but dashborad metrics are not synced and nodes status==


root@mx1:~# pmgcm status
NAME(CID)--------------IPADDRESS----ROLE-STATE---------UPTIME---LOAD----MEM---DISK
mx3(4) 195.xx.74.62 node S 00:16 0.09 24% 1%
mx2(2) 195.xx.74.61 node S 00:16 0.00 46% 2%
mx1(1) 77.xx.16.149 master A 00:16 0.19 50% 2%
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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!