FreePBX Restored from Vultr Snapshot - No IP on boot
-
I guess this is my week to blow up ML with new posts.
So I moved a few ancient remaining customers from my Vultr account to their own, something I have been meaning to do for a year and and half now. The process involved taking a snapshot, requesting vultr to move the snapshot from both accounts and then restoring the snapshot.
Since you lose the IP address this way, we planned a cutover and updated the phones during lunch. Everything went fine except that everytime you reboot FreePBX (for updates etc) it comes online with no ip address.
I assumed this is because I had configured FreePBX for a static IP in System Admin, so I jumped on Putty and ran this from root...
sudo dhclient eth1 -v
And it immediately grabbed its new ip address again. I try to update the network settings in system admin to configuer the static IP, or even to permanently use DHCP, and upon saving it just reverts back to its original setting. So whenever the instance is rebooted it comes back up with no ip stack and I have to run the 'sudo dhclient' again from root to get it working.
This is happening on all 3 customers machines after the migration. I was about to move them to Fusion or Genband but upon reading a little more about FreePBX I thought it would be handy to keep at least one of them on this so I dont fall behind. The updates are honestly my biggest gripe. I think all three of them have errors or are "dorked" in some way with updates. So once I fix the IP Stack issue I am going to start working through cleaning that up and upgrading them to FreePBX 14 with Asterisk 15.
Anyone ever have an issue like this?
-
@bigbear I've never had one where a change from SysAdmin was not kept. Have you tried that?
-
Network settings are part of the free SysAdmin module that is active with PBX registration.
-
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
-
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
Bring it up, change the setting. Save. Change the setting again. Save. Reboot.
Kind of grasping a bit here.
If it was truly DHCP, it should see a gateway.
-
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
Bring it up, change the setting. Save. Change the setting again. Save. Reboot.
Kind of grasping a bit here.
If it was truly DHCP, it should see a gateway.
Even after consecutive changes/saves in the GUI it just reverts to the ip/netmask and no gateway. I unlocked the system to try to run updates (the last 3 system updates have failed on this install) and it has hung on phase 1. Trying to get some support on both matters over at FreePBX forums.
BWT is there a way to update from fwconsole that is more reliable in FreePBX13?
-
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
Bring it up, change the setting. Save. Change the setting again. Save. Reboot.
Kind of grasping a bit here.
If it was truly DHCP, it should see a gateway.
Even after consecutive changes/saves in the GUI it just reverts to the ip/netmask and no gateway. I unlocked the system to try to run updates (the last 3 system updates have failed on this install) and it has hung on phase 1. Trying to get some support on both matters over at FreePBX forums.
BWT is there a way to update from fwconsole that is more reliable in FreePBX13?
The update process is the same. Just in FreePBX 13, there was also a "firmware" step that no longer exists in FreePBX 14.
-
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
Bring it up, change the setting. Save. Change the setting again. Save. Reboot.
Kind of grasping a bit here.
If it was truly DHCP, it should see a gateway.
Even after consecutive changes/saves in the GUI it just reverts to the ip/netmask and no gateway. I unlocked the system to try to run updates (the last 3 system updates have failed on this install) and it has hung on phase 1. Trying to get some support on both matters over at FreePBX forums.
BWT is there a way to update from fwconsole that is more reliable in FreePBX13?
The update process is the same. Just in FreePBX 13, there was also a "firmware" step that no longer exists in FreePBX 14.
Does this look like the most recent version of 13?
Current Version 10.13.66-22
-
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
Bring it up, change the setting. Save. Change the setting again. Save. Reboot.
Kind of grasping a bit here.
If it was truly DHCP, it should see a gateway.
Even after consecutive changes/saves in the GUI it just reverts to the ip/netmask and no gateway. I unlocked the system to try to run updates (the last 3 system updates have failed on this install) and it has hung on phase 1. Trying to get some support on both matters over at FreePBX forums.
BWT is there a way to update from fwconsole that is more reliable in FreePBX13?
The update process is the same. Just in FreePBX 13, there was also a "firmware" step that no longer exists in FreePBX 14.
Does this look like the most recent version of 13?
Current Version 10.13.66-22
Yes.
-
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Network settings are part of the free SysAdmin module that is active with PBX registration.
Once I bring it online with ifconfig I go to that part of the GUI, it shows the ip address and netmask I give it and no gateway info (it is remotely accessible at this point and works fine). Once I reboot the settings are lost and I have to run ifconfig from the console to bring it back online again.
Bring it up, change the setting. Save. Change the setting again. Save. Reboot.
Kind of grasping a bit here.
If it was truly DHCP, it should see a gateway.
Even after consecutive changes/saves in the GUI it just reverts to the ip/netmask and no gateway. I unlocked the system to try to run updates (the last 3 system updates have failed on this install) and it has hung on phase 1. Trying to get some support on both matters over at FreePBX forums.
BWT is there a way to update from fwconsole that is more reliable in FreePBX13?
The update process is the same. Just in FreePBX 13, there was also a "firmware" step that no longer exists in FreePBX 14.
Does this look like the most recent version of 13?
Current Version 10.13.66-22
Yes.
I Under /etc/sysconfig/network-scripts/ I have both
ifcfg-eth0
ifcfg-eth1These systems were restored from snapshots on vultr, and it appears that is why they have an eth0 with some old info in them and eth1 with “undefined” in them.
Should I just delete both of these and reboot, then reconfigure? It seems when I restored the snapshot it created eth1 which is the adapter that is losing its setting.
Or would deleting eth0 solve the issue and allow me to configure eth1
Also thinking I could remove UUID from eth0, delete eth1 and fix it up that way.
Any suggestions?
eth0 screen shot from VIM
eth1 screen shot from VIM
-
Is your hardware address right? Duplicated MAC address might be an issue?
-
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Is your hardware address right? Duplicated MAC address might be an issue?
I ended up deleting everything in eth0, which the system no longer recognizes as "connected" and entered the settings in eth1, saved and restarted network service. Now I am able to edit network settings from system admin and they are immediately reflected in the the network scripts.
Just rebooted and came up perfect!
I think this is an unlikely scenario, restoring snapshots to a different IP address or different vultr account. I am guessing this is what caused the issue.
No on to the FreepPBX 14 updates.
-
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Is your hardware address right? Duplicated MAC address might be an issue?
I ended up deleting everything in eth0, which the system no longer recognizes as "connected" and entered the settings in eth1, saved and restarted network service. Now I am able to edit network settings from system admin and they are immediately reflected in the the network scripts.
Just rebooted and came up perfect!
I think this is an unlikely scenario, restoring snapshots to a different IP address or different vultr account. I am guessing this is what caused the issue.
No on to the FreepPBX 14 updates.
This happens on a number of different distributions that I know of when restoring. The network adapter will pickup the next one in line, eth1 instead of eth0 in your case. I haven't been watching the boards here during the day at the moment, probably could've saved you some headache
-
@travisdh1 said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@jaredbusch said in FreePBX Restored from Vultr Snapshot - No IP on boot:
Is your hardware address right? Duplicated MAC address might be an issue?
I ended up deleting everything in eth0, which the system no longer recognizes as "connected" and entered the settings in eth1, saved and restarted network service. Now I am able to edit network settings from system admin and they are immediately reflected in the the network scripts.
Just rebooted and came up perfect!
I think this is an unlikely scenario, restoring snapshots to a different IP address or different vultr account. I am guessing this is what caused the issue.
No on to the FreepPBX 14 updates.
This happens on a number of different distributions that I know of when restoring. The network adapter will pickup the next one in line, eth1 instead of eth0 in your case. I haven't been watching the boards here during the day at the moment, probably could've saved you some headache
I would like to figure out where I could remove/repair the references to eth0 and delete eth1, but I am satisfied that I got it working for now. I believe it was because the hardware ID as @JaredBusch mentioned was in the eth0 profile, and no longer matched the mac address vultr was assigning it under the new account.
-
@bigbear
It's udev that has a rule with eth0 and the old mac address.
Don't know what distro you're running but try looking in /etc/udev/rules.d/70-persistent-net.rules.
Delete the line that has NAME="eth0" in it. And change the line with NAME="eth1" to eth0.
And then you have to swap back eth1 to eth0 in your network settings. -
@pete-s said in FreePBX Restored from Vultr Snapshot - No IP on boot:
@bigbear
It's udev that has a rule with eth0 and the old mac address.
Don't know what distro you're running but try looking in /etc/udev/rules.d/70-persistent-net.rules.
Delete the line that has NAME="eth0" in it. And change the line with NAME="eth1" to eth0.
And then you have to swap back eth1 to eth0 in your network settings.Perfect!
