-
@dennypage said in NUT package:
@tman222 Which driver are you using?
Hi @dennypage - I'm using the usbhid driver. Is this the correct one, or should I try another? I did do a bit more reading and was left with the impression that the reason I wasn't seeing all the information was the current lack of Modbus support in NUT. Could that be the case?
This is all I see under UPS Status:
Name: ups@localhost Summary status: On line Runtime (H:M:S): 0:00:-1 Battery charge: 100% Battery voltage: 26.3Thanks again.
-
@tman222 said in NUT package:
I did do a bit more reading and was left with the impression that the reason I wasn't seeing all the information was the current lack of Modbus support in NUT. Could that be the case?
If I had to guess, yes that would be the issue. I just ordered a SMX from APC, so I'll have a look shortly. All my other UPSs are on a moving truck somewhere...
I do have an AP9631 on order as well. If I can't get it working with USB, I'll also try SNMP.
-
@dennypage said in NUT package:
@tman222 said in NUT package:
I did do a bit more reading and was left with the impression that the reason I wasn't seeing all the information was the current lack of Modbus support in NUT. Could that be the case?
If I had to guess, yes that would be the issue. I just ordered a SMX from APC, so I'll have a look shortly. All my other UPSs are on a moving truck somewhere...
I do have an AP9631 on order as well. If I can't get it working with USB, I'll also try SNMP.
Thanks @dennypage - I also decided today to go ahead and order the APC AP9630 add-on network card so I can use SNMP instead as it looks like that I won't be able to get USB fully working.
-
I previously had NUT install & talking to my UPS just fine. All I had to do was select Local USB & USBHID driver & it worked perfectly. Unfortunately, I screwed up my config & locked myself out of pfSense so I restored a backup of the config, but now I can't get NUT to work again....
I've already tried the re-install package option. Any other suggestions?
-
@bazzacad Did you go into UPS Settings and press Save?
-
@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.
-
@dennypage said in NUT package:
@bazzacad Did you go into UPS Settings and press Save?
Yes, I hit Save, still doesn't work.
-
@bazzacad Have you rebooted since NUT install? Or unplugged and replugged the cable?
Can you post log entries please?
-
@dennypage said in NUT package:
@bazzacad Have you rebooted since NUT install? Or unplugged and replugged the cable?
Can you post log entries please?
I tried unplug & re-plug and it didn't help.
I'll have to reboot after hours.
But here's the log. The "No such file or directory" looks promising...
-
@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.
