NUT package (2.8.0 and below)

doktornotor

That's Eaton special.

athurdent

That's Eaton special.

So this is normal with EATON and I don't have to get it exchanged?

doktornotor

Yes, it happens with any Eaton I tried. Whether or not it's charging, NFC. The package only reports what's reported by firmware.

athurdent

Thanks, doc! :)

poluket

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.

dennypage

Have you checked the system log? In Status / System Logs / System / General, look for messages matching "ups" or "nut".

poluket

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: exiting

I 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

dennypage

Earlier in this thread:

https://forum.pfsense.org/index.php?topic=115349.msg679431#msg679431

poluket

ok, thanks

I will put the nut and usp on my linux server

thank you for your time

StarkJohan

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

cozkramer

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!

dennypage

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.

cozkramer

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..

dennypage

Your UPS is a network model, yes? If so, is there anything that is connecting to the UPS that could be initiating the self test?

cozkramer

No, it's the non-network model.. I've got two usb cables plugged into it.. One to a (stupid) Windows 7 machine I need for Photography work, and the other goes to the BSD rig.. I've slightly cheated a little here, the cable is plugged into a freenas machine and I have pfsense nut talking to nut on the nas. It's all bsd nuts though and so apparently they can't do anything but report it seems and I know the people here are nicer. =)

Here's a link to the unit I have https://www.tripplite.com/smartpro-120v-2.2kva-1.6kw-line-interactive-ups-tower-snmpwebcard-option-usb-db9-serial~SMART2200VS/

If you know of a way to replace Lightroom on a *Nix/BSD System, I'm all ears!

Thanks Danny!

dennypage

Different story then. NUT doesn't initiate a self-test by default, and the pfSense NUT package doesn't initiate a self-test, but that doesn't mean that the FreeNAS NUT package isn't doing it or that Windows isn't doing it. Before calling Tripplite, I would disconnect all but one USB or RS-232 cable and test each system stand-alone to see if it still happens.

I can't help you with Windows I'm afraid. I stopped running Windows around the XP timeframe. For a nice and cuddly Unix UI environment, I use Mac. As I recall, Lightroom runs a bit better on Mac than Windows. Adobe used to let you turn your Windows license in and get a Mac license in exchange, but I don't know if they still do that.

First time in my life someone has referred to me as one of the nicer people. :)

-Denny

cozkramer

It's always a different story when Microcrap is involved, isn't it…. I'd love to drop kick them to next century, but I refuse to give Apple any money. I've never liked how the OS was setup and you're stuck with whatever they let you have. but that's another topic, lol..

I've removed any trace of ups software from wincrap, and I may disable the service on the nas rig for a day and see, seem easier than trying to reach cables.. :/

I would have thought that the NUT service is the same on both PF and FreeNas and thus has the same functionality/or lack thereof. Incorrect presumption?

I've been a light user of *Nix/BSD since Slackware 4ish iirc and FreeBSD 3ish, I've just never been able to drop win as the software wasn't there for *nix/bsd. Now the only holdup is LR, and running LR under a VM just doesn't get it done, tried that recently..

These days, Adobe wants you to pay them monthly for their software, and if you refuse and buy the standalone, they remove features... bastids..

First time for everything! :) Anyone that can take what could be a stupid and/or silly question/issue and reply with helpful info in a concise manner gets my nice vote... 8)

-Scott

dennypage

@cozkramer:

I would have thought that the NUT service is the same on both PF and FreeNas and thus has the same functionality/or lack thereof. Incorrect presumption?

The NUT distribution itself is the same, but the package that configures and runs it is quite different. If you look at your pfSense system, you will see two packages:

nut-2.7.4_1                    Network UPS Tools
pfSense-pkg-nut-2.7.4_4        Network UPS Tools

The first one is the NUT package itself and the second one the the pfSense package for NUT. The pfSense package is what controls the NUT configuration and starts the NUT service.

cozkramer

Thanks Denny for some clarification there.

Is it wrong of me to then presume that pfSense has a control package for every add-on service/package?

If that's the case, is it possible to run other freebsd packages separately?

Thanks again! Hope I'm not too ot or anything.

dennypage

The list of supported packages for your pfSense version can be found in System / Package Manager / Available Packages. There are a good number of excellent FreeBSD packages directly supported in pfSense.

There are also many packages that are in FreeBSD that are not directly supported in pfSense. If you are interested in installing FreeBSD packages that are not directly supported by pfSense, you can search the forums for instructions on how to do this. In general, I would recommend against using unsupported packages unless 1) you have a very strong need for the package on your firewall, and 2) you are extremely confident of the security implications of having the package running on your firewall.