J.Nerdy Posted August 24, 2019 Share Posted August 24, 2019 (edited) I am having some troubles with server After completing a move with Unbalance, I went to start VM and GUI hung. Went to terminal and used 'reboot' to gracefully restart server. Server came back online, but without a GUI. I can ssh into server and browse directories. However, now when I issue reboot | power down commands from terminal, console just hangs with no change to server state. I can kill the session and reconnect via ssh, but can not kill/reboot server. Any advice appreciated (accessing remotely right now). nerdyraid-diagnostics-20190823-1947.zip Edited August 24, 2019 by J.Nerdy Quote Link to comment
Squid Posted August 24, 2019 Share Posted August 24, 2019 Shouldn't be related, but your schedule you've set for the auto turbo mode is not a valid cron entry Aug 23 07:18:01 nerdyRAID crond[2030]: failed parsing crontab for user root: 12:30 /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 600 > /dev/null 2>&1 And this spams your log every minute Quote Link to comment
J.Nerdy Posted August 24, 2019 Author Share Posted August 24, 2019 I will ASAP. any idea of how to gracefully shutdown server? Or get get back to GUI? thanks. Quote Link to comment
J.Nerdy Posted August 24, 2019 Author Share Posted August 24, 2019 17 minutes ago, Squid said: powerdown -r same result just hangs the console I top'd and it looks like docker daemon is hanging ... when I thought I had rebooted previously it did not take... it just hung... as uptime is uninterrupted. Is there a way to kill docker service from command line? I found /etc/rc.d/rc.docker stop .... but this hung the console too. I tried stopping array with wget -qO /dev/null http://localhost:$(lsof -nPc emhttp | grep -Po 'TCP[^\d]*\K\d+')/update.htm?cmdStop=Stop The command takes in console... but the array is still up since I can browse shares. Quote Link to comment
Squid Posted August 24, 2019 Share Posted August 24, 2019 It won't be clean, but either reboot or echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger should work Quote Link to comment
J.Nerdy Posted August 24, 2019 Author Share Posted August 24, 2019 (edited) I was able to get to server and do a hard reboot... neither command above worked. GUI is back up... will fix CA turbo. It was definitely something with Docker service... since HTOP was getting riddled with processes regarding trying to stop Running a parity check. I assumed that a parity check would start automatically... it seems an unclean shutdown was not detected? Should I run a check? Edited August 24, 2019 by J.Nerdy Quote Link to comment
BRiT Posted August 24, 2019 Share Posted August 24, 2019 You have a Zombie process (State Z) that's prob preventing a graceful shutdiwn. 10664 nobody 20 0 0 0 0 Z 0.0 0.0 1:56.54 Plex Medi+ Quote Link to comment
J.Nerdy Posted August 24, 2019 Author Share Posted August 24, 2019 Just now, BRiT said: You have a Zombie process (State Z) that's prob preventing a graceful shutdiwn. 10664 nobody 20 0 0 0 0 Z 0.0 0.0 1:56.54 Plex Medi+ thank you! That was spamming HTOP... should have known. Hard reset... but system did not detect unclean shutdown... that seems odd. I did try to manually stop array. Quote Link to comment
J.Nerdy Posted August 24, 2019 Author Share Posted August 24, 2019 2 hours ago, Squid said: Shouldn't be related, but your schedule you've set for the auto turbo mode is not a valid cron entry Aug 23 07:18:01 nerdyRAID crond[2030]: failed parsing crontab for user root: 12:30 /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 600 > /dev/null 2>&1 And this spams your log every minute Removed the erroneous schedule. Don't know how I missed that in logs. Thank you. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.