similar to: passing nut_debug_level from upsdrvctl to drivers

On Jan 27, 2008 11:07 AM, Arjen de Korte <nut+devel at de-korte.org> wrote: > > >> I also think we should not encourage people to post debug output before > >> consultation with a developer. Most of the time, providing useful debug > >> output requires more than just running the driver with an arbitrary > >> number of -D flags anyway. > > Well,

Hi again, it seems to me that "upsdrvctl shutdown" fails to pass the "-u" flag to the driver. See drivers/upsdrvctl.c:shutdown_driver(), and compare to start_driver() in the same file. This has been so since ancient history (I checked back to 1.5.0), so there must be a reason, but I can't think of any. I have a good reason for passing "-u root": at the time

I did a test shutdown on a nut controlled UPS and it all went as expected except that when it got to: /usr/local/ups/bin/upsdrvctl shutdown Nothing happened. So the halt script went on and shut down the system. I waited a while but the UPS never turned itself off. Am I doing something wrong, or does this UPS not support this function? Thank you, David Mathog mathog at caltech.edu Manager,

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

Hello list, I'm fresh in using an ups for shutting down a linux server and i was thinking someone could give a hand at debugging a problem i stumbled to. I'm used to the redhat type of distribution, mainly centos 4/5, and off-course i installed nut and nut-client from the available rpm packages. After some reading i disconnected the server from the power supplied by the ups and

Hello list, I'm fresh in using an ups for shutting down a linux server and i was thinking someone could give a hand at debugging a problem i stumbled to. I'm used to the redhat type of distribution, mainly centos 4/5, and off-course i installed nut and nut-client from the available rpm packages. After some reading i disconnected the server from the power supplied by the ups and

Hello All I have a MicroDowell ups (BBox BP 1000) connected to a Gentoo box by serial cable. If I try to start the driver , I see the following : Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '13' ups_sync: send [\rP4\r] ups_sync: got ret 46 [#1000VA

On opensuse 10.3, i installed nut and configured my ups.conf like i did it on opensuse 10.2 by putting (10.3 , nut 2.2.0): [MGEpc675] driver = usbhid-ups port = auto desc = "MGEpc675" instead of (10.2 , nut 2.0.4) : [MGEpc675] driver = newhidups port = auto desc = "MGEpc675" But it doesn't work. It appears that upsdrvctl

Hi all, I'm currently trying to install a APC Back-UPS ES 700 on FreeBSD. This UPS has a usb connection to the PC and is recognized as: ugen0: APC Back-UPS ES 700 FW:829.D2 .I USB FWD2 rev 1.10/1.06, addr 2 my ups.conf looks like: [back-ups] driver = usbhid-ups port = auto desc = "server" When I now run /usr/local/libexec/nut/upsdrvctl start the output is: Network UPS Tools

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Anyone know what is the problem for this? thanks Andrew freebsd 540$ /usr/local/etc/rc.d/nut restart nut not running? (check /var/db/nut/upsd.pid). Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - Generic UPS driver 1.32 (2.0.4) UPS type: APC Back-UPS (940-0023A cable) Unable to open /dev/cuad0: Device busy Current user id: uucp (66) Serial port owner: uucp (66) Serial

I'm a linux newbie and having some trouble with NUT, can anyone assist? I've read the FAQ and various articles online by Peter Sellinger and others thoroughly. OS is ClarkConnect 4.2, which is based on CentOS4/RHEL 4. UPS is an APC SmartUPS 1500 (USB). Correct driver is believed to be usbhid-ups. No RPM for my OS was available past 2.0, so I built from source using NUT 2.2. I think

Hi all, New to NUT dev, i was hoping someone can clear up an issue i have with the unix socket naming for me (FYI my C is not that great). I'm using 2.0.5 and this stems from a problem with the general admin of Nut but looking at the code led me to think maybe it's a bigger issue (thus i joined this list). Right to start with if i have the following in ups.conf: [apc]

Hi everybody, I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable looks fairly simple: RX->RX , TX->TX and GND->GND. Using this cable and Minicom with 2400 8N1 I'm able to issue commands to the UPS using the "Megatec Protocol" http://www.networkupstools.org/protocols/megatec.html so I know the UPS is fairly "intelligent" :-) and the

Hi, I'm running a Debian server (amd64) with the latest nut package (2.0.3-4). The server is connected to a Cyberpower OP750E ups. This seems to be connectable using nut with the cpsups driver. I've configured /etc/nut/ups/conf with the correct information. Here is what i get when trying to load the driver : serveurmeteo:/home/did# /sbin/upsdrvctl -v start myups Network UPS Tools -

Here is my ups.conf... [ups-router] driver = usbhid-ups port = auto desc = "Powerware 3110 - Router" [ups-server] driver = usbhid-ups port = auto desc = "Powerware 3110 - Server" Here is the output from upsdrvctl start... Network UPS Tools - UPS driver controller 2.2.0 Network UPS Tools: 0.28 USB communication driver 0.28 -

Hi List, I just got myself a new everpower-1000va. according to the compatibility list, the 'safenet' driver supposed to support it, however, when I try, I get this in syslog: Jul 24 15:05:22 tv upsd[26458]: Can't connect to UPS [everpower1000] (safenet-ttyS1): No such file or directory this is my ups.conf: [everpower1000] driver = safenet port = /dev/ttyS1 desc =