<div dir="ltr">Roger,<div> here is my output of ps -elf |grep upssched</div><div><br></div><div>root@nutpi:~# ps -elf |grep upssched<br>0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00 grep upssched<br></div><div><br></div><div>No timer, just the grep of upssched.. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 27, 2020 at 4:27 AM <<a href="mailto:nut-upsuser-request@alioth-lists.debian.net">nut-upsuser-request@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Nut-upsuser mailing list submissions to<br>
<a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:nut-upsuser-request@alioth-lists.debian.net" target="_blank">nut-upsuser-request@alioth-lists.debian.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:nut-upsuser-owner@alioth-lists.debian.net" target="_blank">nut-upsuser-owner@alioth-lists.debian.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Nut-upsuser digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Timer doesn't appear to start (Roger Price)<br>
2. Re: System with MGE UPS shuts down too early (nicolae788)<br>
3. Re: System with MGE UPS shuts down too early (Georgi D. Sotirov)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 27 Jan 2020 09:31:49 +0100 (CET)<br>
From: Roger Price <<a href="mailto:roger@rogerprice.org" target="_blank">roger@rogerprice.org</a>><br>
To: nut-upsuser Mailing List <<a href="mailto:nut-upsuser@lists.alioth.debian.org" target="_blank">nut-upsuser@lists.alioth.debian.org</a>><br>
Subject: Re: [Nut-upsuser] Timer doesn't appear to start<br>
Message-ID: <alpine.LSU.2.20.2001270913440.5507@titan><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed<br>
<br>
On Sun, 26 Jan 2020, Greg Treantos wrote:<br>
<br>
> I have a Raspberry PI that I have connected to a Deltec UPS via serial <br>
> (upscode2 driver). ... On the old OS when I pull the power I would see a <br>
> message in the syslog that a timer was set. On the new system I never see that <br>
> message.<br>
<br>
> here is my upssched.conf<br>
> CMDSCRIPT /bin/upssched-cmd<br>
> PIPEFN /home/nutmon/upssched/upssched.pipe<br>
> LOCKFN /home/nutmon/upssched/upssched.lock<br>
> AT COMMBAD deltec-PRA1500@localhost START-TIMER upsgone 10<br>
> AT ONBATT deltec-PRA1500@localhost START-TIMER upsonbat 60<br>
<br>
When a timer is running, the ps command will show that upssched is running. <br>
For example, I have timers running 24hrs to operate a "heartbeat" function, and <br>
at any time the command "ps -elf | grep upssched" reports<br>
<br>
1 S upsd 2962 1 00:00:18 /usr/sbin/upssched UPS heartbeat@localhost:<br>
<br>
At a moment when a timer should be running in your PI, what does this command <br>
report?<br>
<br>
Roger<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 27 Jan 2020 10:38:05 +0200<br>
From: nicolae788 <<a href="mailto:nicolae788@gmail.com" target="_blank">nicolae788@gmail.com</a>><br>
Cc: <a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a><br>
Subject: Re: [Nut-upsuser] System with MGE UPS shuts down too early<br>
Message-ID:<br>
<CAE076VCi-CQacsDi+YHS8x0dHyOg9WC1JRi9tHvt0-L1=<a href="mailto:uJ3OA@mail.gmail.com" target="_blank">uJ3OA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello.<br>
<br>
I sometimes encountered batteries that were ok, but at times one of the<br>
cells would develop a random short/open, therefore reducing the real<br>
capacity even if voltage reading was ok. In the absence of a battery load<br>
tester i would suggest running multiple tests with a load (car headlight<br>
bulb or similar) on the battery outside the ups. This is to eliminate the<br>
suspicion of a software or UPS unit fault.<br>
<br>
Alex.<br>
<br>
On Mon, 27 Jan 2020, 02:53 Manuel Wolfshant, <<a href="mailto:wolfy@nobugconsulting.ro" target="_blank">wolfy@nobugconsulting.ro</a>><br>
wrote:<br>
<br>
> On 1/25/20 10:53 AM, Georgi D. Sotirov wrote:<br>
><br>
> OK, so yesterday evening I done a real test cutting of the power to the<br>
> UPS. And it went good... the UPS supported my server for 28:50 minutes<br>
> (i.e. the expected runtime with this load), before forcing shutdown. The<br>
> batteries could still hold as charge was 30 % with about 15 minutes run<br>
> time. And the UPS did hold for another full 10 minutes before powering off.<br>
> These are the relevant lines from /var/log/ups:<br>
><br>
> 20200124 201318 32 0.0 12 [OB] NA 0.0<br>
> 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0<br>
> 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
> 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
> 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
> 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
><br>
> that looks perfectly fine<br>
><br>
><br>
><br>
> The server was shutdown properly, but for some reason it did not power<br>
> off. I saw an error from umount about busy file system, but I'm sure this<br>
> doesn't always happen.<br>
><br>
> the error is related to your linux system, not to nut<br>
><br>
><br>
><br>
> With everything powered off, I extracted the original batteries to check<br>
> them and measure the voltage. The batteries are Leoch DJW12-9.0 with one of<br>
> them at 12.57 V and the other at 12.64 V (measured without load after the<br>
> discharge).<br>
><br>
> That's... surprisingly well, assuming your multimeter indicates correct<br>
> values. I would have expected values well below 12V<br>
><br>
><br>
><br>
><br>
> And this morning there was again a short power failure (not more than 30<br>
> minutes, because the router connected to the battery power from the UPS did<br>
> hold up). With batteries charged up to 91% the UPS supported the server for<br>
> just 07:10 minutes and forced shutdown with 69% battery charge and over 20<br>
> minutes of run time...<br>
><br>
> 20200125 021123 70 0.0 16 [OB] NA 0.0<br>
> 20200125 021128 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
> 20200125 021133 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
> 20200125 021138 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
> 20200125 021143 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
> 20200125 021148 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
> 20200125 021150 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
><br>
> So, it seems to me that my UPS forces shutdown pretty randomly. Why the<br>
> UPS is not waiting for the preset low battery charge value of 15%? What is<br>
> actually driving this FSD ALARM and LB signal when batteries for sure could<br>
> hold up more?<br>
><br>
><br>
> Can you please show us all the configuration files ? I can only suspect<br>
> that there is something wrong there because (from a hardware point of view)<br>
> the UPS behaves very very well, according to your tests and logs.<br>
><br>
><br>
> _______________________________________________<br>
> Nut-upsuser mailing list<br>
> <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200127/44e776cc/attachment-0001.html" rel="noreferrer" target="_blank">http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200127/44e776cc/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 27 Jan 2020 11:27:01 +0200<br>
From: "Georgi D. Sotirov" <<a href="mailto:gdsotirov@gmail.com" target="_blank">gdsotirov@gmail.com</a>><br>
To: <a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a><br>
Subject: Re: [Nut-upsuser] System with MGE UPS shuts down too early<br>
Message-ID: <<a href="mailto:d4958554-40ca-cf0f-77bf-c9d6774d51de@gmail.com" target="_blank">d4958554-40ca-cf0f-77bf-c9d6774d51de@gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Hello Manuel,<br>
<br>
> that looks perfectly fine<br>
<br>
That one yes, but as I wrote, LB and FSD are happening on much higher <br>
battery charge values - 90% or more, which is not fine.<br>
<br>
> That's... surprisingly well, assuming your multimeter indicates <br>
> correct values. I would have expected values well below 12V<br>
<br>
My multimeter hasn't gone inspection recently, but I do not have reasons <br>
to believe that the readings are wrong :-)<br>
<br>
> Can you please show us all the configuration files ? I can only <br>
> suspect that there is something wrong there because (from a hardware <br>
> point of view) the UPS behaves very very well, according to your tests <br>
> and logs.<br>
<br>
Which configuration files you'd like to see exactly? I haven't made many <br>
configuration changes anyway. Isn't the UPS that reports LB (Low <br>
Battery) and FSB (forcing shutdown of the machine)? I mean if this is a <br>
configuration issue, then why I did not have this problem before? Why <br>
the shutdown happens on different battery charge levels?<br>
<br>
<br>
Regards,<br>
--<br>
Georgi<br>
<br>
On 27.1.2020 at 2:53, Manuel Wolfshant wrote:<br>
> On 1/25/20 10:53 AM, Georgi D. Sotirov wrote:<br>
>> OK, so yesterday evening I done a real test cutting of the power to <br>
>> the UPS. And it went good... the UPS supported my server for 28:50 <br>
>> minutes (i.e. the expected runtime with this load), before forcing <br>
>> shutdown. The batteries could still hold as charge was 30 % with <br>
>> about 15 minutes run time. And the UPS did hold for another full 10 <br>
>> minutes before powering off. These are the relevant lines from <br>
>> /var/log/ups:<br>
>><br>
>> 20200124 201318 32 0.0 12 [OB] NA 0.0<br>
>> 20200124 201323 30 0.0 13 [ALARM OB LB] NA 0.0<br>
>> 20200124 201328 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
>> 20200124 201333 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
>> 20200124 201338 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
>> 20200124 201340 30 0.0 13 [FSD ALARM OB LB] NA 0.0<br>
><br>
> that looks perfectly fine<br>
><br>
><br>
>><br>
>> The server was shutdown properly, but for some reason it did not <br>
>> power off. I saw an error from umount about busy file system, but I'm <br>
>> sure this doesn't always happen.<br>
><br>
> the error is related to your linux system, not to nut<br>
><br>
><br>
>><br>
>> With everything powered off, I extracted the original batteries to <br>
>> check them and measure the voltage. The batteries are Leoch DJW12-9.0 <br>
>> with one of them at 12.57 V and the other at 12.64 V (measured <br>
>> without load after the discharge).<br>
><br>
> That's... surprisingly well, assuming your multimeter indicates <br>
> correct values. I would have expected values well below 12V<br>
><br>
><br>
><br>
>><br>
>> And this morning there was again a short power failure (not more than <br>
>> 30 minutes, because the router connected to the battery power from <br>
>> the UPS did hold up). With batteries charged up to 91% the UPS <br>
>> supported the server for just 07:10 minutes and forced shutdown with <br>
>> 69% battery charge and over 20 minutes of run time...<br>
>><br>
>> 20200125 021123 70 0.0 16 [OB] NA 0.0<br>
>> 20200125 021128 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
>> 20200125 021133 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
>> 20200125 021138 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
>> 20200125 021143 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
>> 20200125 021148 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
>> 20200125 021150 69 0.0 16 [FSD ALARM OB LB] NA 0.0<br>
>><br>
>> So, it seems to me that my UPS forces shutdown pretty randomly. Why <br>
>> the UPS is not waiting for the preset low battery charge value of <br>
>> 15%? What is actually driving this FSD ALARM and LB signal when <br>
>> batteries for sure could hold up more?<br>
><br>
><br>
> Can you please show us all the configuration files ? I can only <br>
> suspect that there is something wrong there because (from a hardware <br>
> point of view) the UPS behaves very very well, according to your tests <br>
> and logs.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Nut-upsuser mailing list<br>
> <a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200127/a3ad9267/attachment.html" rel="noreferrer" target="_blank">http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200127/a3ad9267/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
<br>
------------------------------<br>
<br>
End of Nut-upsuser Digest, Vol 175, Issue 30<br>
********************************************<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Greg<br><br><a href="http://www.linkedin.com/in/gregtreantos" target="_blank">http://www.linkedin.com/in/gregtreantos</a></div>