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