January 31, 201610 yr I had noticed that my webGUI was unresponsive; so I jumped on telnet and issued powerdown -r. Bear in mind this powerdown version is the plugin; as opposed to the built-in version that comes with unRAID. However the system would not reboot. I issued a ps -ux; and although there were no deprecated processes; I killed the main docker process and the system then rebooted. (I assume it was this that was stopping powerdown -r from continuing) I've attached the diagnostic logs. tower-diagnostics-20160131-1118.zip
January 31, 201610 yr It doesn't look like powerdown was initiated. Install this plugin http://lime-technology.com/forum/index.php?topic=42881.0 and follow the instructions at the bottom to find out what is causing the hang up. You also have a lot of these: Jan 31 11:13:01 Tower crond[1397]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null This is from one of the Dynamix plugins and you should figure it out to stop the flood of these log messages.
January 31, 201610 yr Author It doesn't look like powerdown was initiated. Install this plugin http://lime-technology.com/forum/index.php?topic=42881.0 and follow the instructions at the bottom to find out what is causing the hang up. You also have a lot of these: Jan 31 11:13:01 Tower crond[1397]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null This is from one of the Dynamix plugins and you should figure it out to stop the flood of these log messages. I've got the Open Files plugin installed. However; I cant take a look if emhttp / webGUI itself isnt responding? Log attached. syslog.zip
January 31, 201610 yr It doesn't look like powerdown was initiated. Install this plugin http://lime-technology.com/forum/index.php?topic=42881.0 and follow the instructions at the bottom to find out what is causing the hang up. You also have a lot of these: Jan 31 11:13:01 Tower crond[1397]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null This is from one of the Dynamix plugins and you should figure it out to stop the flood of these log messages. I've got the Open Files plugin installed. However; I cant take a look if emhttp / webGUI itself isnt responding? Log attached. Scroll to the bottom of the open files webpage and you'll see buttons that will shutdown unraid. The process is exactly the same as what powerdown does. Once that is completed you can then see the files open and the processes holding the files open. Click the 'Help' buttom for more information on the shutdown procedurre. I'll take a look at your log and see if there is anything obvious holding up the shutdown.
January 31, 201610 yr That log is not helpful. It does not show that powerdown was initiated. Apparently you are not getting far enough in the shutdown process for powerdown to archive a log.
January 31, 201610 yr You are manually loading the cache_dirs script from your go file. You need to remove that and install the dynamix cache dirs plugin. The old cache_dirs script is known to have issues when stopping the array. The dynamix cache dirs plugin fixes that.
February 2, 201610 yr Author I've removed the cache-dir script & the entry from the go file as well. Installed the dynamix plugin & restarting unRAID now. Re: Logs. I ran & subsequently pulled the diagnostic logs prior to running powerdown -r. I have a feeling its the docker process; because as soon as I killed the docker daemon the machine restarted (thus I assume its this process that was preventing powerdown -r from completing?) Lets see how we get on now.
Archived
This topic is now archived and is closed to further replies.