thr3ads.net - Nut upsuser - [Nut-upsuser] The system doesn't shutdown [Oct 2015]

If this information is useful, please help other people find it:
Share via:

George Anchev

2015-Oct-26 22:10 UTC

[Nut-upsuser] The system doesn't shutdown

Yes:

Previous complete boot through shutdown
Oct 26 21:02:54 i7 upsdrvctl[1955]: Using subdriver: MGE HID 1.32
Oct 26 21:02:55 i7 upsdrvctl[1955]: Network UPS Tools - Generic HID driver
0.38 (2.7.1)
Oct 26 21:02:55 i7 upsdrvctl[1955]: USB communication driver 0.32
Oct 26 21:02:56 i7 upsdrvctl[1955]: Network UPS Tools - UPS driver
controller 2.7.1
Oct 26 21:02:56 i7 upsd[2226]: fopen /var/lib/ups/upsd.pid: No such file or
directory
Oct 26 21:02:56 i7 upsd[2226]: listening on ::1 port 3493
Oct 26 21:02:56 i7 upsd[2226]: listening on ::1 port 3493
Oct 26 21:02:56 i7 upsd[2226]: listening on 127.0.0.1 port 3493
Oct 26 21:02:56 i7 upsd[2226]: Connected to UPS [myups]: usbhid-ups-myups
Oct 26 21:02:56 i7 upsd[2226]: listening on 127.0.0.1 port 3493
Oct 26 21:02:56 i7 upsd[2226]: Connected to UPS [myups]: usbhid-ups-myups
Oct 26 21:02:56 i7 upsd[2227]: Startup successful
Oct 26 21:02:56 i7 upsmon[2228]: fopen /var/run/upsmon.pid: No such file or
directory
Oct 26 21:02:56 i7 upsmon[2229]: Startup successful
Oct 26 21:02:56 i7 upsd[2227]: User upsmaster@::1 logged into UPS [myups]
Oct 26 21:02:56 i7 upsmon[2228]: UPS: myups at localhost (master) (power value
1)
Oct 26 21:02:56 i7 upsmon[2228]: Using power down flag file
/etc/ups/killpower
Oct 26 21:04:51 i7 upsmon[2230]: UPS myups at localhost on battery
Oct 26 21:05:11 i7 upsmon[2230]: UPS myups at localhost on line power
Oct 26 21:12:57 i7 upsmon[2230]: Signal 15: exiting
Oct 26 21:12:57 i7 upsd[2227]: User upsmaster@::1 logged out from UPS
[myups]
Oct 26 21:12:57 i7 upsd[2227]: mainloop: Interrupted system call
Oct 26 21:12:57 i7 upsd[2227]: Signal 15: exiting
Oct 26 21:12:57 i7 upsdrvctl[3063]: Network UPS Tools - UPS driver
controller 2.7.1
Oct 26 21:13:03 i7 systemd-journal[459]: Journal stopped
        Current boot
Oct 26 21:18:23 i7 upsdrvctl[2446]: Using subdriver: MGE HID 1.32
Oct 26 21:18:23 i7 upsdrvctl[2446]: Network UPS Tools - Generic HID driver
0.38 (2.7.1)
Oct 26 21:18:23 i7 upsdrvctl[2446]: USB communication driver 0.32
Oct 26 21:18:25 i7 upsdrvctl[2446]: Network UPS Tools - UPS driver
controller 2.7.1
Oct 26 21:18:25 i7 upsd[2719]: fopen /var/lib/ups/upsd.pid: No such file or
directory
Oct 26 21:18:25 i7 upsd[2719]: listening on ::1 port 3493
Oct 26 21:18:25 i7 upsd[2719]: listening on ::1 port 3493
Oct 26 21:18:25 i7 upsd[2719]: listening on 127.0.0.1 port 3493
Oct 26 21:18:25 i7 upsd[2719]: Connected to UPS [myups]: usbhid-ups-myups
Oct 26 21:18:25 i7 upsd[2719]: listening on 127.0.0.1 port 3493
Oct 26 21:18:25 i7 upsd[2719]: Connected to UPS [myups]: usbhid-ups-myups
Oct 26 21:18:25 i7 upsd[2720]: Startup successful
Oct 26 21:18:25 i7 upsmon[2721]: fopen /var/run/upsmon.pid: No such file or
directory
Oct 26 21:18:25 i7 upsmon[2722]: Startup successful
Oct 26 21:18:25 i7 upsd[2720]: User upsmaster@::1 logged into UPS [myups]
Oct 26 21:18:25 i7 upsmon[2721]: UPS: myups at localhost (master) (power value
1)
Oct 26 21:18:25 i7 upsmon[2721]: Using power down flag file
/etc/ups/killpower

---
George Anchev

On Mon, Oct 26, 2015 at 10:55 PM, Roger Price <roger at rogerprice.org>
wrote:
> On Mon, 26 Oct 2015, George Anchev wrote:
>
> Hello,
>> I have been following the details in this article to configure my UPS:
>>
>> http://rogerprice.org/NUT.html
>>
>> However the system won't shutdown although file permissions look
ok:
>>
>> ls -alF /usr/sbin/ups*
>> -rwxr--r-- 1 upsd daemon 64984 Oct 15  2014 /usr/sbin/upsd*
>> -rwxr--r-- 1 upsd daemon 48584 Oct 15  2014 /usr/sbin/upsmon*
>> -rwxr--r-- 1 upsd daemon 31536 Oct 15  2014 /usr/sbin/upssched*
>> -rwxr--r-- 1 upsd daemon  1798 Oct 26 13:52 /usr/sbin/upssched-cmd*
>>
>> When plugging the cord the only notification is "on battery/ line
power"
>> in journalctl and nothing happens.
>>
>> When I run /usr/sbin/upssched-cmd as root the journal says:
>>
>> Oct 26 20:22:37 i7 upssched-cmd[19433]: Calling upssched-cmd
>> Oct 26 20:22:37 i7 upssched-cmd[19434]: Unrecognized command:
>>
>> However when trying su - upsd -c "/usr/sbin/upssched-cmd" I
don't get
>> this output in journalctl although the file permissions look ok.
>>
>> What might be wrong?
>>
>
> Could you show us the output of the utility script nut-journal ? Chapter
> 5.15 in the referenced article.
>
> 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/20151027/36412304/attachment-0001.html>

Roger Price

2015-Oct-27 15:57 UTC

head link

[Nut-upsuser] The system doesn't shutdown

On Tue, 27 Oct 2015, George Anchev wrote:
> Oct 26 21:02:56 i7 upsd[2227]: Startup successful
...> Oct 26 21:02:56 i7 upsmon[2229]: Startup successful
...> Oct 26 21:04:51 i7 upsmon[2230]: UPS myups at localhost on battery
> Oct 26 21:05:11 i7 upsmon[2230]: UPS myups at localhost on line power
Power was off for 20 seconds so you should have seen upssched activity. 
Could you run the nut-report utility which I have added to the "NUT on 
OpenSUSE" website in section 5.16. 
http://rogerprice.org/NUT.html#NUT_REPORT It probably has to be run as 
root.  This will generate a condensed presentation of your NUT 
configuration with passwords removed.

The output is a bit too much for an e-mail so the best way of presenting 
the result in file /tmp/NUT.report is to upload it to a free file hoster
such as filehosting.org and post the URL they give you here in this list.
You might want to use a throw-away e-mail address when dealing with 
filehosting.org.  I use Mailinator.com

Roger

George Anchev

2015-Oct-27 18:37 UTC

head link

[Nut-upsuser] The system doesn't shutdown

Yes, that was the power off test. However the upssched-cmd script gave
absolutely no signs of activity. Even it's logger lines don't show up in
journalctl. No any permission error messages - nothing. Only the 2 messages
from upsmon - on battery and then on line power.

Here is the nut-report:

http://www.filehosting.org/file/details/518300/NUT.report

---
George Anchev

On Tue, Oct 27, 2015 at 5:57 PM, Roger Price <roger at rogerprice.org>
wrote:
> On Tue, 27 Oct 2015, George Anchev wrote:
>
> Oct 26 21:02:56 i7 upsd[2227]: Startup successful
>>
> ...
>
>> Oct 26 21:02:56 i7 upsmon[2229]: Startup successful
>>
> ...
>
>> Oct 26 21:04:51 i7 upsmon[2230]: UPS myups at localhost on battery
>> Oct 26 21:05:11 i7 upsmon[2230]: UPS myups at localhost on line power
>>
>
> Power was off for 20 seconds so you should have seen upssched activity.
> Could you run the nut-report utility which I have added to the "NUT on
> OpenSUSE" website in section 5.16.
> http://rogerprice.org/NUT.html#NUT_REPORT It probably has to be run as
> root.  This will generate a condensed presentation of your NUT
> configuration with passwords removed.
>
> The output is a bit too much for an e-mail so the best way of presenting
> the result in file /tmp/NUT.report is to upload it to a free file hoster
> such as filehosting.org and post the URL they give you here in this list.
> You might want to use a throw-away e-mail address when dealing with
> filehosting.org.  I use Mailinator.com
>
>
> 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/20151027/e2f235aa/attachment.html>

Apparently Analagous Threads

Search for more seemingly similar threads

Nut upsuser - Oct 2015 - The system doesn't shutdown

[Nut-upsuser] The system doesn't shutdown

[Nut-upsuser] The system doesn't shutdown

[Nut-upsuser] The system doesn't shutdown

Apparently Analagous Threads