Did I Find a Bug?

Status
Not open for further replies.

NASbox

Guru
Joined
May 8, 2012
Messages
650
While testing a rebuild of my FreeNAS, I booted without the network cable plugged in.

I plugged the cable in, and the DHCP assigned an IP Address as expected, but I was not able to log into the WebGUI.

I took the extra step of ifconfig em0 down/ifconfig em0 up from the system console, but the WebGUI was still not responsive.

I had to do a reboot before I was able to log in.

I was running FreeNAS v11U3, but then I noticed there was an update to U4. I installed it, but it didn't correct the problem.

After executing the command service nginx start, I was able to access the WebGUI.

Is failure of the WebGUI expected behaviour in the event network connectivity is delayed to some time after boot finishes?

Thanks in advance for any input/suggestions.
 

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
This sounds like typical behavior. Nginx typically binds to all interfaces (example: igb0, re0, or whatever). If a interface is not available at boot, then Nginx may fail to start.
 
Status
Not open for further replies.
Top