We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
BUG when adding secondary ip?
BUG when adding secondary ip?
Hello, os CentOS 7
When you add a secondary ip, my vesta created :
ifcfg-ens3:0
cat
# Added by vesta
DEVICE=ens3:0
BOOTPROTO=static
ONBOOT=yes
IPADDR=xxx.xx.xxx.133
NETMASK=255.255.255.0
Then after reboot.
systemctl --failed
● httpd.service loaded failed failed The Apache HTTP Server
● nginx.service loaded failed failed nginx - high performance web server
my fix is: rm /etc/sysconfig/network-scripts/ifcfg-ens3:0
But then the secondary ip on panel will not work. So.....
my fix is to manually add the ip to:
ifcfg-eth0
cat
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eth0
UUID=02a3ff16-b9cb-47b3-8ef5-cedbdbbe2edc
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR1=xxx.xx.xxx.xxx
IPADDR2=xxx.xx.xxx.xxx
Then reboot it starts working..
IS THERE any other EAsier way to fix this without manually editing ? if none is my method correct , if no then what would be right way to fix it?
Thank you
When you add a secondary ip, my vesta created :
ifcfg-ens3:0
cat
# Added by vesta
DEVICE=ens3:0
BOOTPROTO=static
ONBOOT=yes
IPADDR=xxx.xx.xxx.133
NETMASK=255.255.255.0
Then after reboot.
systemctl --failed
● httpd.service loaded failed failed The Apache HTTP Server
● nginx.service loaded failed failed nginx - high performance web server
my fix is: rm /etc/sysconfig/network-scripts/ifcfg-ens3:0
But then the secondary ip on panel will not work. So.....
my fix is to manually add the ip to:
ifcfg-eth0
cat
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eth0
UUID=02a3ff16-b9cb-47b3-8ef5-cedbdbbe2edc
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR1=xxx.xx.xxx.xxx
IPADDR2=xxx.xx.xxx.xxx
Then reboot it starts working..
IS THERE any other EAsier way to fix this without manually editing ? if none is my method correct , if no then what would be right way to fix it?
Thank you