Dinow Hsieh
2017-May-17 08:55 UTC
[Nut-upsuser] Fw: [Nut-upsdev] POWERCOM-UPS-USB : UPS Shutdown
Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without certificate database battery.charge: 32 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/12/20 battery.runtime: 256 battery.type: PbAc device.mfr: POWERCOM Co.,LTD device.model: HID UPS Battery device.serial: 004-0D9F-000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.1 driver.version.data: PowerCOM HID 0.4 driver.version.internal: 0.38 input.frequency: 0.0 input.voltage: 0.0 output.frequency: 60.0 output.voltage: 110.0 ups.beeper.status: disabled ups.date: 2010/12/20 ups.delay.shutdown: 20 ups.delay.start: 60 ups.load: 58 ups.mfr: POWERCOM Co.,LTD ups.model: HID UPS Battery ups.productid: 0004 ups.serial: 004-0D9F-000 ups.status: OB DISCHRG TRIM ups.test.result: Done and passed ups.timer.shutdown: 169 ups.timer.start: 755760 ups.vendorid: 0d9f ---------------------------------------------------------------------------------------- BB. I wonder where the ups.delay.start: 60 comes from. The NUT default value is 30 secs, and you do not change the value in ups.conf. ==> I tried below set-command but it react fail dinow-All-Series:~# upsrw -s "ups.delay.shutdown"="30" -u pcmups pcmups at localhost Password: Unexpected response from upsd: ERR ACCESS-DENIED ==> Are there any behaviors that I should confirm ? ---------------------------------------------------------------------------------------- CC. Does a Ubuntu user with no xterm window open see the message as part of the ==> The root and remote user(ssh-putty) get the broadcasting message all from terminal-window ---------------------------------------------------------------------------------------- DD. I have tried below commands and the ups actually works (Battery test and Beeper ON/OFF) dinow-All-Series:~# upscmd -l pcmups Instant commands supported on UPS [pcmups]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.toggle - Toggle the UPS beeper load.on - Turn on the load immediately load.on.delay - Turn on the load with a delay (seconds) shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off test.battery.start.quick - Start a quick battery test dinow-All-Series:~# upscmd pcmups test.battery.start.quick Username (root): pcmups Password: OK ==> The ups run battery mode dinow-All-Series:~# upscmd pcmups beeper.disable Username (root): pcmups Password: OK ==> The ups turn off it beeper when its on battery mode ==> However, I command center 5 (load.on / delay / shutdown return / stay off) but no any reaction occur If you have any questions, please don't hesitate to inform us. Sincerely yours, May. 17th Dinow Hsieh ----- Original Message ----- From: "Roger Price" <roger at rogerprice.org> To: "nut-upsuser Mailing List" <nut-upsuser at lists.alioth.debian.org> Sent: Tuesday, May 16, 2017 5:24 PM Subject: Re: [Nut-upsuser] Fw: [Nut-upsdev] POWERCOM-UPS-USB : UPS Shutdown> On Tue, 16 May 2017, Dinow Hsieh wrote: > >> BB. Could you show us the output of command "upsc pcmups"? >> >> ==> Yes. Below 2 mode were the outputs of command "upsc pcmups" >> >> battery.charge: 100 >> battery.charge.low: 10 >> battery.charge.warning: 30 >> battery.date: 2010/12/20 > ... >> ups.date: 2010/12/20 >> ups.load: 4 > ... >> ups.status: OB DISCHRG > > Is this battery really 6.5 years old? Is this part of the problem? One > would not expect such a battery to support any load. I notice that during > the test, you have little or no load, since despite being in state OB > DISCHRG the battery.charge is still 100. It's best to perform such tests > with a dummy load such as a table lamp and an old fashioned incandescent > 100 watt bulb. > >> ups.delay.shutdown: 20 >> ups.delay.start: 60 > > I wonder where the ups.delay.start: 60 comes from. The NUT default value > is 30 secs, and you do not change the value in ups.conf. > >> DD. Does wall successfully notify the users on an Ubuntu system? If you >> type >> >> echo "Hello from wall" | wall >> >> do the users of Gnome, KDE, LXDE, LightDM etc see the message? >> >> ==> Yes. I used the putty and got below 3 messages >> (Battery Power / Power Resotre / and type commands directly) >> >> >> D3. Broadcast Message from dinow-Al >> (/dev/pts/0) at 11:02 ... >> >> Hello from wall > > I'm guessing that this output is in an xterm window or something similar. > It shows that wall is working but does not show that the wall->Gnome, > wall->KDE, wall->LXDE, wall->LightDM interfaces are working. Does a > Ubuntu user with no xterm window open see the message as part of the > system notifications? > > Roger--------------------------------------------------------------------------------> _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170517/5bb10fcf/attachment.html>
On Wed, 17 May 2017, Dinow Hsieh wrote:> ---------------------------------------------------------------------------------------- > CC. Does a Ubuntu user with no xterm window open see the message as part of > the > > ==> The root and remote user(ssh-putty) get the broadcasting message all > from terminal-windowSince all the users have xterm access, there's no problem. To get back to your original problem that the delayed shutdown of the UPS did not happen, and that the power outlets were not disconnected.> NUT 2.7.4 includes file .../scripts/systemd/nutshutdown . Does Ubunti > install this?> ==> Yes. Ubuntu haved installed this as below contents> dinow-All-Series:/lib/systemd/system-shutdown$ cat nutshutdown > #!/bin/sh > /sbin/upsmon -K >/dev/null 2>&1 && /sbin/upsdrvctl shutdownIt would be interesting to know if this script is really executed on a system shutdown. Try adding line logger -t upsdrvctl "Calling for delated UPS shutdown" The difficulty is that the NUT script is called very late when logging is probably no longer possible. For this reason, I don't use the NUT nutshutdown script. I prefer a systemd service unit # nut-delayed-ups-shutdown.service [Unit] Description=Initiate delayed UPS shutdown Before=umount.target DefaultDependencies=no [Service] Type=oneshot ExecStart=/usr/bin/logger -t upsdrvctl "nut-delayed-ups-shutdown.service calling upsdrvctl to shut down UPS unit" ExecStart=/usr/lib/ups/driver/upsdrvctl shutdown [Install] WantedBy=final.target This service unit needs to be enabled with a command such as systemctl --system reenable /etc/systemd/system/nut-delayed-ups-shutdown.service Roger