June 16, 20179 yr I tried stop the array prior to wanting to reboot and the web UI stopped responding. It managed to stop my vm's but I had to just reboot as typing powerdown had no effect. This was the last thing I saw while waiting for the UI to start responding again. Jun 17 00:19:37 Tower kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 tower-diagnostics-20170617-0026.zip
June 18, 20179 yr On 6/16/2017 at 5:44 PM, Tuftuf said: I tried stop the array prior to wanting to reboot and the web UI stopped responding. It managed to stop my vm's but I had to just reboot as typing powerdown had no effect. This was the last thing I saw while waiting for the UI to start responding again. Jun 17 00:19:37 Tower kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 tower-diagnostics-20170617-0026.zip You didnt happen to play with manually assigning ip addresses to dockers from the command line. I had seen that error a week ago or so and I thought it was related. I was on 6.3 I believe though. My server was hard freezing randomly at least once a day. The only thing I had done was upgrade/rebuild a drive and try and run a docker on it's own ip. Have since upgraded the power supply from a 450 to 600 and removed the docker network. No More freezes. Power supply is working fine in new backup server. Edited June 18, 20179 yr by dmacias
June 18, 20179 yr 7 minutes ago, bonienl said: What specific problem with Docker and manual IP assignment? This was before it was integrated it into the gui. I have not tried again. I was using the using the manual command line method from the original docker ip thread. I was seeing the same unregister netdevice. I edited my post to reflect command line method. Edited June 18, 20179 yr by dmacias
June 24, 20179 yr Author I have not been making changes on the command line with docker. The issue did not happen again.
Archived
This topic is now archived and is closed to further replies.