NUT package (2.8.0 and below)
-
@dennypage said in NUT package:
@tman222 FWIW, I'm up and running with the AP9631. I haven't had time to play with the USB, but I assume it won't work until Modbus support is added to NUT.
Thanks @dennypage, that's good to know. I've actually got a AP9630 sitting next to me here as well. Planning to install in the next couple days so I can get the full information from the UPS via SNMP.
-
@bazzacad I've seem some weird problems with packages re-installed after a restore. If reboot doesn't solve your issue, I would recommend removing the NUT package and re-installing it.
-
@tman222 said in NUT package:
@dennypage said in NUT package:
@tman222 FWIW, I'm up and running with the AP9631. I haven't had time to play with the USB, but I assume it won't work until Modbus support is added to NUT.
Thanks @dennypage, that's good to know. I've actually got a AP9630 sitting next to me here as well. Planning to install in the next couple days so I can get the full information from the UPS via SNMP.
Installed the AP9630 last night -- all is working well now and I see the required information using NUT.
Only pain was getting a SSL cert installed on the UPS -- turns out one has to use the APC Network Management Card Security Wizard software to generate a .p15 cert file as the UPS doesn't seem to want to take any other format.
https://www.apc.com/shop/my/en/products/APC-Network-Management-Card-Security-Wizard-v1-0-4/P-SFNMCSECWIZ104
-
@tman222 said in NUT package:
Only pain was getting a SSL cert installed on the UPS -- turns out one has to use the APC Network Management Card Security Wizard software to generate a .p15 cert file as the UPS doesn't seem to want to take any other format.
Yea, serious pain. I haven’t been able to accomplish it as I don’t have access to a Windows system. APC is ridiculously behind security wise. Be sure to update the firmware on the network card or you will be stuck with TLS 1.0.
-
@dennypage said in NUT package:
@bazzacad I've seem some weird problems with packages re-installed after a restore. If reboot doesn't solve your issue, I would recommend removing the NUT package and re-installing it.
The reboot worked. ;-)
Thanks much -
@dennypage said in NUT package:
@tman222 said in NUT package:
Only pain was getting a SSL cert installed on the UPS -- turns out one has to use the APC Network Management Card Security Wizard software to generate a .p15 cert file as the UPS doesn't seem to want to take any other format.
Yea, serious pain. I haven’t been able to accomplish it as I don’t have access to a Windows system. APC is ridiculously behind security wise. Be sure to update the firmware on the network card or you will be stuck with TLS 1.0.
I was lucky enough that mine came with firmware 6.6.4 pre-installed so I already had support up to TLS 1.2. I did install 6.7.2 yesterday hoping I might see TLS 1.3, but alas still only 1.2.
One thing I did notice - I'm unable to over-write some of the UPS parameters: For instance if I try to overwrite battery.runtime.low under "Extra Arguments To Driver" I get a message in the syslog that this parameter is immutable. Have you run into this as well @dennypage ? Thanks in advance.
-
@tman222 said in NUT package:
One thing I did notice - I'm unable to over-write some of the UPS parameters: For instance if I try to overwrite battery.runtime.low under "Extra Arguments To Driver" I get a message in the syslog that this parameter is immutable.
I haven't explored the SNMP implementation much yet, but I expect that you will want to change these variables in the UPS itself via Configuration->Shutdown in the NMC interface. You can probably also change them using SNMPv3, but I haven't tried.
-
@dennypage said in NUT package:
@kevindd992002 It will be a while before I can truly experiment. I won't actually have a UPS again for several weeks.
However, I just brought my Synology up and noticed that I didn't not receive an email indicating that the nut server was not available. Previously I always received notification from the Synology when the nut server went offline so there may indeed be an issue with newer the DSM versions.
@dennypage , when do you think can you get back to troubleshooting this?
-
@kevindd992002 I have confirmed that the Synology is no longer sending emails when it is disconnected from the NUT server even though these are enabled in the Synology notification interface. This would certainly be a Synology bug.
I've also confirmed that there is a log entry in the pfSense system log when the Synology connects. It looks like this:
Aug 6 09:50:09 upsd 52880 User monuser@192.168.0.4 logged into UPS [ups]If you are not seeing this in the logs, then the Synology is not successfully connecting.
-
@dennypage said in NUT package:
If you are not seeing this in the logs, then the Synology is not successfully connecting.
@dennypage : thanks for your last (above) message.
I knew something was missing.
Could figure out what is was / didn't take the time for it.Placed this on the NUT settings page :
because the file on my Syno said ( /usr/syno/etc/ups/upsmon.conf ) :
..... MONITOR ups@192.168.1.1 1 monuser secret slave ....Know I have :
192.168.1.15 is my Syno.
When I have some time, I'll check what happens when pfSense (the UPS master) is switched to battery.
-
@dennypage said in NUT package:
upsd
Ok, that's not good then. When I checked the logs now, I didn't see any upsd entries. I only saw upsmon entries. I then restarted the pfsense UPS monitoring service and got this:
Aug 9 07:52:04 upsmon 17459 UPS ups on battery Aug 9 08:02:16 upsmon 17459 UPS ups on line power Aug 9 08:04:01 upsmon 17459 UPS ups on battery Aug 9 08:05:16 upsmon 17459 UPS ups on line power Aug 9 11:01:04 upsmon 17459 Signal 15: exiting Aug 9 11:01:04 upsd 19154 User local-monitor@::1 logged out from UPS [ups] Aug 9 11:01:04 upsd 19154 mainloop: Interrupted system call Aug 9 11:01:04 upsd 19154 Signal 15: exiting Aug 9 11:01:04 usbhid-ups 18838 Signal 15: exiting Aug 9 11:01:04 upsmon 37412 Startup successful Aug 9 11:01:05 usbhid-ups 38472 Startup successful Aug 9 11:01:05 upsd 38680 listening on 192.168.55.1 port 3493 Aug 9 11:01:05 upsd 38680 listening on 192.168.10.1 port 3493 Aug 9 11:01:05 upsd 38680 listening on ::1 port 3493 Aug 9 11:01:05 upsd 38680 listening on 127.0.0.1 port 3493 Aug 9 11:01:05 upsd 38680 Connected to UPS [ups]: usbhid-ups-ups Aug 9 11:01:05 upsd 38722 Startup successful Aug 9 11:01:07 upsd 38722 User local-monitor@::1 logged into UPS [ups]I don't see any logs in the past. Does pfsense do circular logging? I'm thinking past logs were deleted or something but the weird thing is that I still have August 2 logs from other services so that couldn't be it. I'm not really sure.
The most pressing matter though is why does the Synology GUI say that it is connected to the UPS but the pfsense system logs doesn't show that? What could be the issue here? I have a similar setup in two locations but this one has a Synology client and experiencing this issue.
EDIT1:
I did another test. Like I said, I have two locations and I have a site-to-site OpenVPN tunnel between them. I connected the Synology device to the UPS of the remote site and when I checked the pfsense system logs there, I also didn't see the monuser log that we're looking for. So this tells me that there is something wrong with the Synology device? I'm not really sure.
EDIT2:
I already tried reinstalling the NUT package to no avail. Here's what I see in Synology:
It does show the correct UPS statistics there so I know it's connecting.
-
@kevindd992002 said in NUT package:
Does pfsense do circular logging?
Yep (see manual - the clog stuff)
Did you looked up the user name of your UPS ? I had to access the files (found them using the Syno forums) to see that the user/password were.
I entered those into the UPS settings on pfSense (see above).No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
monuser/secret is the default username/password for Synology devices. It's interesting though:
This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.
-
@Gertjan and the UPS on the server must be named “ups”
-
@kevindd992002 said in NUT package:
This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.
The upsd.users file on pfSense will be overwritten whenever the service re-saves.
On the Syno you’re probably looking in the wrong place for the upsmon.conf file. They moved it a few releases back. Look to see what file gets modded.
-
@dennypage said in NUT package:
@kevindd992002 said in NUT package:
This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.
The upsd.users file on pfSense will be overwritten whenever the service re-saves.
On the Syno you’re probably looking in the wrong place for the upsmon.conf file. They moved it a few releases back. Look to see what file gets modded.
I meant I changed the password of the monuser user in the pfsense NUT GUI. So technically if I change that to some gibberish random string, the Syno won't be able to connect and get the ups device information, right? Or is that monuser account only used for monitoring alone?
That's weird. All documentation I see in the Internet say that's the correct place for the upsmon.conf in a Syno. And regardless, you won't be able to change the Syno monuser account anyway, right?
-
@dennypage , do you still have any other ideas/clues as to why this is happening on my environment?
-
@kevindd992002 said in NUT package:
monuser/secret is the default username/password for Synology devices. It's interesting though:
This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.
Some of the previous information has to be incorrect.
An empty upsmon.conf file would not only would this mean that there is no authentication, it would also mean that the Synology was able to magically intuit the IP address of the remote NUT master.
I am running DSM 6.2.2-24922 Update 2.
There are these "ups.conf" and "upsmon.conf" files:
-rwxr-xr-x 1 root root 3935 May 9 15:51 /etc.defaults/ups/ups.conf
-rwxr-xr-x 1 root root 3924 May 10 2015 /etc/ups/ups.conf
-rw-r----- 1 root root 3935 May 9 15:51 /usr/syno/etc.defaults/ups/ups.conf
-rw-r----- 1 root root 3898 Aug 11 15:08 /usr/syno/etc/ups/ups.conf
-rw-r----- 1 root root 12150 May 9 15:51 /usr/syno/etc.defaults/ups/upsmon.conf
-rw-r--r-- 1 root root 12150 Aug 11 15:08 /usr/syno/etc/ups/upsmon.confThe operational files currently appear in /usr/syno/etc/ups.
With ups monitoring enabled on the Synology, /usr/syno/etc/ups/upsmon.conf cannot not be empty, regardless of the ups being local or remote.
I would suggest you start from the ground up. Ignore pfSense for now. Update, reboot and reconfigure ups monitoring on the Synology. Confirm that it is updating /usr/syno/etc/ups/upsmon.conf as expected.
-
Also : login using 'root'.
-
@Gertjan said in NUT package:
Also : login using 'root'.
Lol. I thought that might be a Synology issue as well. I did test however, and was able to see the correct content of upsmon.conf using sudu.
