Some troubles after upgrade from 2.1.5 to 2.2.2
-
Hello,
We have some troubles after upgrade to 2.2.2.
Indeed the upgrade operation worked well, no problems after reboot on the both nodes, but after 2-3 hours the node A has stopped to work correctly and the node B became master.
No way to ping the node A on his IP from the network, but it's possible from node B via pfsync ip address.
To see what happened on the node A, we connected on node A via ssh from node B, in the log we have seen nothing strange, just notifications about carp changing.When we tried to show the network interfaces status with "ifconfig" command the terminal got stuck and no way to kill it.
We have tried to replace the RAM, no changes :-/
Do you have any idea of what happen ?Installation Diagram :
PF A : Master
|
| Pfsync
|
PF B : SlaveThank you very much
PS : Sorry for my english, i hope to be clear
-
More information please.
What hardware are you running? NIC types especially?
Are you able to access the primary after rebooting it? It goes back to being the backup after a few hours again?Steve