Error Communicating with UPS via NAS - Two NASs, one UPS

---

Bruce_In_Philly wrote:

 

UPS is plugged directly into USB port on Storage-0 and shows a correct connection to the UPS

Storage-1 is configured in System/Power/UPS to connect to "UPS 192.168.50.59" which is the other NAS

Both NASs are plugged via Ethernet into the same Ethernet switch.

 

I am getting emails from Storage-1 denoting "Error communicating with UPS "UPS"()"  and then another within seconds denoting "Communication with UPS 'UPS' () is OK."

Frequency email pair is every 1 to 2 to 3 days.  Logs are getting filled up with these messages.

I get no emails from Storage-0 that is connected directly to the UPS.

 

Appears that maybe a timeout should be increased a bit?  

 

Ideas?

 

---

Sandshark got these messages a while back on one of his setups - not sure if he ever sorted out what was happening or not.

 

I've also seen these errors, but if I remember correctly it was with a USB-connected CyberPower UPS, so maybe not the same.

 

 

There are a couple of parameters that you could set in upsmon.conf (in \etc\nut)

• https://networkupstools.org/docs/man/upsmon.conf.html

Not sure when or if the readynas firmware overwrites this file.  Generally I keep both the original and my mod handy, so I can re-apply the fix easily (in this case, I'd create \etc\nut\upsmon.conf.orig and \etc\nut\upsmon.conf.mod, and also keep a copy of both somewhere else, in case I needed a factory default later on).  

 

If it rewrites it every time the NAS is booted, you could try setting file permissions to prevent that.

 

 

Looking through the doc, I don't think changing the polling parameters will help.  Changing 

 

NOTIFYFLAG COMMOK   EXEC
NOTIFYFLAG COMMBAD  EXEC

 

to

 

NOTIFYFLAG COMMOK   IGNORE
NOTIFYFLAG COMMBAD  IGNORE

 

should suppress the messages (not something I've ever tried, but what I'd do first). 

 

 

It looks like it is possible to do something more elaborate with the NUT CMDSCRIPT capability if you were so inclined.  Chapter 7 in the NUT manual has more info on this.

• https://networkupstools.org/docs/user-manual.pdf

 

One thought on debugging this stuff safely - 

 

You do want to make sure that any mods don't interfere with the shutdown when power is lost.

 

Moving the NAS power so it isn't connected to the UPS power (but leaving the monitoring paths ok) might be useful.  Connect a different load to the UPS (something that will drain the battery reasonably quickly without damaging anything).  Then you can make sure that the shutdown still happens cleanly, without risking an unclean shutdown when the battery drains.