March 2, 201511 yr Did anyone ever find a fix for this issue - the computer powering itself back on after a shutdown? I still experience this on occasions I have looked at BIOS setting (SuperMicro X9SCM-iiF) and I don't believe that I have any 'wake on' settings enabled. I have the same board. Under your BIOS settings Advanced/Boot Feature/Restore on AC Power Loss - make sure it is set to Power-Off. If set to Power-On it will power back on when power is restored, and if set to Last State it will power back on if the system was powered up when power was lost.
March 2, 201511 yr Did anyone ever find a fix for this issue - the computer powering itself back on after a shutdown? I still experience this on occasions I have looked at BIOS setting (SuperMicro X9SCM-iiF) and I don't believe that I have any 'wake on' settings enabled. I have the same board. Under your BIOS settings Advanced/Boot Feature/Restore on AC Power Loss - make sure it is set to Power-Off. If set to Power-On it will power back on when power is restored, and if set to Last State it will power back on if the system was powered up when power was lost. Err... but I want it to power back on after the power goes off and comes back on. The problem is that, when shutting down, the computer turns off and then, after about two seconds, it turns back on again before the UPS has cut the power. This means that it is part way through the boot sequence when the UPS does turn the power off.
March 3, 201511 yr Author I think (mostly guessing) that if you change the BIOS, the computer won't turn itself back on, but if you set the UPS to turn the computer back on, that might work. I hope it does work for you, since I know you have very frequent power issues there, so i can only imagine how frustrating it must be.
March 3, 201511 yr Did anyone ever find a fix for this issue - the computer powering itself back on after a shutdown? I still experience this on occasions I have looked at BIOS setting (SuperMicro X9SCM-iiF) and I don't believe that I have any 'wake on' settings enabled. I have the same board. Under your BIOS settings Advanced/Boot Feature/Restore on AC Power Loss - make sure it is set to Power-Off. If set to Power-On it will power back on when power is restored, and if set to Last State it will power back on if the system was powered up when power was lost. Err... but I want it to power back on after the power goes off and comes back on. The problem is that, when shutting down, the computer turns off and then, after about two seconds, it turns back on again before the UPS has cut the power. This means that it is part way through the boot sequence when the UPS does turn the power off. Does your system do this (power back up) every time or just every once in a while? (I know you have this great power environment down there ..... ) Edit: Opps I see you already answered that above. I missed it. My bad.
March 3, 201511 yr Did anyone ever find a fix for this issue - the computer powering itself back on after a shutdown? I still experience this on occasions I have looked at BIOS setting (SuperMicro X9SCM-iiF) and I don't believe that I have any 'wake on' settings enabled. I have the same board. Under your BIOS settings Advanced/Boot Feature/Restore on AC Power Loss - make sure it is set to Power-Off. If set to Power-On it will power back on when power is restored, and if set to Last State it will power back on if the system was powered up when power was lost. Err... but I want it to power back on after the power goes off and comes back on. The problem is that, when shutting down, the computer turns off and then, after about two seconds, it turns back on again before the UPS has cut the power. This means that it is part way through the boot sequence when the UPS does turn the power off. Does your system do this (power back up) every time or just every once in a while? (I know you have this great power environment down there ..... ) Not every time, but I get the impression that the frequency is increasing! If I turn the computer off, and it stays off for more than a couple of seconds, it behaves as it should - will only turn on when power is cycled or the power button is pushed. I have only witnessed the problem when the shutdown is under apcupsd control - but that accounts for 99% of shutdowns. That has been with five different APC units - two different models. Perhaps I should try a series of tests, powering down from the web gui and/or command line and/or IPMI to see whether it can occur in other circumstances.
March 3, 201511 yr PeterB, I just setup apcupsd earlier today and have been experimenting with it mostly so I can get familiar with the way it operates. No expertise here, at least not yet. I have it working now with an APC SmartUPS 1500 that has USB as well as with an AP9619 (ether). I have gotten the UPS to successfully shutdown unRAID using either USB or via the AP9619 using PCNET. Through the AP9619 I can also access the UPS web server and all it's internal settings and logs (nice). But it is not shutting the UPS off even though "Turn Off UPS After Shutdown" is set to Yes. I also just noticed I am getting error messages on the console when doing a "Normal" shutdown via the webgui when "Turn Off UPS" is set to yes. I have captured them with a camera, but would prefer to capture a syslog of the shutdown if you or someone else can point me to proper procedure. Using USB I am getting a "Killpower requested in non-power fail condition or bug" error message. It occurs right before power turn off on the computer. It causes a small delay in the shutdown process but not enough to notice especially it you are headless. Using PCNET I am getting a different error message "Unable to open UPA device for hibernate or shutdownapcupsd[2827] apcupsd FATAL ERROR in apcupsd.c at line 232". In this case there is a very noticeable delay in the shutdown of about 65 additional seconds. In either case the UPS does not shutdown. If I set "Turn Off UPS" to No I get a normal system shutdown with no error messages or delays with apcupsd enabled. This may or may not have anything to do with the OP or your intermittent problem PeterB but it does need checking out in any case. .
March 4, 201511 yr Using USB I am getting a "Killpower requested in non-power fail condition or bug" error message. It occurs right before power turn off on the computer. It causes a small delay in the shutdown process but not enough to notice especially it you are headless. Okay, I suspect that this error message is indicating the nature of the problem. Before apcupsd issues the killpower command to the UPS, it creates a flag file called 'powerfail'. If this file is not present, at the time the killpower is issued, then it is believed that the system is not in a power failure situation amd the killpower is refused. The location for this file is specified in /etc/apcupsd/apcupsd.con, as PWRFAILDIR. The default location in the apcupsd distribution included with unRAID v6b14 is /etc/apcupsd - which is where the error message indicates. It would seem that, for some reason, apcupsd is not able to find this file when it attempts the killpower command - most likely the file has not been created. As to why this should be, I cannot say - do you do anything out of the ordinary to the files/directories in this area? You could try creating the file manually and them pulling the power from your UPS. Hopefully, this would result in a shutdown followed by the UPS turning off. Ah, one thought, off the top of my head - could it be that you are still loading the third-party apcupsd plugin, as distributed by dlandon? This is no longer necessary - the plugin functionality is included in the latest v6 betas and loading the old plugin may cause a conflict. Using PCNET I am getting a different error message "Unable to open UPA device for hibernate or shutdownapcupsd[2827] apcupsd FATAL ERROR in apcupsd.c at line 232". In this case there is a very noticeable delay in the shutdown of about 65 additional seconds. I am unfamiliar with PCNET. If I set "Turn Off UPS" to No I get a normal system shutdown with no error messages or delays with apcupsd enabled. This may or may not have anything to do with the OP or your intermittent problem PeterB but it does need checking out in any case. I think that it has very little to do with the intermittent restart issue which I experience. I do notice one other error message in your screen shots. There is a fault in the v6beta14b image - the execution permission is not set for the apcupsd.notify script. Try using this command (I have placed it in my go file as a temporary measure): chmod +x /usr/local/emhttp/plugins/apcupsd/apcupsd.notify That should remove the 'Permission denied' errors.
March 4, 201511 yr Using USB I am getting a "Killpower requested in non-power fail condition or bug" error message. It occurs right before power turn off on the computer. It causes a small delay in the shutdown process but not enough to notice especially it you are headless. Okay, I suspect that this error message is indicating the nature of the problem. Before apcupsd issues the killpower command to the UPS, it creates a flag file called 'powerfail'. If this file is not present, at the time the killpower is issued, then it is believed that the system is not in a power failure situation amd the killpower is refused. The location for this file is specified in /etc/apcupsd/apcupsd.con, as PWRFAILDIR. The default location in the apcupsd distribution included with unRAID v6b14 is /etc/apcupsd - which is where the error message indicates. It would seem that, for some reason, apcupsd is not able to find this file when it attempts the killpower command - most likely the file has not been created. As to why this should be, I cannot say - do you do anything out of the ordinary to the files/directories in this area? You could try creating the file manually and them pulling the power from your UPS. Hopefully, this would result in a shutdown followed by the UPS turning off. Ah, one thought, off the top of my head - could it be that you are still loading the third-party apcupsd plugin, as distributed by dlandon? This is no longer necessary - the plugin functionality is included in the latest v6 betas and loading the old plugin may cause a conflict. Using PCNET I am getting a different error message "Unable to open UPA device for hibernate or shutdownapcupsd[2827] apcupsd FATAL ERROR in apcupsd.c at line 232". In this case there is a very noticeable delay in the shutdown of about 65 additional seconds. I am unfamiliar with PCNET. If I set "Turn Off UPS" to No I get a normal system shutdown with no error messages or delays with apcupsd enabled. This may or may not have anything to do with the OP or your intermittent problem PeterB but it does need checking out in any case. I think that it has very little to do with the intermittent restart issue which I experience. I do notice one other error message in your screen shots. There is a fault in the v6beta14b image - the execution permission is not set for the apcupsd.notify script. Try using this command (I have placed it in my go file as a temporary measure): chmod +x /usr/local/emhttp/plugins/apcupsd/apcupsd.notify That should remove the 'Permission denied' errors. This is from my Testbed system, which I initially did a clean install of 6.0B12 two weeks ago followed by updates to 6.0B14, 6.0N14a and 6.0B14b. It never previous third party apcupsd plugin installed at any time. Everything is stock. I am using this system to get myself caught up on the 6.0 betas having been away from all of this since June of last year. I am aware of the fact that the previous apcupsd plugin is no longer needed and should not be installed. Also I have noted a number of posts related to problems with notifications. This could also be related to those issues. However, I have not done anything to configure notifications on this system yet. That is still on my ToDo list. For now I will leave these two areas (apcupsd and notifications) alone in case LT wants to have a look at it or try something. It is repeatable. You are correct this probably has nothing to do with your restart problem. I don't have any more ideas what is causing your problem. Intermittent problems of that nature are always a real pain to track down. Has this problem occurred again since you got your latest ups replacement unit? But this does seem to be related to the OP but with a different result. Perhaps this post should be moved to its own thread, but I will leave that to others more aware of the issues at hand to decide. Capturing the screen shots was difficult as the error messages are displayed for only a second or two before the system powers off. So I thought it best to get the information posted regardless. PCNET is just another way of doing the same thing you are doing with USB for except communications is over ethernet using AP9617/19 network management cards in the smart slot.
Archived
This topic is now archived and is closed to further replies.