October 2, 20169 yr I'm assuming this is hardware since it doesn't happen to my other server but after not using it for a while (it's new so nothing is running) I try to browse to the web interface and I get it can't connect. If I keep refreshing it comes back after a few (5-10 seconds) but it's annoying. Is something going to sleep and waking up? What would this be called if it was a bios feature?
October 2, 20169 yr Please first post diagnostics and syslogs. We can't help you if we don't know what emhttp is doing in the background.
October 2, 20169 yr Please first post diagnostics and syslogs. We can't help you if we don't know what emhttp is doing in the background. No need to post syslogs since they are already included in diagnostics.
October 2, 20169 yr Author Just happened again, here are the diagnostics. skylon-diagnostics-20161002-1749.zip
October 3, 20169 yr Author I don't know if it's unraid or something hardware related but it's annoying because it closes VNC too.
October 7, 20169 yr Looks like one of your NIC's is getting disabled? br0: port 2(vnet0) entered disabled state
October 9, 20169 yr Author Looks like one of your NIC's is getting disabled? br0: port 2(vnet0) entered disabled state Is this an unraid/vm thing or bios? So it appears others have had this issue and everyone thinks it's a kernal/unraid issue. This has been going on for years and no solution?
October 23, 20169 yr Author So now I can't get to the server...at all. Strange enough I can get to the Windows VMS on the unraid box but not ssh or the web interface. This pretty much tells me it's an unraid thing. How can I access the Vm on the same box but not ssh in? To be clear, it's a different ip but there is only one network card in the system. Update: So I can't get to it from other machines but if i'm on the physical machine but in the windows vm (hooked up to the monitor) I can get to unraid.
October 25, 20169 yr Author An update in case this helps someone else. After pulling my hair out I randomly tried something the other night, changing the static up to a high value. It was .35 I changed it to .135 and so far everything is stable. So, I guess another device was also trying to use that ip and it collided, maybe it's time to read more about using static/dhcp on the same network.
October 25, 20169 yr Everything on my network is DHCP, and then I reserve IP addresses on the router by MAC address. That way everything has a known IP address, but I can maintain all of them in the router.
October 25, 20169 yr Author Everything on my network is DHCP, and then I reserve IP addresses on the router by MAC address. That way everything has a known IP address, but I can maintain all of them in the router. The fios router I have now sucks, once I get the network cards I ordered I'm building an fpsense box and I'll probably do this. Makes it easier I guess.
Archived
This topic is now archived and is closed to further replies.