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

Daily (almost) UPS Communication error

SLK-Purdue
Luminary

Daily (almost) UPS Communication error

I see a periodic (almost every day) UPS Communication Error at 1900h.  This is too regular to not be a software error.  I am running 6.6.1.  This is nothing else in the logs at this time.  I believe this started with 6.6 but not 100% sure on that.

 

ReadyNASOS!!version=6.6.1,time=1482880160,arch=arm,descr=ReadyNASOS


Jan 15 19:04:01 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 15 19:04:02 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 16 19:03:48 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 16 19:03:53 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 17 19:03:51 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 17 19:03:56 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 18 19:03:50 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 18 19:03:54 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 19 19:03:50 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 19 19:03:55 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 20 19:03:49 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 20 19:03:54 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 21 19:02:23 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 21 19:02:28 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.


Jan 23 19:02:26 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 23 19:02:31 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 24 19:02:24 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 24 19:02:29 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

Jan 25 19:02:25 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 25 19:02:30 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.


Jan 27 19:02:24 NAS-Ksander-2 readynasd[2292]: Error communicating with UPS 'UPS' ().
Jan 27 19:02:29 NAS-Ksander-2 readynasd[2292]: Communication with UPS 'UPS' () is OK.

 

Packages.log UPS items

 

ii  nut                            2.7.4-3.netgear2              all          network UPS tools - metapackage
ii  nut-client                     2.7.4-3.netgear2              armel        network UPS tools - clients
ii  nut-server                     2.7.4-3.netgear2              armel        network UPS tools - core system
ii  nut-snmp                       2.7.4-3.netgear2              armel        network UPS tools - SNMP driver

 

UPS log is

 

***** UPS *****
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2015/05/26
battery.runtime: 5976
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.3
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS RS 1500G
device.serial: 3B1522X06331 
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0002
driver.parameter.serial: 3B1522X06331
driver.parameter.synchronous: no
driver.parameter.vendorid: 051d
driver.version: 2.7.4
driver.version.data APC HID 0.96
driver.version.internal: 0.41
input.sensitivity: low
input.transfer.high: 150
input.transfer.low: 78
input.voltage: 119.0
input.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 865.L5 .D
ups.firmware.aux: L5
ups.load: 5
ups.mfr: American Power Conversion
ups.mfr.date: 2015/05/26
ups.model: Back-UPS RS 1500G
ups.productid: 0002
ups.realpower.nominal: 865
ups.serial: 3B1522X06331 
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Model: RN102|ReadyNAS 100 Series
Message 1 of 10
FramerV
NETGEAR Employee Retired

Re: Daily (almost) UPS Communication error

Hi SLK-Purdue,

 

Not sure if this is related to the AV issue that is being investigated. Can you try to disable your Anti-Virus and see if it will make any difference.

 

 

Regards,

Message 2 of 10
SLK-Purdue
Luminary

Re: Daily (almost) UPS Communication error

No Joy!!  I disabled AV and got the same error at the same time later that day.

Message 3 of 10
StephenB
Guru

Re: Daily (almost) UPS Communication error

Maybe PM skywalker and ask him if he'd like the logs.

 

There are some ongoing issues with UPS monitoring in 6.6.1 that some people are running into.  One of my cyberpowers hasn't been playing nicely with my RN526 (though another cyberpower is working just fine).

Message 4 of 10
SLK-Purdue
Luminary

Re: Daily (almost) UPS Communication error

Problem continues with AV disabled.

 

New data - this is clearly clock based.  When I adjust the time, the problem moves accordingly.  I have confirm I can see nothing in the cron logs.  Any clues?

Message 5 of 10
FramerV
NETGEAR Employee Retired

Re: Daily (almost) UPS Communication error

Hi SLK-Purdue,

 

May I ask for the system logs? I will try to inquire about your case.

 

How do I send all logs to ReadyNAS Community moderators?

 

 

Regards,

Message 6 of 10
nsne
Virtuoso

Re: Daily (almost) UPS Communication error

I'm seeing this issue too. Didn't realize a thread of sorts had already been created when I posted mine: https://community.netgear.com/t5/ReadyNAS-Hardware-Compatibility/Regular-UPS-disconnects-reconnects/...

Message 7 of 10
FramerV
NETGEAR Employee Retired

Re: Daily (almost) UPS Communication error

Hi SLK-Purdue,

 

If in case you would want to try, we have the BETA firmware released already.

 

ReadyNASOS 6.7.0-T158 (Beta 1)

 

 

Regards,

Message 8 of 10
SLK-Purdue
Luminary

Re: Daily (almost) UPS Communication error

Thanks for the offer.  I don't have a spare unit available at the moment to try a Beta.  Primary units are being used for some important work and need to not take beta risk with those units.  Did you find a problem that explains this behavior?

 

Thanks,

 

Scott

Message 9 of 10
FramerV
NETGEAR Employee Retired

Re: Daily (almost) UPS Communication error

Hi SLK-Purdue,

 

I am not really within the loop regarding the bugs that they find. Might be best to follow StephenB's advise to PM Skywalker about it

 

 

Regards,

Message 10 of 10
Top Contributors
Discussion stats
  • 9 replies
  • 2771 views
  • 0 kudos
  • 4 in conversation
Announcements