-
In case anybody else will need it; just make the appropriate changes for you in the line with "blazer_usb-ActiveJet.pid";
you can find your "driver_usb-upsname.pid" in /var/db/nut/ when NUT is running…I forgot about the ups name in the pid file. It had to be something stupid.
On the system I was testing on the ups is named "ups" and the driver name is "usbhid-ups". This results in a pid file named "usbhid-ups-ups.pid". I think I'll change the name of the ups to prevent this sort of mistake in the future. :)
-
Yesterday i saw in my pfsense, that there is an update for the nut package (2.7.4_3). Is it save to hit the update button, or will the custom Settings be lost after the update?
Best Regards
-
What version of the nut package are you currently running? If you are already running 2.7.4, then there should no issue with the update. If you are running a version prior to 2.7.4, then the settings will be converted from the old package to the new package, and may require attention. See the beginning of this thread for more information. If you are still unsure, post some information about your settings.
The current version is 2.7.4_4
-
What version of the nut package are you currently running? If you are already running 2.7.4, then there should no issue with the update. If you are running a version prior to 2.7.4, then the settings will be converted from the old package to the new package, and may require attention. See the beginning of this thread for more information. If you are still unsure, post some information about your settings.
The current version is 2.7.4_4
Thank you for the answer. I'm using the Version 2.7.4_3. Do i Need to save some Settings? I have set custom Parameters on the following fileds:
- Extra Arguments to Driver (optional
- Additional configuration lines for upsd.conf
- Additional configuration lines for upsd.users
Best Regards
-
Thank you for the answer. I'm using the Version 2.7.4_3. Do i Need to save some Settings?
In moving from 2.7.4_3 to 2.7.4_4 there is nothing special you need to do. The settings will all be maintained.
-
Thank you for the answer. I'm using the Version 2.7.4_3. Do i Need to save some Settings?
In moving from 2.7.4_3 to 2.7.4_4 there is nothing special you need to do. The settings will all be maintained.
Perfect, thank you!
-
Thanks for this nice package, works fine and look great!
Forgive me for being slightly OT, but is it normal for a UPS to stay at 100% Charging? It's my first UPS ever and running like this for 2 days now (EATON 3S 550). Shouldn't it stop charging when it's at 100%?
-
That's Eaton special.
-
That's Eaton special.
So this is normal with EATON and I don't have to get it exchanged?
-
Yes, it happens with any Eaton I tried. Whether or not it's charging, NFC. The package only reports what's reported by firmware.
-
Thanks, doc! :)
-
Hello,
sorry for my English :)
I think that I have the same problem than ecfx-xunil but I am a newbie.
PFsense version : 2.3.3 amd 64
NUT package version 2.7.4_4
I have an UPS FSP EP 2000
I use the nutdrv_qx driver. (without custom option)
it work fine but after a time, I have this message "Failed to retrieve status". I click on top to restart the service on the gui and i have again the value.
I have seen your message but I don't understand what to do to resolve the problem.
I need to chage the code?
Thank you for your help.
-
Have you checked the system log? In Status / System Logs / System / General, look for messages matching "ups" or "nut".
-
thank you for your help :)
the logs when I have the problem (newest entries on top):
Mar 7 13:48:30 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:25 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:25 kernel ugen3.2: <inno tech="">at usbus3 Mar 7 13:48:22 kernel ugen3.2: <inno tech="">at usbus3 (disconnected) Mar 7 13:48:20 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:17 upsd 90750 Can't connect to UPS [UPS-Local-USB] (nutdrv_qx-UPS-Local-USB): No such file or directory Mar 7 13:48:15 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:14 kernel ugen3.2: <inno tech="">at usbus3 Mar 7 13:48:11 kernel ugen3.2: <inno tech="">at usbus3 (disconnected) Mar 7 13:48:10 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:05 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:02 kernel ugen3.2: <inno tech="">at usbus3 Mar 7 13:48:00 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:48:00 kernel ugen3.2: <inno tech="">at usbus3 (disconnected) Mar 7 13:47:55 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:47:51 kernel ugen3.2: <inno tech="">at usbus3 Mar 7 13:47:50 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:47:48 kernel ugen3.2: <inno tech="">at usbus3 (disconnected) Mar 7 13:47:45 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:47:40 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:47:40 kernel ugen3.2: <inno tech="">at usbus3 Mar 7 13:47:37 kernel ugen3.2: <inno tech="">at usbus3 (disconnected) Mar 7 13:47:35 upsmon 80446 Communications with UPS UPS-Local-USB lost Mar 7 13:47:35 upsmon 80446 Poll UPS [UPS-Local-USB] failed - Driver not connected Mar 7 13:47:33 nutdrv_qx 96269 Permissions problem: Input/output error</inno></inno></inno></inno></inno></inno></inno></inno></inno></inno>and after a service reboot:
Mar 7 14:00:49 upsd 41029 User monuser@::1 logged into UPS [UPS-Local-USB] Mar 7 14:00:49 upsd 41029 Connected to UPS [UPS-Local-USB]: nutdrv_qx-UPS-Local-USB Mar 7 14:00:48 nutdrv_qx 41173 Startup successful Mar 7 14:00:47 upsd 41029 Startup successful Mar 7 14:00:47 upsd 40900 Can't connect to UPS [UPS-Local-USB] (nutdrv_qx-UPS-Local-USB): No such file or directory Mar 7 14:00:47 upsd 40900 listening on 127.0.0.1 port 3493 Mar 7 14:00:47 upsd 40900 listening on ::1 port 3493 Mar 7 14:00:46 upsmon 39909 Startup successful Mar 7 14:00:46 upsd 90750 Signal 15: exiting Mar 7 14:00:46 upsd 90750 mainloop: Interrupted system call Mar 7 14:00:46 upsd 90750 User monuser@::1 logged out from UPS [UPS-Local-USB] Mar 7 14:00:46 upsmon 80446 Signal 15: exitingI have found this:
https://www.nas4free.org/forums/viewtopic.php?t=946
In port #17, he change the pollinterval to 10/15. Maybe a solution?https://forums.freenas.org/index.php?threads/2-issues-behaviours-with-attached-and-identified-ups.24033/
or use a script with cron …like he say: "I would be very happy to know that there's another/better solution."
thank for read my message
-
Earlier in this thread:
https://forum.pfsense.org/index.php?topic=115349.msg679431#msg679431
-
ok, thanks
I will put the nut and usp on my linux server
thank you for your time
-
I just wanted to repeat a tip that dennypage (thanks!) mentioned earlier which seems to have helped me with my Eaton 5S repeatedly losing and reestablishing connection every few minutes on NUT 2.7.4_4 (haven't tried this UPS on earlier versions).
Changing the poll interval to 10 worked around my issue. I think the default value is something ridiculous like 2 which in my case catches the very brief flakiness in the USB connection.
Using the GUI, add the advanced setting "pollinterval=10" to ups.conf
-
I'm not sure if this is the right spot, but if not please correct location.
I've got a TrippLite Smart2200 connected with Nut running on Pf 2.4 using tripplite_usb, and ever since I've started using Nut the UPS runs a self-test once or twice a day.. Anyone have any thoughts or suggestions? I have no problems with a self test once a month or even once a week, but daily just kills the ups..
Thanks!
-
NUT itself doesn't invoke self-tests on a schedule. This is done by the UPS itself.
There are usually configuration parameters that can be viewed and modified in the UPS. The complete list of NUT variables can be found here. Note that a given UPS model will generally only offer a small subset of these variables. Use the upsrw command to discover the list of variables you can modify. For your particular issue, the variable you are looking to modify is ups.test.interval.
Further information on running commands can be found here. Be careful.
-
Thanks Denny!
After using upsrw, and only getting three outlet switch options, a delay shutdown and ups.id as modifiable, I fear a call to TrippLite is in order..
