Question regarding Failover 3 Node System Backend Network
exitsys
43 Posts
September 28, 2020, 8:09 amQuote from exitsys on September 28, 2020, 8:09 amI 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?
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?
admin
2,930 Posts
September 28, 2020, 8:21 amQuote from admin on September 28, 2020, 8:21 amwhat version are you using ?
what version are you using ?
admin
2,930 Posts
September 28, 2020, 9:26 amQuote from admin on September 28, 2020, 9:26 amalso post the complete log
also post the complete log
Last edited on September 28, 2020, 9:26 am by admin · #13
exitsys
43 Posts
September 28, 2020, 9:39 amQuote from exitsys on September 28, 2020, 9:39 amVersion 2.6.2
how can i get the log without Network Connection?
Version 2.6.2
how can i get the log without Network Connection?
admin
2,930 Posts
September 28, 2020, 9:56 amQuote from admin on September 28, 2020, 9:56 amCan 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
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
exitsys
43 Posts
September 28, 2020, 12:37 pmQuote from exitsys on September 28, 2020, 12:37 pmat 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
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
exitsys
43 Posts
September 28, 2020, 12:43 pmQuote from exitsys on September 28, 2020, 12:43 pmps 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
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
Last edited on September 28, 2020, 1:00 pm by exitsys · #17
admin
2,930 Posts
September 28, 2020, 1:09 pmQuote from admin on September 28, 2020, 1:09 pmgot 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
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
Last edited on September 28, 2020, 1:09 pm by admin · #18
exitsys
43 Posts
September 28, 2020, 1:43 pmQuote from exitsys on September 28, 2020, 1:43 pmOK ssh is working now.
it was because of my ssh client. it somehow had a problem.
OK ssh is working now.
it was because of my ssh client. it somehow had a problem.
admin
2,930 Posts
September 28, 2020, 1:52 pmQuote from admin on September 28, 2020, 1:52 pmdmesg / syslog erros ? eth names ?
dmesg / syslog erros ? eth names ?
Last edited on September 28, 2020, 1:52 pm by admin · #20
Question regarding Failover 3 Node System Backend Network
exitsys
43 Posts
Quote from exitsys on September 28, 2020, 8:09 amI 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?
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?
admin
2,930 Posts
Quote from admin on September 28, 2020, 8:21 amwhat version are you using ?
what version are you using ?
admin
2,930 Posts
Quote from admin on September 28, 2020, 9:26 amalso post the complete log
also post the complete log
exitsys
43 Posts
Quote from exitsys on September 28, 2020, 9:39 amVersion 2.6.2
how can i get the log without Network Connection?
Version 2.6.2
how can i get the log without Network Connection?
admin
2,930 Posts
Quote from admin on September 28, 2020, 9:56 amCan 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
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
exitsys
43 Posts
Quote from exitsys on September 28, 2020, 12:37 pmat 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
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
exitsys
43 Posts
Quote from exitsys on September 28, 2020, 12:43 pmps aux | grep sshd - OKnetstat -plant | grep :22 - OKlsof -i - OK Unfortunately I cannot get a connection via ssh. 172.16.2.201 i send a screenshot to contact-us@petasan.org
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
admin
2,930 Posts
Quote from admin on September 28, 2020, 1:09 pmgot 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
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
exitsys
43 Posts
Quote from exitsys on September 28, 2020, 1:43 pmOK ssh is working now.
it was because of my ssh client. it somehow had a problem.
OK ssh is working now.
it was because of my ssh client. it somehow had a problem.
admin
2,930 Posts
Quote from admin on September 28, 2020, 1:52 pmdmesg / syslog erros ? eth names ?
dmesg / syslog erros ? eth names ?