Network not coming up after restart
jeenode
27 Posts
September 29, 2020, 4:49 pmQuote from jeenode on September 29, 2020, 4:49 pmHi,
I did have to restart one of the node of a 3 node cluster and it didnt have services started after reboot.
After looking at it, I see that the network interfaces do not seem to get brought up on boot. If I bring management and front/end interface IPs up manually and restart Ceph services, all works ok. Checked that /.etc/network/interfaces has proper config for mgmt interface and "systemctl restart networking" brings it up ok.
Any pointers as to where to look?
PeataSAN version 2.6, was originally installed with 2.1 and then upgraded using standard methods (via boot CD first, than apt-get).
Thanks!
Hi,
I did have to restart one of the node of a 3 node cluster and it didnt have services started after reboot.
After looking at it, I see that the network interfaces do not seem to get brought up on boot. If I bring management and front/end interface IPs up manually and restart Ceph services, all works ok. Checked that /.etc/network/interfaces has proper config for mgmt interface and "systemctl restart networking" brings it up ok.
Any pointers as to where to look?
PeataSAN version 2.6, was originally installed with 2.1 and then upgraded using standard methods (via boot CD first, than apt-get).
Thanks!
admin
2,930 Posts
September 29, 2020, 8:33 pmQuote from admin on September 29, 2020, 8:33 pmDo you see any errors in PetaSAN.log file ?
PetaSAN does not use the Ubuntu /etc/network/interfaces, or to be exact it is used at the very beginning of the boot process for the management interface until PetaSAN takes over. The network configuration is set in cluster_info.json and node_info.json
Do you see any errors in PetaSAN.log file ?
PetaSAN does not use the Ubuntu /etc/network/interfaces, or to be exact it is used at the very beginning of the boot process for the management interface until PetaSAN takes over. The network configuration is set in cluster_info.json and node_info.json
Network not coming up after restart
jeenode
27 Posts
Quote from jeenode on September 29, 2020, 4:49 pmHi,
I did have to restart one of the node of a 3 node cluster and it didnt have services started after reboot.
After looking at it, I see that the network interfaces do not seem to get brought up on boot. If I bring management and front/end interface IPs up manually and restart Ceph services, all works ok. Checked that /.etc/network/interfaces has proper config for mgmt interface and "systemctl restart networking" brings it up ok.
Any pointers as to where to look?
PeataSAN version 2.6, was originally installed with 2.1 and then upgraded using standard methods (via boot CD first, than apt-get).
Thanks!
Hi,
I did have to restart one of the node of a 3 node cluster and it didnt have services started after reboot.
After looking at it, I see that the network interfaces do not seem to get brought up on boot. If I bring management and front/end interface IPs up manually and restart Ceph services, all works ok. Checked that /.etc/network/interfaces has proper config for mgmt interface and "systemctl restart networking" brings it up ok.
Any pointers as to where to look?
PeataSAN version 2.6, was originally installed with 2.1 and then upgraded using standard methods (via boot CD first, than apt-get).
Thanks!
admin
2,930 Posts
Quote from admin on September 29, 2020, 8:33 pmDo you see any errors in PetaSAN.log file ?
PetaSAN does not use the Ubuntu /etc/network/interfaces, or to be exact it is used at the very beginning of the boot process for the management interface until PetaSAN takes over. The network configuration is set in cluster_info.json and node_info.json
Do you see any errors in PetaSAN.log file ?
PetaSAN does not use the Ubuntu /etc/network/interfaces, or to be exact it is used at the very beginning of the boot process for the management interface until PetaSAN takes over. The network configuration is set in cluster_info.json and node_info.json