similar to: Powervar UPS with nut

On Mar 8, 2024, at 8:22?AM, Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > I've installed 2.8.1 on a Raspberry PI 5 using Pi OS bookworm 64 bit (Debian 12) with success. > > When I take that same configuration to a PI 3B running bookworm 32 bit, compile from source, use the same files from /etc/nut, I get a 'nut-monitor ups at

The "#! <shell>" is a *nix thing that exists in every *nix I have ever seen, for as long as I know (mid 1980's for me . . ) and is used to specify what shell is to be loaded to run that script, since there are many, and syntax is not compatible. Without it, the shell already running will try to run the script, which may well bomb, or no shell could be loaded at all. - Tim On

Hi all, On 5/16/23 20:08, Carsten Aulbert wrote: > Idly browsing the client sources, I guess I could try to add our logic > here[1] and use [2] to gather the battery stats from our UPS and then > decide if this UPS is considered critical or not. But for this, I would > need to dust off/excavate my ancient poor C knowledge ;-). > > I guess I will give this a try unless

I still have two questions: 1) How do I make the nut-server and nut-monitor find the right pid files? They are there but it seems they can't be opened. Permissions are nut/nut. 2) What do these error messages mean? Jan 19 16:14:52 mars nut-monitor[3781]: Init SSL without certificate database Jan 19 16:14:52 mars nut-monitor[3781]: Login on UPS [Eaton at localhost] failed - got [ERR

Roger, Well, I tried the same script method with openSUSE 13.2, and it still did not execute. So I tried the system method, and it worked 1 time out of 3 attempts. I captured the last failure: 2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't claim USB device [2a37:5110]: No such file or directory 2015-09-04T11:43:38.825970-04:00 linux-5048 upsdrvctl[1887]: Network UPS

Stefan Schumacher via Nut-upsuser writes: > I am considering returning the device to the online shop I bought. As > it is, it's nothing but trouble. Can you recommend a small UPS (1 > Server) that is guaranteed to work flawlessly with NUT? I've had good experience with Cyberpower units, as long as they're included NUT's hardware list. -------------- next part

On 19.01.24 17:02, Stefan Schumacher via Nut-upsuser wrote: >Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting >Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting this looks like someone repeatedly killed nut server. This not a problem of UPS. -- Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this

Roger, rtd at linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 0.000000 debug level is '3' 0.000405 upsdrv_initups... 0.004386 Checking device (0930/6545) (002/002) 0.004431 Failed to open device, skipping. (Permission denied) 0.004442 Checking device (1D6B/0002)

> 1) How do I make the nut-server and nut-monitor find the right pid files? They are there but it seems they can't be opened. Permissions are nut/nut. Actually, if the preceding lifetime of the service was a graceful stop, the exiting daemon should have removed its PID files. Then the newly starting one would check and not find them - as I wrote before - to make sure there is no hung old

I didn't think to look for a log (attached), but now looking in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what

linux-5048:/home/rtd # ldd /usr/local/ups/bin/usbhid-ups linux-vdso.so.1 (0x00007fff403fc000) libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f7c34b56000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7c34939000) libc.so.6 => /lib64/libc.so.6 (0x00007f7c34590000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f7c34378000)

Charles, 3.16.6.-2-desktop Keep in mind, despite the subject line, that this has been openSUSE 13.2 recently. I had hoped it would work better than 13.1, but so far hasn't. When I was trying with openSUSE 13.1, it was kernel 3.11.6-2-desktop. Rob Groner Software Engineer Level II RTD Embedded Technologies, Inc. ISO 9001 and AS9100 Certified Ph: +1 814-234-8087

Tim, Thanks for the help! No, I didn't already know that... I swear, the more time I spend at this, the less I seem to be understanding. I know that it had to be finding the libusb-compat I had just installed, because configure hadn't worked before that, and now it did. But finding useful version information seems to be almost impossible. Rob Groner Software Engineer Level II RTD

Roger, Thank you for the help. I tried what you suggested, going the system service unit route. Well...that works. So unfortunately, it doesn't provide a lot of debugging information. But I guess it also gives me a method I can move forward with. I had preferred the shutdown script method because it was a little more straight-forward, and possibly more portable. This guide is meant to

Charles, dmesg doesn't say anything when "usbhid-ups -a rtdups -k" is executed. I'm not sure which USB lib it compiled against. I installed them via "zypper install libusb-*". I'll try to find the version that got installed, as that WOULD be one thing that might have changed since the last time I had this working. I'm not sure how to check for multiple

Well, I've spent a couple hours on this, unable to figure it out. I removed the libusb-compat-devel package using zypper. And I've downloaded, built, and installed libusb from sourceforge. But trying to configure nut now I get "USB drivers requested, but libusb not found", no matter what I put for --with-usb-libs. Continuing to flog away at it... Rob Groner Software

Thanks Charles, you were right about that. Here is what I tried...I installed openSUSE 13.1 from scratch (which means no libusb). I then took libusb-1.0 from the sourceforge site and built and installed it. Still it got the "cannot find libusb" error. So, looking at the sourceforge site, is see it mention that to work with the older libusb-0.1, you had to use libusb-compat-0.1.5.

And now....suddenly, and so far unexplainably....it works again. I did the same as before, installed openSUSE 13.1 from scratch, then installed the libusb* libraries. And now...it works, so far reliably. I'm certain that there is some micro-step I started doing different than last time. For example, I used to install jedit from the command line after install, but I had started installing

So far, the systemd service unit is working perfectly. Halleluia! For reference, here are the libs associated with the usbhid-ups driver: rtd at linux-fnda:/etc/init.d> ldd /usr/local/ups/bin/usbhid-ups linux-vdso.so.1 (0x00007fffecd25000) libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007ff3b841b000) libpthread.so.0 => /lib64/libpthread.so.0

Thanks again Tim. I installed openSUSE from scratch, without installing libusb anything. I tried configure, and it failed because it couldn't find libusb. I used ldconfig to see what the system could see. It found 3 entries with "libusb" in them. I then built and installed the last update of libusb-0.1 (not libusb-compat or libusb-1.0). I tried configure, and it ran without