Power outage - Can't ping Fog Server after reboot

[mesaman0182]

So I have Fog server running on a VM via VirtualBox. The server lost power so I had to restart everything. Now I can’t login nor ping my Fog server IP. I don’t have a Ubuntu GUI so I am wondering how I can fix this via command line. Can someone help me out?

[george1421]

@mesaman0182 If you are on the fog server linux console can you ping something else on your network? Can you ping an adjacent VM on the same VM host server?

[mesaman0182]

@george1421 From Linux I cannot ping anything. Everything else is communicating fine so its not a network issue.

[mesaman0182]

Should I reinstall Fog? If so, does it wipe out my images directory? I ask this because I now have my new NAS appliance installed and I have a spare server that’s been decommissioned that I could setup with Ubuntu and install Fog on with a storage node install type.

[george1421]

@mesaman0182 said in Power outage - Can't ping Fog Server after reboot:

Should I reinstall Fog?

No this sounds like a network issue (maybe not with cabling). So on the fog server what do you get when you key in ip a s You should get a list of network interfaces with IP addresses. Please post a snapshot of this output here. Hopefully you have the FOG sever configured at a static IP address.

In virtual box itself. Confirm that you have the FOG server vm’s nic bridged to the physical network adapter.

Are there any other VMs running on this virtualbox host? If so, confirm that they will ping a physical device on the network.

We need to isolate the issue down to this specific linux VM.

[mesaman0182]

@george1421

The VM nic is bridged. No other VMs running on the host.

By the way, I am setting up another Fog server to replace this one as its on my to-do list. What Ubuntu version is preferred; Ubuntu desktop or server?

[george1421]

@mesaman0182 Ubuntu server is preferred. Stick to 20.04 for now. FOG has not been tested with 21.04. I hear there are a few bugs since Ubuntu changed quite a bit between the two versions.

So 10.118.0.59/16 is valid for your network?

It would be interesting to see if arp -a would return any hear arp requests. These settings look good, it should be working.