codec Posted September 16, 2015 Share Posted September 16, 2015 Original Subject: ping, webUI, telnet and shares down - ping from console works Been running unraid since version 4 using same basic hardware and thumbdrive. Upgraded to v6 2 weeks ago. Setup a few dockers and vm's, everything was wonderful. About a week after the upgrade I started noticing that the webUI would go down and i would have to either reboot the server (via power button, or ssh) about once a day. I just dealt with it for the time being. A few days later (in an unrelated effort) I upgraded my router (which used a different dhcp scope). After the router replacement I lost all access to webUI, ssh and shares. Troubleshooting: I connected a monitor and keyboard locally and confirmed via console ifconfig command that the server was pulling the correct ip address from the new router. Checked the usb's network.cfg file to ensure that dhcp was enabled. I can access various docker webUI's just fine. While running a continuous ping on the server during bootup there are several seconds where the server replies to pings but within about 30 seconds it stops responding to pings. I can ping my router and internet ip's from the server console. Looking at the logs the only worrisome message i see concerning eth0 is this: Sep 16 15:23:18 Tower kernel: forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x1c1 @ 1, addr 00:1d:92:2e:74:02 Not sure what "forcedeth" is but it sounds bad . . . . The following forum posts looked promising but upon reading seemed unrelated: http://lime-technology.com/forum/index.php?topic=42855.0 http://lime-technology.com/forum/index.php?topic=42319.0 This topic seems similar but no solution yet: http://lime-technology.com/forum/index.php?topic=42865.0 I have attached the diagnostics zip. tower-diagnostics-20150916-1523.zip Link to comment
codec Posted September 18, 2015 Author Share Posted September 18, 2015 It just dawned on me to try booting in safe mode. That didn't work either. Still no webUI, ping or shares. Link to comment
codec Posted September 18, 2015 Author Share Posted September 18, 2015 After reading a few more forum posts I am now suspecting that my issues are caused by emhttp (and other services) running out of memory. I had several containers set to load on startup and I think that one of them is causing the memory issues. I can't find a way to disable the auto-start of containers. I can only find a way to disable docker completely (via docker.cfg). After disabling docker I can access the webUI and telnet. However, the only way I know to disable auto start on all the containers is via the docker tab in webUI. When I re-enable the docker all the containers start up, the system runs out of memory and I lose my connection. Is there an easy way to disable all containers from auto-starting from the CLI or a config file? Then I can begin to troubleshoot which docker is causing the issue. Link to comment
mr-hexen Posted September 18, 2015 Share Posted September 18, 2015 Stop docker via cmd line like you have. Rename docker.img to something else. start docker. This will cause the docker.img to rebuild (meaning re-download the images from the repo's). This MIGHT allow you enough time to get to the docker manager page and fix your settings. Link to comment
codec Posted September 19, 2015 Author Share Posted September 19, 2015 That worked mr-hexen. Thanks. Rebuilding my containers now. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.