Would ignorelb work on socomec double on-line conversion UPS
-
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
With just the upsd.conf modified for LISTEN interface and the upsd.users modified for synology, pulling the cord out of
the wall shows the following power-off times...pfsense - 48 secs
synology - 89.05 secs
apc ups - 91.58 secs
Is this a normal behavior with pfsense shutting down first followed by the synology then the ups? I thought it was the other way around, synology first before pfsense.The server waits for clients to initiate their shutdown (indicated by the client logging out of the server) rather than complete their shutdown. The server has no way to know how long a client actually takes to complete the shutdown. Once all clients have logged out, the server initiates its own shutdown following a short delay (FINALDELAY).
pfSense generally shuts down relatively quickly, while Synology shuts down very slowly. So yes, it's reasonable to expect that pfSense would complete its shutdown before the Synology does. Variable ups.delay.shutdown can be used to cover this. You could also use FINALDELAY, but since your UPS has the capability to control the power off delay I would use that instead.
One question: you list a "power-off" for the Synology of 89 seconds. Was this an actual power off, or achievement of quiescent mode?
WRT the socomec, I expect the UPS vendor knows what they are doing, so setting battery.protection to true is probably sufficient to maintain battery life. Also, be sure to set ups.delay.shutdown to a sufficient value to cover the Synology's shutdown. Maybe 100-120 seconds.
As to where you run the server, you can run the server on pfSense or on the pi. Which system is more reliable? If you choose the pi, keep in mind that it may shut down even faster than pfSense. If so, you'll need to allow a little extra time. The only thing I would not do is to use the Synology as the master.
HTH
-
This post is deleted! -
Regarding the synology quiescent mode, I am not sure about this. I just have my settings same as server on
time before server enters standby mode under the UPS tab of the synology. Would gladly check it if you could
show me how. Perhaps under var/log/messages on synology?Do i put this line in the ups conf or in the extra arguments to driver to control ther power off delay?
ups.delay.shutdown = 120or is it,
offdelay = 120in Extra Arguments to driver
or should i issue this command via the cli?
upsrw -s ups.delay.shutdown =120
Is there way of making the soscomec shutdown immediately just for testing purposes? Since the scomec is 2 kva, it may
take forever for it to shutdown wtih just the Pi as its load. Mindful of your advice to use igbnorelb only when UPS
declares battery immediately after the mains fail?Luckily, I did read your post on why not to run nut master on synology...
Thank you very much
-
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
Regarding the synology quiescent mode, I am not sure about this. I just have my settings same as server on
time before server enters standby mode under the UPS tab of the synology. Would gladly check it if you could
show me how. Perhaps under var/log/messages on synology?Standby mode is quiescent mode. Older version of Synology would actually power off, now they just shut down all the services and sit there.
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
or should i issue this command via the cli?
upsrw -s ups.delay.shutdown =120
This.
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
Is there way of making the soscomec shutdown immediately just for testing purposes? Since the scomec is 2 kva, it may
take forever for it to shutdown wtih just the Pi as its load.You can instruct the UPS to power off immediately via a NUT command, but that's different than the UPS declaring LB (Low Battery).
-
@dennypage thank you again
-
@chewie Most welcome!
-
@dennypage said in Would ignorelb work on socomec double on-line conversion UPS:
This.
upsrw -s ups.delay.shutdown =120doesn 't seem to persist across reboots. The ups dealy shutdown goes back to the deafualt value of 30. should i use the ..
offdelay = 120in ExtraArgument to driver instead? This one seem to persist across reboots.
Thank you again.
-
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
doesn 't seem to persist across reboots. The ups dealy shutdown goes back to the deafualt value of 30.
Can you clarify what you mean by "Across reboots"?
Does this refer to the reboot of the OS? Or reboot of the UPS? Or the restart of the NUT daemon or NUT UPS driver?
-
@dennypage said in Would ignorelb work on socomec double on-line conversion UPS:
Can you clarify what you mean by "Across reboots"?
Does this refer to the reboot of the OS? Or reboot of the UPS? Or the restart of the NUT daemon or NUT UPS driver?
Restarting the Daemon successfully showed the delay shutdown at 120 but not when you reboot the OS.
-
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
Restarting the Daemon successfully showed the delay shutdown at 120 but not when you reboot the OS.
Okay, that's kinda weird. Only thing I can think of would be that the UPS is reseting when the USB resets. You can confirm by pulling the USB cable out for a 5-10 seconds, and then plugging it back in.
[Edit: By "restarting the Daemon" you mean completely restarting NUT, yes?]
-
@dennypage I apologize, this is what i did...
upsrw -s ups.delay.shutdown =120and immediately the delay shutdown was set to 120 without me restarting nut with the circular arrow on the top right corner of pfsense. But the moment i hit that arrow the delay shutdown goes back to its original value of 30. Rebooting pfsense would still show the value at 30. I must be doing something wrong or not understanding something. Thank you very much
-
@chewie said in Would ignorelb work on socomec double on-line conversion UPS:
@dennypage I apologize, this is what i did...
upsrw -s ups.delay.shutdown =120and immediately the delay shutdown was set to 120 without me restarting nut with the circular arrow on the top right corner of pfsense. But the moment i hit that arrow the delay shutdown goes back to its original value of 30. Rebooting pfsense would still show the value at 30.
Apologies for the delay, I've been busy/offline.
So I expect what is happening is that the NUT driver is resetting the shutdown delay on start, even though you have not specified a value. Lots of little quirks like this in NUT drivers.
So yes, I would recommend setting the offdelay parameter in the Extra Arguments to driver section. You can confirm that it is correctly setting the value in the UPS by using the upsrw command to read from the UPS after restarting NUT.
