Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Question regarding Failover 3 Node System Backend Network

Pages: 1 2 3

I have switches that do not support LACP over multiple switches. I have, as I wrote above, tried all variants that are switch independent, including Active-Backup. The server is then immediately in Step 7 no longer accessible. No more ping answers. And even after 30min waiting time it won't come back online. Extracts from the log of the upper post do not help?

what version are you using ?

also post the complete log

Version 2.6.2

how can i get the log without Network Connection?

Can you log into the console, use ALT + F1 ( try F1 to F6 ) to get a virtual console and log as root with cluster password.

You can either view the log and see if there are any more errors that what you posted. or better configure yourslef

ip addr add 172.16.2.201/24 dev eth0

ip addr list

Then you should access it via ssh.

If this works, we can send you a patch to include more logs to help identify the issue, but we need access to getting the logs

at the moment when i click on continue the network service seems to crash. if i enter on the console "systemctl restart networking" the machine is accessible again. but the configuration is not completed and brings the error:  Error saving node network settings. i will now try to get the logfiles

ps aux | grep sshd - OK
netstat -plant | grep :22 - OK
lsof -i - OK

Unfortunately I cannot get a connection via ssh. 172.16.2.201

i send a screenshot to contact-us@petasan.org

got the email and we are looking at it.

do you see any kernel errors in dmesg or in syslog ?

did you rename the eth0 names to something custom ?

to try to get ssh working, try to use the ip addr command posted earlier and restart the ssh service via systemctl restart ssh

 

OK ssh is working now.
it was because of my ssh client. it somehow had a problem.

dmesg / syslog erros ? eth names ?

Pages: 1 2 3