UPS wrong notification every start or shutdown

Status
Not open for further replies.

Jacopx

Patron
Joined
Feb 19, 2016
Messages
367
Buongiorno a tutti,
a few weeks ago I bought a new APC UPS for my environment, everything works very well. The UPS is usb-linked to my pfSense box that it works like a NUT Server, FN is a NUT Client for the pfSense system. The system hasen't problem, when i need that the system going off it do what i want and so on...

My problem is that every time that I start or that I shutdown my FN system I'm receiving 2 annoying mails with this text:
Code:
COMMBAD - SaveLife@172.16.0.1:3493


SaveLife is the name of my UPS (LoL) and the number is the IP of pfSense... Someone can help me to avoid this "problem"?
 

Jacopx

Patron
Joined
Feb 19, 2016
Messages
367
Anything in /var/log/messages?

This is the output:
Code:
Oct 10 00:33:39 freenas upsmon[2316]: Poll UPS [SaveLife@172.16.0.1:3493] failed - Server disconnected
Oct 10 00:33:39 freenas upsmon[2316]: Communications with UPS SaveLife@172.16.0.1:3493 lost
Oct 10 00:33:44 freenas upsmon[2316]: Login on UPS [SaveLife@172.16.0.1:3493] failed - got [ERR ACCESS-DENIED]
Oct 10 00:33:49 freenas dhclient: New IP Address (lagg0): 172.16.0.10
Oct 10 00:33:49 freenas dhclient: New Subnet Mask (lagg0): 255.255.255.192
Oct 10 00:33:49 freenas dhclient: New Broadcast Address (lagg0): 172.16.0.63
Oct 10 00:33:49 freenas dhclient: New Routers (lagg0): 172.16.0.1
Oct 10 00:33:49 freenas upsmon[2316]: Communications with UPS SaveLife@172.16.0.1:3493 established


I have added the part of the dhclient because I think that is the problem! My FN try to reach the UPS by its IP but as soon it hans't already grab the connection parameters with the DHCP it can't reach the router where the UPS is phisically-linked. One solution can be switch to a fixed IP or change the order of the system boot call. I don't want to fix the IP on the machine, i prefer the DHCP Reservation but I think the the second solution isn't to easy...
 
Status
Not open for further replies.
Top