search for: amdbox

...in making little headway. This system is running Debian Wheezy and connected to an APC BackUPS ES550. Starting things manually seems to go well, but my startup script fails, and nothing is logged anywhere. This may not be a NUT question per se, but I don't know where else to turn. What works: amdbox:/etc/nut# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 Using subdriver: APC HID 0.95 amdbox:/etc/nut# /sbin/upsd Network UPS Tools upsd 2.6.4 fopen /var/run/nut/upsd.pid: No such file or dire...

On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote: > There is no other information provided, and there is nothing in the log to help > either. Can anyone tell me what I need to do to make this output some useful > information that I can use to further trouble-shoot the problem? In general, if a startup script isn't doing what I think it should, I run

...as there was no match for the MODE in the switch statement of the start_stop_client function. I "knew" that I had set that correctly (to standalone), so I modified things a bit to show just what it was trying to match rather than look at nut.conf. It was indeed incorrect in the conf file: amdbox:/etc/nut# grep MODE /etc/nut/nut.conf # The MODE determines which part of the NUT is to be started, and which # The values of MODE can be: # Since this MODE is opened to the network, a special care should be applied MODE=standalone: Not sure why I felt the need to end the line with a colon, but...