× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973

6.6.0 UPS alerts not sent

vandermerwe
Master

6.6.0 UPS alerts not sent

Had a power supply failure prior to the daily boot up at 08:00.

Looking at the logs it appears that a controlled shutdown took place about 2 minutes after the initial startup.  The UPS powers other devices and the remaing charge was probabaly already below the 60% threshold I have set.

This is all fine, but there are no entries in the normal GUI logs, and no email alert was sent about any UPS event.

Cutrently the UPS is charging and it's status is yellow in the GUI.

 

I have tested the email alert and this is functioning correctly, the switch and internet hub through which the email would have been sent is powered by the same UPS so would have been on at the time of the event.

 

Firstly which log would have recorded if an attempt had been made to send an email.

Secondly is this scenario (a prexisting power outage prior to boot), perhaps the reason there is no log entry in the main log and the reason there was no email?

 

 

Model: RN31600|ReadyNAS 300 Series 6- Bay
Message 1 of 95

Accepted Solutions
mdgm-ntgr
NETGEAR Employee Retired

Re: 6.6.0 UPS alerts not sent

Btw ReadyNAS OS 6.6.1 is now available!

 

In the unlikely event you still have problems on 6.6.1 please start a new thread.

View solution in original post

Message 95 of 95

All Replies
StephenB
Guru

Re: 6.6.0 UPS alerts not sent

email transmission is in msmtp.log (though it doesn't tell you why the emails are sent).  systemd-journal.log might also log it.


@vandermerwe wrote:

 

Secondly is this scenario (a prexisting power outage prior to boot), perhaps the reason there is no log entry in the main log and the reason there was no email?

  


It wouldn't surprise me.  Normally I only only two emails sent - one when the UPS state changes to battery power, and a second when the state changes again to line power.  There were no state changes in your case.

Message 2 of 95
evan2
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

Hi Vandermerve,

Could you please tell me which model UPS you are using?

Message 3 of 95
vandermerwe
Master

Re: 6.6.0 UPS alerts not sent

The UPS is an APC Smart-UPS 1500I.

There are no emails sent around the time of the power related shutdown according to the log files.  

I would expect to be notified about a prolonged power cut leading to a shutdown, this is far more important than knowing that the unit is on or off UPS power, events which do seem to trigger email alerts. 

Message 4 of 95
CigarSurgeon
Aspirant

Re: 6.6.0 UPS alerts not sent

Using an APC Smart-UPS RS 1500 and my UPS status is yellow with a UPS_RAWSTATUS_WAIT message.

Message 5 of 95
evan2
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

See your problem,

the UPS is charging and it's status is yellow in the GUI.

but there is any log in GUI Logs, and if onGUI warning log, system won't sent email alert,

I filed a request to Development,

Thanks for your report.

Message 6 of 95
vandermerwe
Master

Re: 6.6.0 UPS alerts not sent

Not exactly. I don't need an alert that the UPS  is charging. The alert needs to be about a shutdown if the UPS power reaches the threshold set. This did not happen even though the shutdown was a graceful shutdown when the readynas discovered UPS power was low.

Message 7 of 95
evan2
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

I just checked 6.5.1, there is a log entry when it changes to battery power,

and there is a log entry if the UPS power reaches the threshold set.

 

The issue only happens on 6.6.0, I will file bug to RD.

 

Thanks for your report.

 

Following is log on 6.5.1:

 6.5.1_UPS Log.png

Message 8 of 95
dabanh_freak
Tutor

Re: 6.6.0 UPS alerts not sent

I also have this problem.

 

UPS Warning in Status page

Under Power I have UPS_RAWPOWER_WAIT

Main problem looks like under Performance, I see this:ReadyNAS_104.png

Model: RN10400|ReadyNAS 100 Series 4- Bay (Diskless)
Message 9 of 95
haus
Aspirant

Re: 6.6.0 UPS alerts not sent

Edit: After hitting "refresh" a few times on the various frontview System pages my UPS section under "Power" now shows green and "On line power". Very strange.

 

---

 

I am also seeing a yellow warning "UPS_RAWSTATUS_WAIT" under "Power" with a Cyberpower CP850PFCLCD UPS system (attached via USB) since upgrading to 6.6.0. I haven't created any power events yet to test notifications or shutdown, but I always had a green status icon under "Power" before the upgrade (I was on 6.5.1).

 

Under "Performance" right now I have a green icon next to the UPS with "100%".

 

When I first checked Frontview this morning under "Overview" I had a yellow icon next to "Status" with the same UPS warning as the "Power" tab, but after unplugging the USB cable from the UPS and plugging it back in that icon switched to green and now says "Healthy". 

 

I do not know what UPS_RAWSTATUS_WAIT means exactly, but this is a new message since upgrading to 6.6.0.

Message 10 of 95
evan2
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

Hi CigarSurgeon, dabanh_freak, haus

Thanks for your report the issue,

through I can't reproduce the issue on my UPS (APC Smart UPS 1000)

We have reported issue to developer,

I will let you know if it is fixed.

 

Message 11 of 95
ShoGinn
Tutor

Re: 6.6.0 UPS alerts not sent

There was a thread about this as well.. It was in the beta forum, but it has bled over into the release

 

https://community.netgear.com/t5/ReadyNAS-Beta-Release/ReadyNASOS-6-6-0-RC2-UPS-problems/m-p/1153066...

 

 

I have the same problem with the RN104 and Cyberpower.

Model: RN104|ReadyNAS 100 Series
Message 12 of 95
haus
Aspirant

Re: 6.6.0 UPS alerts not sent

Thank you for posting that. I did a search on the exact error message I was getting and that thread didn't come up despite being written in one of the posts there.
Message 13 of 95
ShoGinn
Tutor

Re: 6.6.0 UPS alerts not sent

Its odd how the search works on the forums, I have struggled trying to find stuff on here!

 

Not sure what they did to mess up NUT but it looks like its been escalated a couple times.

 

 

Message 14 of 95
haus
Aspirant

Re: 6.6.0 UPS alerts not sent

I hope they solve it soon. I'm currently running a test on the UPS; removing it from line power and the ReadyNAS 102 has no idea there's a power situation. I assume this means if a power outage occurs, the NAS won't cleanly shut down before the UPS runs out of battery power.

Message 15 of 95
ewok
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

6.6.0 has an issue with UPS event notifications, which will be fixed for the 6.6.1 release.  The underlying UPS functionality should still work, only notifications are affected.

Message 16 of 95
ShoGinn
Tutor

Re: 6.6.0 UPS alerts not sent

Except it doesn't ewok.

The data is stale which means the communication with the ups is affected.
Message 17 of 95
haus
Aspirant

Re: 6.6.0 UPS alerts not sent


@ShoGinn wrote:
Except it doesn't ewok.

The data is stale which means the communication with the ups is affected.

Thank you. This was my thought too; though I haven't yet tested mine to failure (UPS battery depletion), when I unplugged the UPS from the wall, the ReadyNAS made no indication at all of any power issue, which it has done on the prior firmware. It certainly appears that the ReadyNAS simply has no communication with the UPS and therefore wouldn't shut itself down safely at any point.

 

I'll give it a shot later on and let the UPS run down fully to find out for sure. My data is backed up anyway.

 

 

Message 18 of 95
ewok
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

You're right.  I took a closer look and saw that UPS health updates are tied to the event mechanism.  We'll have a fix available in 6.6.1, possibly sooner.

Message 19 of 95
JBDragon1
Virtuoso

Re: 6.6.0 UPS alerts not sent

I'm having the same problem myself.  I just replaced the battery like 3 months ago.  It's a APC 500 Pro I belieave.  It's been Yellow for a while.  I've been thinking something was wrong with the UPS again.   I just went into the settings for it, clicked on Apply and it changed to Green.  It's been yellow for a while now.    So, clearly a bug.

Message 20 of 95
Amidala
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

Hi CigarSurgeon:

 

Does the UPS status eventually go back to an expected value? Can be used normally now?

 

-Amidala

Message 21 of 95
Amidala
NETGEAR Expert

Re: 6.6.0 UPS alerts not sent

Hi dabanh_freak:

 

Does the UPS status eventually go back to an expected value? Can be used normally now?

 

-Amidala

Message 22 of 95
Michael_Oz
Luminary

Re: 6.6.0 UPS alerts not sent

I'm getting this too.

Since 6.6.0 update yesterday.

 

RN316

UPS - Cyber Power Value 1200E

Also a old RN NV+ using the UPS and monitoring RN316 for UPS status via network.

 

First symptom was alert emails from NV+ (nothing from 316):

UPS Communication error. followed eventually by Communication with UPS OK.

Checking the NV+ shows:

 

UPS 1Remote Error, Battery charge: 0%, 0 minutes 

Out of Spec

 

(note it was not shutting down after the above)

I looked at the UPS display, all seemed OK.

Then later

 

 UPS 1Remote CPS Value1200E, Battery charge: 100%, 21 minutes OK

 

I then looked at the 316:

 

316 was showing yellow & UPS_RAWSTATUS_WAIT, constantly. Nothing in the frontview logs.

 

(this could be a red herring)

System/Power/UPS/Settings/Shutdoen_threshold was Auto.

When changed to 40%, the status went green 'On line power' - for a while...

but the yellow UPSRAW... was back later. So I don't know if changing the threshold matters.

 

Examination of the NV+ emails/logs show:

Comms OK,

followed, ~10s to a few minutes later with Comms Error.

Then ~ 90 minutes later repeats.

 

Severity Date Message 
Sun Nov 13 11:46:29 EST 2016Communication with UPS OK.
Sun Nov 13 11:46:25 EST 2016UPS Communication error.
Sun Nov 13 11:13:51 EST 2016Communication with UPS OK.
Sun Nov 13 11:03:42 EST 2016UPS Communication error.
Sun Nov 13 10:59:41 EST 2016Communication with UPS OK.
Sun Nov 13 08:13:03 EST 2016UPS Communication error.
Sun Nov 13 08:12:58 EST 2016Communication with UPS OK.
Sun Nov 13 06:40:42 EST 2016UPS Communication error.
Sun Nov 13 06:40:31 EST 2016Communication with UPS OK.
Sun Nov 13 03:36:08 EST 2016UPS Communication error.
Sun Nov 13 03:36:03 EST 2016Communication with UPS OK.
Sun Nov 13 02:03:47 EST 2016UPS Communication error.
Sun Nov 13 02:03:32 EST 2016Communication with UPS OK.
Sun Nov 13 00:31:16 EST 2016UPS Communication error.

 

So it seems to be in the Comms OK for the last 30 minutes...(I chaned the settings again and it generated the 11:46 errors above)

Probably a red herring, as I changed it back and got another pair of errors...lately the OK follows the error; I'm wondering if the time shown in the email/logs may be inacurate?

 

Anyway, I'm 1/2 way thru a 7TB backup, so can't test a simulated power failure ATM.

Will do a test after it finishes.

 

 

Model: RN31600|ReadyNAS 300 Series 6- Bay
Message 23 of 95
ShoGinn
Tutor

Re: 6.6.0 UPS alerts not sent

I would not recommend testing it, and just trust the status. I think because they updated to the new Linux Kernel that this is truely messed up.

Message 24 of 95
Michael_Oz
Luminary

Re: 6.6.0 UPS alerts not sent

 

System log, yesterday until this morning this is typical:

 

Nov 13 08:43:25 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:25 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:25 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:30 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 08:43:30 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 08:43:30 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 08:43:30 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:30 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:30 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:32 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 08:43:32 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 08:43:32 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 08:43:32 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 08:43:32 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 08:43:49 ME-NAS-316A upsd[26513]: Data for UPS [UPS] is stale - check driver
Nov 13 08:43:49 ME-NAS-316A upsd[26513]: Data for UPS [UPS] is stale - check driver
Nov 13 08:43:49 ME-NAS-316A upsd[26513]: Data for UPS [UPS] is stale - check driver
Nov 13 08:43:50 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:50 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:50 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:55 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:55 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 08:43:55 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
...
Nov 13 09:14:10 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:10 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:10 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:15 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:15 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:15 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:20 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 09:14:20 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 09:14:20 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 09:14:20 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:20 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:20 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:22 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 09:14:22 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 09:14:22 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 09:14:22 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 09:14:22 ME-NAS-316A upsd[26513]: Connected to UPS [UPS]: usbhid-ups-UPS
Nov 13 09:14:39 ME-NAS-316A upsd[26513]: Data for UPS [UPS] is stale - check driver
Nov 13 09:14:39 ME-NAS-316A upsd[26513]: Data for UPS [UPS] is stale - check driver
Nov 13 09:14:39 ME-NAS-316A upsd[26513]: Data for UPS [UPS] is stale - check driver
Nov 13 09:14:40 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:40 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:14:40 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale

 

I don't recall what I did at ~9:45 but

 

Nov 13 09:45:06 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:45:06 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:45:06 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 09:45:10 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 09:45:10 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 09:45:10 ME-NAS-316A upsd[26513]: Send ping to UPS [UPS] failed: Resource temporarily unavailable
Nov 13 09:45:11 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:11 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:11 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:21 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Server disconnected
Nov 13 09:45:21 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Server disconnected
Nov 13 09:45:21 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Server disconnected
Nov 13 09:45:31 ME-NAS-316A upsmon[26516]: Set username on [UPS@localhost] failed: Server disconnected
Nov 13 09:45:31 ME-NAS-316A upsmon[26516]: Set username on [UPS@localhost] failed: Server disconnected
Nov 13 09:45:36 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:36 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:36 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:46 ME-NAS-316A upsmon[26516]: Set username on [UPS@localhost] failed: Server disconnected
Nov 13 09:45:46 ME-NAS-316A upsmon[26516]: Set username on [UPS@localhost] failed: Server disconnected
Nov 13 09:45:51 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:51 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:45:51 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 09:46:01 ME-NAS-316A upsmon[26516]: Set username on [UPS@localhost] failed: Server disconnected
Nov 13 09:46:01 ME-NAS-316A upsmon[26516]: Set username on [UPS@localhost] failed: Server disconnected
Nov 13 09:46:06 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected

...

until

 

Nov 13 10:57:38 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 10:57:38 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 10:57:38 ME-NAS-316A upsmon[26516]: Poll UPS [UPS@localhost] failed - Driver not connected
Nov 13 10:57:39 ME-NAS-316A upsmon[26516]: Signal 15: exiting
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: Can't connect to UPS [UPS] (usbhid-ups-UPS): Interrupted system call
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: Can't connect to UPS [UPS] (usbhid-ups-UPS): Interrupted system call
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: Can't connect to UPS [UPS] (usbhid-ups-UPS): Interrupted system call
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: Can't connect to UPS [UPS] (usbhid-ups-UPS): Interrupted system call
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: Can't connect to UPS [UPS] (usbhid-ups-UPS): Interrupted system call
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: User monuser@::1 logged out from UPS [UPS]
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: User monuser@::1 logged out from UPS [UPS]
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: User monuser@::1 logged out from UPS [UPS]
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: write() failed for ::1: Broken pipe
Nov 13 10:57:40 ME-NAS-316A upsd[26513]: Signal 15: exiting
Nov 13 10:57:40 ME-NAS-316A usbhid-ups[26511]: Parse error on sock: Invalid ctx buffer
Nov 13 10:57:40 ME-NAS-316A usbhid-ups[26511]: Signal 15: exiting
Nov 13 10:57:41 ME-NAS-316A usbhid-ups[5158]: Startup successful
Nov 13 10:57:41 ME-NAS-316A upsd[5160]: Startup successful
Nov 13 10:57:41 ME-NAS-316A upsmon[5162]: Startup successful
Nov 13 10:57:41 ME-NAS-316A upsd[5160]: User monuser@::1 logged into UPS [UPS]
Nov 13 10:57:41 ME-NAS-316A upsd[5160]: User monuser@::1 logged into UPS [UPS]
Nov 13 10:57:41 ME-NAS-316A upsd[5160]: User monuser@::1 logged into UPS [UPS]
Nov 13 10:59:41 ME-NAS-316A upsd[5160]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 10:59:41 ME-NAS-316A upsd[5160]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 10:59:41 ME-NAS-316A upsd[5160]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:03:38 ME-NAS-316A upsd[5160]: Data for UPS [UPS] is stale - check driver
Nov 13 11:03:38 ME-NAS-316A upsd[5160]: Data for UPS [UPS] is stale - check driver
Nov 13 11:03:38 ME-NAS-316A upsd[5160]: Data for UPS [UPS] is stale - check driver
Nov 13 11:03:41 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:41 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:41 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:45 ME-NAS-316A upsd[5160]: User monuser@192.168.1.10 logged out from UPS [UPS]
Nov 13 11:03:45 ME-NAS-316A upsd[5160]: User monuser@192.168.1.10 logged out from UPS [UPS]
Nov 13 11:03:45 ME-NAS-316A upsd[5160]: User monuser@192.168.1.10 logged out from UPS [UPS]
Nov 13 11:03:46 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:46 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:46 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:51 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:51 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:51 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:03:56 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale

...

 

then

Nov 13 11:11:56 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:11:56 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:11:56 ME-NAS-316A upsmon[5163]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 11:11:58 ME-NAS-316A upsmon[5163]: Signal 15: exiting
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: UPS [UPS] data is no longer stale
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: UPS [UPS] data is no longer stale
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: UPS [UPS] data is no longer stale
Nov 13 11:11:58 ME-NAS-316A usbhid-ups[5158]: Signal 15: exiting
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: mainloop: Interrupted system call
Nov 13 11:11:58 ME-NAS-316A upsd[5160]: Signal 15: exiting
Nov 13 11:11:58 ME-NAS-316A usbhid-ups[6688]: Startup successful
Nov 13 11:11:58 ME-NAS-316A upsd[6690]: Startup successful
Nov 13 11:11:58 ME-NAS-316A upsmon[6692]: Startup successful
Nov 13 11:11:58 ME-NAS-316A upsd[6690]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:11:58 ME-NAS-316A upsd[6690]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:11:58 ME-NAS-316A upsd[6690]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:13:51 ME-NAS-316A upsd[6690]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:13:51 ME-NAS-316A upsd[6690]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:13:51 ME-NAS-316A upsd[6690]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:46:23 ME-NAS-316A upsmon[6693]: Signal 15: exiting
Nov 13 11:46:23 ME-NAS-316A upsd[6690]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:46:23 ME-NAS-316A upsd[6690]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:46:23 ME-NAS-316A upsd[6690]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:46:23 ME-NAS-316A upsd[6690]: mainloop: Interrupted system call
Nov 13 11:46:23 ME-NAS-316A upsd[6690]: Signal 15: exiting
Nov 13 11:46:23 ME-NAS-316A usbhid-ups[6688]: Signal 15: exiting
Nov 13 11:46:24 ME-NAS-316A usbhid-ups[11151]: Startup successful
Nov 13 11:46:24 ME-NAS-316A upsd[11153]: Startup successful
Nov 13 11:46:24 ME-NAS-316A upsmon[11155]: Startup successful
Nov 13 11:46:24 ME-NAS-316A upsd[11153]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:46:24 ME-NAS-316A upsd[11153]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:46:24 ME-NAS-316A upsd[11153]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:46:30 ME-NAS-316A upsd[11153]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:46:30 ME-NAS-316A upsd[11153]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:46:30 ME-NAS-316A upsd[11153]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:50:15 ME-NAS-316A upsmon[11156]: Signal 15: exiting
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: User monuser@::1 logged out from UPS [UPS]
Nov 13 11:50:15 ME-NAS-316A usbhid-ups[11151]: Signal 15: exiting
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: mainloop: Interrupted system call
Nov 13 11:50:15 ME-NAS-316A upsd[11153]: Signal 15: exiting
Nov 13 11:50:16 ME-NAS-316A usbhid-ups[11986]: Startup successful
Nov 13 11:50:16 ME-NAS-316A upsd[11988]: Startup successful
Nov 13 11:50:16 ME-NAS-316A upsmon[11990]: Startup successful
Nov 13 11:50:16 ME-NAS-316A upsd[11988]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:50:16 ME-NAS-316A upsd[11988]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:50:16 ME-NAS-316A upsd[11988]: User monuser@::1 logged into UPS [UPS]
Nov 13 11:50:20 ME-NAS-316A upsd[11988]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:50:20 ME-NAS-316A upsd[11988]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 11:50:20 ME-NAS-316A upsd[11988]: User monuser@192.168.1.10 logged into UPS [UPS]
Nov 13 12:13:58 ME-NAS-316A upsd[11988]: Data for UPS [UPS] is stale - check driver
Nov 13 12:13:58 ME-NAS-316A upsd[11988]: Data for UPS [UPS] is stale - check driver
Nov 13 12:13:58 ME-NAS-316A upsd[11988]: Data for UPS [UPS] is stale - check driver
Nov 13 12:14:01 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 12:14:01 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 12:14:01 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 12:14:02 ME-NAS-316A upsd[11988]: User monuser@192.168.1.10 logged out from UPS [UPS]
Nov 13 12:14:02 ME-NAS-316A upsd[11988]: User monuser@192.168.1.10 logged out from UPS [UPS]
Nov 13 12:14:02 ME-NAS-316A upsd[11988]: User monuser@192.168.1.10 logged out from UPS [UPS]
Nov 13 12:14:06 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 12:14:06 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 12:14:06 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale
Nov 13 12:14:11 ME-NAS-316A upsmon[11991]: Poll UPS [UPS@localhost] failed - Data stale

 

I suspect changing the frontview settings restarts the daemon, it works OK for a bit, then has trouble. ??

Lety me know if anyone needs more info.

BTW helpfully ups.log is empty ecxept for "***** UPS *****"

Message 25 of 95
Top Contributors
Discussion stats
Announcements