similar to: Are UPS shutdown commands automatically sent?

Roger, Following your guide, it now works great, shutting down the UPS after the system has shutdown. I went with the bash script method. I have noticed, however, that the command to the UPS to do the delayed shutdown comes RIGHT as openSUSE is shutting down. While that is a good thing as far as timing and the potential race is concerned, I have seen it once where the UPS received the command

Roger, Your guide is already my go-to source, especially since openSUSE 13.1 is our currently supported system (though I'm doing this testing on Porteus due to its file system resilience). It's AWESOME, btw. Very helpful. I'll spend some time tomorrow going through chapter 6 and trying again. Sincerely, Robert G. Groner Software Engineer RTD Embedded Technologies, Inc. ISO 9001

Roger, So I'm pursuing the strategy of issuing the "upsdrvctl shutdown" command script when the OS (Porteus, in this case) is shutting down. I so far can't get it to do it, but I'm sure I'll overcome it, but I realized something else might be a problem. Won't that script execute every time Linux is shutting down, including rebooting? So, if I choose to reboot my

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

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

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

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

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

For fun, if you want to see where the system thinks it is linking a library from, you can use "ldconfig -p" and it will give you a path to all known libraries that it can find. If you have one loaded, and it can't find it (odd directory, etc.) you can always amend "LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier . . . . PKG . . . is for the build

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

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

I found something particularly strange while trying out different things: I started up upsdrvctl, upsd, and upsmon. I then stopped upsdrvctl, and tried starting the usbhid-ups driver a few times. Each time I executed the driver, it indicated an instance was already running, stopped it, and then started it again....which is what it should do. I then added -DDDD to the command....and then it

rtd at linux-5048:~> lsusb -vvv -d 2a37: Bus 001 Device 005: ID 2a37:5110 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor

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.

I am running tests on my system and UPS, making sure that it is reliably able to come up, detect power loss, shutdown safely, and then come back up when the power returns. It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn't respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing

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)

iSerialNumber does not need to be unique per device - it is not very many bits wide. I?m pretty sure I don?t *need* iSerialNumber?I mean, I could just remove it from the report descriptor altogether. But since it is available to give, and we are writing each board?s serial number into flash as part of the micro-controller programming (we aren?t talking a staggering number of boards per year

Rob - Just stepping in from the sidelines . . . with a few tidbits. Nut uses pkgconfig to find and identify stuff as part of it's build . . . So, depending on where your libusb install went, if it wasn't in the default "PKG_CONFIG_PATH" setting, it won't be found. Much like other shell variables, you can adjust that setting to find anything you like . . . IE

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