-
@dennypage said in NUT package:
@kevindd992002 said in NUT package:
And that thread I linked looks like the OP was saying that the upsd.users gets edited to the original monuser user everytime Synology gets an update and that you were going to verify. Were you able to verify that already?
upsd.users is used on the server side rather than the client side, so if the UPS is attached to the pfSense host, then it is the pfSense upsd.users that must be modified.
As of DSM 6, the Synology rewrites all the ups files at startup, and is hard-coded around the default user/password, so you have to use the NUT default. Kind of stupid on Synology's part, but it is what it is.
As discussed in post #2 in this thread, you need to add config to the upsd.users on the pfSense side to support remote access. The Synology is hardcoded to these values:
[monuser] password = secret upsmon slaveFWIW, I haven't tested Synology remote access in a couple of years. Hopefully this should still work.
Ahh, I see. But then you also said in one of your posts there that it is not recommended to modify the monuser credentials in the upsd.users advanced settings in pfsense as that will mess up the local monitoring, correct?
So for clients (slaves) in general, where do you specify the user credentials they use to connect to the master?
-
Also, I did already try putting the monuser/secret credentials in pfsense and add LISTEN <pfsense LAN IP> but when I configured my Synology to connect to pfsense it says cannot connect to the network UPS or something along those lines.
-
@kevindd992002 said in NUT package:
Ahh, I see. But then you also said in one of your posts there that it is not recommended to modify the monuser credentials in the upsd.users advanced settings in pfsense as that will mess up the local monitoring, correct?
So for clients (slaves) in general, where do you specify the user credentials they use to connect to the master?
You are adding to upsd.users rather than changing the content already there.
Client side credentials are in upsmon.conf. Server side are in upsd.users.
-
I'll re-test with the Synology when I get a chance.
-
I see. What did you exactly mean by this comment in that thread then?
"For what it's worth, the lines you have in the advanced section for ups.conf have no effect and can be deleted.
The lines in the advanced section for upsd.users override the automatic content for upsd.users and prevent local monitoring on the pfSense unit from functioning correctly (not recommended). If you want to try this approach, you would need to add the corresponding lines in upsmon.conf for it all to work.
Just FYI."
-
I also have another random issue. Sometimes, I reveive a notification email that the communication with the UPS is lost even though nothing is really happening with the UPS (no blackouts, power dips, etc.). I don't understand why I receive that but as soon as I go in the GUI, everything is happy. Any ideas?
-
Okay, I tested with the Synology. With DSM 6.2, I was not able to find a way to change the user/password for a remote monitor. Best that I can tell, they've moved all the stuff inside a service library.
So, this leaves us with a problem. The Synology is hard coded to the name "ups", user "monuser", and password "secret". The pfSense NUT package also uses the user "monuser" for the local monitor. Since upsd will ignore the second occurrence of monuser in the upsd.users file, there is no way to reconcile the current pfSense package and the Synology.
In order to make this work again, a change to the pfSense package is required. I have created a PR that will address this. You can track the PR here.
After installing the new version of the NUT package (2.7.4_7), you should follow the instructions above to add user "monuser" in the "Additional configuration lines for upsd.users" section.
BTW, one thing I forgot to mention earlier, your ups must be named "ups" in order to work with the Synology.
-
Ok, that's great :) I'll wait for this PR to be merged to master and will test again. Thanks for the quick support.
-
@kevindd992002 said in NUT package:
Ok, that's great :) I'll wait for this PR to be merged to master and will test again. Thanks for the quick support.
No problem
-
Oh btw, do you have any thoughts on the random disconnection issues I'm experiencing? It looks like it is related to the USB drivers or something.
-
@dennypage said in NUT package:
In order to make this work again, a change to the pfSense package is required. I have created a PR that will address this. You can track the PR here.
Renato was super fast in pulling the PR in. Thanks Renato!!!
Don't forget that your ups must be named "ups" for remote access by the Synology to work.
-
@kevindd992002 said in NUT package:
Oh btw, do you have any thoughts on the random disconnection issues I'm experiencing? It looks like it is related to the USB drivers or something.
Usually this is associated with the bridge chip. Things that I would recommend to try:
- Use a high quality cable to the UPS
- Try a different USB port on the host (particularly USB3 vs USB2)
- If you have a hub involved, try removing it
- If you don't have a hub involved, try adding one (hub bridge chips are usually different than host bridge chips)
Also, have a look in the system log to see of there are any USB messages concerning the disconnect/reconnect.
-
Wow, that was real fast! When a PR gets merged to master, does pfsense automatically upgrade the package? And yes, I already renamed my UPS to "ups", thanks for the tip!
-
I'm using the supplied cable from APC and I believe it is high quality. I use an PCEngines APU2C4 board for my pfsense box which only has two built-in USB3 external ports and tried both of them already. No hub involved but yeah I can try.
Yeah, I might dig into the logs and correlate with the timestamp of the notification email.
FWIW, I have the same setup in another house (same UPS, pfsense box, and cable) and never received a communication error with that.
-
@kevindd992002 said in NUT package:
Wow, that was real fast! When a PR gets merged to master, does pfsense automatically upgrade the package? And yes, I already renamed my UPS to "ups", thanks for the tip!
It's not normally this fast. Renato is a great guy, trying to help us out.
Anyway, I expect that the updated package is available to you. It was already available in the factory package repo when I posted earlier.
You have to explicitly upgrade the package. See System / Package Manager / Installed Packages.
-
@kevindd992002 said in NUT package:
I'm using the supplied cable from APC and I believe it is high quality. I use an PCEngines APU2C4 board for my pfsense box which only has two built-in USB3 external ports and tried both of them already. No hub involved but yeah I can try.
Yeah, I might dig into the logs and correlate with the timestamp of the notification email.
FWIW, I have the same setup in another house (same UPS, pfsense box, and cable) and never received a communication error with that.
Definitely worth looking at the logs for anything about the comm error. FWIW, I've had generally good experience with the APU2, but haven't used a UPS with it. Of course, it's possible it's a flakey cable or UPS unit.
-
Yeah, I got it to work now :) As for WinNUT, do you have any epxerience with it? Is there a GUI version that I can use for my Windows machines?
-
Well, it could be also a conflict with apcupsd as I have it installed in this box as well. I just removed it and let's see if that solves the issue.
-
@dennypage said in NUT package:
@kevindd992002 said in NUT package:
-
I installed apcupsd and noticed some discrepancy with NUT. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date (NUT) but BATTDATE shows the correct date of 2016/05/11. While NUT shows the battery.date as 2001/09/25 which doesn't make sense. Any ideas?
-
Also, is the APCUPSD-UPS drive client of NUT the "remote apcupsd" connection method that @Grimson is referring to?
-
Is there a guide for NUT that I can read?
-
With NUT, can you set pfsense and other servers in the network to turn off when the battery charge hits 70%?
-
The pfSense NUT package reports what the NUT upsc command returns (without interpretation). Either the NUT driver that supports the UPS doesn't handle the string correctly, or apcupsd caches the battery change date in the local file system. I would consider the caching to be highly unlikely, but it's possible. Either way, the best place to enquire would be the NUT mailing lists. You can find information here.
-
Yes.
-
Yes, the NUT support site has a user guide and manuals.
-
Yes, local and remote shutdown is what NUT does for a living. Information on remote access in the second post of this thread. Plenty of discussion about controlling shutdown percentages earlier in this thread. Look for things like this:
ignorelb override.battery.charge.low = 50 override.battery.runtime.low = 60See the 'ignorelb' section in the ups.conf manual for details on this.
I take it that you just enter these arguments in the "extra driver arguments" section and you're all set. Are these globally applicable though, meaning the same override settings will apply for the master and slaves?
Also, do I need to set both or just the percentage? What's a good value if I aim to "preserve" battery life? Or is it generally recommended to run the UPS (when mains are cut) until the battery is depleted so that you actually take advantage of the the full capacity of the battery?
-
-
Yes, the slaves follow the master. The master sends the slaves a shutdown order, and then waits for them all to disconnect. Once the slaves have disconnected, the master shuts down.
Yes, the battery overrides go in the Extra Arguments to driver section. One or both is up to you. If you are running a Synology as a slave, I would certainly set the runtime.low a bit higher to ensure that the Synology has sufficient time to shutdown. I believe I'm using 300 on mine.
As to charge.low, that's personal preference. The more times you discharge a lead acid battery the shorter its life, but that's why you have a UPS in the first place isn't it? The trade off between surviving an outage and battery health is a personal choice. Note that even if you baby the battery, you're still going to have to replace it every few years.
