I am having this issue as well. Something with the last update must have change the parameter.

Varick

Hi there,

I had the same Problem on a hyper-v system. Solution = Rebuild second node and rebuild HA. That is done in 10 Minutes.

regards

mod

I am not clustered nor virtual.  I running UTM on a single HD?   Any suggestions?

Hi Varick,

the subject is

After up2date, slave node death

Please create a new threat with your issue. That's not the same.

Regards

mod

Yes Mod while I appreciate the subject line and understand I may not be configured for clustering, I have the exact same symptom and error messages caused by the same up2date to version9.500.9. I can start my own thread but searches in the forum led me here because of the error message. Something in that release caused this error.

Yes Mod while I appreciate the subject line and understand I may not be configured for clustering, I have the exact same symptom and error messages caused by the same up2date to version9.500.9. I can start my own thread but searches in the forum led me here because of the error message. Something in that release caused this error.

I contacted the sophos technical support but could not give me support because it was not possible to connect it remotely to a PC that I connected via the serial port to the slave node, then I decided to reinstall the slave node and rebuild the cluster.

I tried connecting from a pc to the master node (that worked perfectly) but not even there it was possible to connect via serial port.
Do I think it's only possible with appliances?

Hi papali,

you should connect via ssh to the master and then you can switch to slave with ha_utils ssh

regards

mod

Hi mod2402, I tried, but there was only 1 node, probably the slave node failed to load the modules needed to be recognized as online?