I went to the link to test the power off if the battery gets to low. Here is what I got on the command line. root at odroid-u2:/etc/nut# /usr/local/ups/bin/upsdrvctl -t shutdown -bash: /usr/local/ups/bin/upsdrvctl: No such file or directory root at odroid-u2:/etc/nut# find / -name upsdrvctl /sbin/upsdrvctl ^C root at odroid-u2:/etc/nut# /sbin/upsdrvctl -t shutdown Network UPS Tools - UPS driver controller 2.6.4 *** Testing mode: not calling exec/kill 0.000000 If you're not a NUT core developer, chances are that you're told to enable debugging to see why a driver isn't working for you. We're sorry for the confusion, but this is the 'upsdrvctl' wrapper, not the driver you're interested in. Below you'll find one or more lines starting with 'exec:' followed by an absolute path to the driver binary and some command line option. This is what the driver starts and you need to copy and paste that line and append the debug flags to that line (less the 'exec:' prefix). 0.007145 Shutdown UPS: serverups 0.007618 exec: /lib/nut/usbhid-ups -a serverups -k root at odroid-u2:/etc/nut# So I guess it's saying it will not work but to copy and paste some place the line at the end. It that right? If so what file do I copy and paste it in? -Raymond Day -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20161030/dd09b4a6/attachment.html>
On Sun, 30 Oct 2016, Raymond Day wrote:> Below you'll find one or more lines starting with 'exec:' followed by an absolute > path to the driver binary and some command line option. This is what the driver > starts and you need to copy and paste that line and append the debug flags to that > line (less the 'exec:' prefix). > > ?? 0.007145???? Shutdown UPS: serverups > ?? 0.007618???? exec:? /lib/nut/usbhid-ups -a serverups -k > > So I guess it's saying it will not work but to copy and paste some place > the line at the end. It that right? If so what file do I copy and paste > it in?Copy and paste to the command line. Roger
I did just copy and paste on the command line like this: root at odroid-u2:/etc/nut# Shutdown UPS: serverups -bash: Shutdown: command not found root at odroid-u2:/etc/nut# /lib/nut/usbhid-ups -a serverups -k Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 Initiating UPS shutdown root at odroid-u2:/etc/nut# Don't know why it says "-bash: Shutdown: command not found" But the next command "/lib/nut/usbhid-ups -a serverups -k" sounds like it turn off the UPS for a sec. then back on. So not sure if it did a poweroff command before that. Something is wrong with reboot on this any way I can say reboot and it seems like it does but I have to unplug the power to it for a few sec. then it will boot up. So I did have to pull the power and back in after that last command for it to boot backup. -Raymond Day
> Below you'll find one or more lines starting with 'exec:' followed by an > absolute path to the driver binary and some command line option. This is > what the driver starts and you need to copy and paste that line and > append the debug flags to that line (less the 'exec:' prefix).?? 0.007145???? Shutdown UPS: serverups ?? 0.007618???? exec:? /lib/nut/usbhid-ups -a serverups -k On Sun, 30 Oct 2016, Raymond Day wrote:> I did just copy and paste on the command line like this: > > root at odroid-u2:/etc/nut# Shutdown UPS: serverups > -bash: Shutdown: command not found> Don't know why it says "-bash: Shutdown: command not found"There is no command Shutdown with an upper case "S". In any case, you only needed to copy the lines preceeded by "exec".> root at odroid-u2:/etc/nut# /lib/nut/usbhid-ups -a serverups -k > Network UPS Tools - Generic HID driver 0.37 (2.6.4) > USB communication driver 0.31 > Using subdriver: CyberPower HID 0.3 > Initiating UPS shutdown > root at odroid-u2:/etc/nut# > > But the next command "/lib/nut/usbhid-ups -a serverups -k" sounds like > it turn off the UPS for a sec. then back on. So not sure if it did a > poweroff command before that.For more detail, try adding the -DD debug flags as suggested previously. Roger