June 25, 201016 yr Hi, I have been having troubles lately when I powerdown my system from the Powerdown button within the unraid interface. I have APC installed and working fine as well as powerdown and unraid notify. Specifically, when I hit the button to shut everything down after stopping the array the system goes through it's powerdown procedures and then never actually turns off. It seems like this began happening after installing unraid notify; which does work properly as a side note. Or perhaps this is APC related? Here's the error message on screen in the terminal mode: Killpower requested in non-power fail condition or bug. Killpower request ignored at device .c:120 apcupsd[23340]: apcupsd error shutdown completed awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) /usr/bin/mail: line 55: /root/.forward: No such file or directory awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) awk: cmd. line:1:fatal: cannot open file '/boot/config/unraid_notify.cfg for reading (no such file or directory) System halted. I would sincerely appreciate any assistance in correcting this issue so that my system will powerdown properly. I have no idea what might be going wrong. Thanks... **Error Screen Photo Attached**
June 25, 201016 yr Do you have ACPI enabled in BIOS? If not, that could explain why the system remains running instead of actually turning off. You need ACPI enabled to have the system be able to turn off, otherwise it will just halt.
June 25, 201016 yr Author Hi, That's interesting because I recently turned that feature off to see if it had any effect on this and it still had the same issue. Another issue which also may be related to all of this that I noticed is that after an undetermined amount of time when acpi is enabled, the video output goes off and I cannot get it back on unless I reboot the server. So it seems that when acpi is disabled this problem goes away with the video. But also seems that having acpi on or off does not affect this powerdown problem as it still remains. I will test this again but I know the problem will most likely still exist. Any other ideas?
June 25, 201016 yr how did you install apcupsd? The script I wrote for unMENU adds a command to invoke killpower to the end of /etc/rc.0 if you are not rebooting. It is being ignored since you are not in a power fail mode. You can ignore those messages, they are quite normal and usually you would not see them since the server would power itself down in the next command. It sure looks like unraid_notify is looking for the unraid_notify.cfg file, and it does not exist. That again does not look related to your problem, but depending on if you edited /etc/rc.0, it might. As far as the actual power down. Try this. Stop the array log in via telnet, or on the system console and type: poweroff If the array does not power itself off, then you have ACPI disabled in the BIOS.
June 25, 201016 yr Author I will test the poweroff with ACPI enabled again. I am however a bit confused about your statement mentioning unMENU - are you stating that I should have installed something additional from the packages section in there? Also, I'm not sure what you mean by me editing the /etc/rc.0 - how would I have done this or would it have had to be something I knew what I was doing? Also, I have confirmed that the unraid_notify.cfg file does exist in the /config folder - and since it does send emails right now then it must be working properly right? Why would this error message be showing that the file doesn't exist when it actually does? Any Ideas on this? Also, any ideas on why the video output goes off after a while - any ideas on keyboard strokes to make it come back on? I thought that this was related to ACPI surrounding s3 sleep or something - but I really am not sure of why?
June 25, 201016 yr I will test the poweroff with ACPI enabled again.Without it enabled, the server will just halt, but not be able to power down. I am however a bit confused about your statement mentioning unMENU - are you stating that I should have installed something additional from the packages section in there?You did not say how you installed apcupsd. unMENU does what it need to do to invoke killpower, but immediately after that command is the one in /etc/rc.0 to power down the server. (but that won't work completely unless ACPI is enabled in the BIOS) Also, I'm not sure what you mean by me editing the /etc/rc.0 - how would I have done this or would it have had to be something I knew what I was doing?It was done for you when you installed apcupsd through unMENU. Also, I have confirmed that the unraid_notify.cfg file does exist in the /config folder - and since it does send emails right now then it must be working properly right? Why would this error message be showing that the file doesn't exist when it actually does? Any Ideas on this?No, you'll have to ask its author. Also, any ideas on why the video output goes off after a while - any ideas on keyboard strokes to make it come back on? I thought that this was related to ACPI surrounding s3 sleep or something - but I really am not sure of why? The video is configured to blank itself. I don't use S3, so can't help you there.
June 25, 201016 yr Author Since you state that the video is configured to blank itself - do you know how to turn it back on when needed? Thanks for the other answers
June 25, 201016 yr Since you state that the video is configured to blank itself - do you know how to turn it back on when needed? Thanks for the other answers I just press a key on the system console. You can use the "setterm" command to enable/disable the screen blanking See this link for full options: http://linux.die.net/man/1/setterm setterm -blank 0 -powersave off -powerdown 0 -blank [0-60] (virtual consoles only) Sets the interval of inactivity, in minutes, after which the screen will be automatically blanked (using APM if available). Without an argument, defaults to 0 (disable console blanking). -powersave [off] Turns off monitor VESA powersaving features. -powerdown [0-60] Sets the VESA powerdown interval in minutes. Without an argument, defaults to 0 (disable powerdown). If the console is blanked or the monitor is in suspend mode, then the monitor will go into vsync suspend mode or powerdown mode respectively after this period of time has elapsed.
June 25, 201016 yr There should be a sleep at least I think it was called sleep, but anyways you can change it in one of the config files. Don't ask me which one because that was forever ago that I remember tinkering with that. Found this doing a search in some of the linux forums May or may not be of any use but, in /etc/rc,d/rc.M I replace "/bin/setterm -blank 15 -powersave powerdown -powerdown 60" with "/bin/setterm -blank 0"
Archived
This topic is now archived and is closed to further replies.