Re: [Nut-upsuser] initial configuration assistance
From your tip I did check that - it is indeed a script but as you say, running it gave no reference to the driver starting. So I found /etc/init.d/upsdrv and went directly to /usr/sbin/upsdrvctl start which gave this output: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 Check the cabling, port name or model name and try again Driver failed to start (exit status=1) According to the nut-2.0.4 data/driver.list file, the APC Smart-UPS is supported through the 'apcsmart' driver. You could try if running the driver in debug mode (by passing '-D' on the startup command line) will give a hint to why the driver fails to recognize your UPS. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance
Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 Check the cabling, port name or model name and try again Driver failed to start (exit status=1) Had you previously connected the UPS by USB? If so, you'll have to completely power-cycle it before it'll speak to the serial port again. Pull the input power and press-and-hold the off button until the unit gives a click, and then wait a while... -- Dr George D M Ross, School of Informatics, University of Edinburgh Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ Mail: [EMAIL PROTECTED] Voice: +44 131 650 5147 Fax: +44 131 667 7209 PGP: 1024D/AD758CC5 B91E D430 1E0D 5883 EF6A 426C B676 5C2B AD75 8CC5 pgpCy7B1FEBMo.pgp Description: PGP signature ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance, fixed
George Ross wrote: Driver failed to start (exit status=1) Had you previously connected the UPS by USB? If so, you'll have to completely power-cycle it before it'll speak to the serial port again. Pull the input power and press-and-hold the off button until the unit gives a click, and then wait a while... Thankfully this wasn't the issue, because the UPS is powering necessary systems and our next maintenance downtime isn't for a few months (: I know it wasn't the issue because I made a glaring mistake which I'll share for amusement's sake. I had planned to migrate the gentoo instance (where my test-nut installation resides) from one older machine to a newer one a couple of weeks ago, and incorrectly assumed that I'd now done it. Therefore, plugging the serial cable into the newer machine gave all sorts of no response over serial cable issues on the older - duh! It works beautifully now, especially since thanks to you guys I'd already fixed the issues that I would have encountered after getting the serial cable right! Now, onto the finer details of event configuration and working out exactly how to deal with our dual-PSU servers supplied by different UPS: Some work ahead for me. For clarity, and because someone mentioned Gentoo not being a commonly used platform here, I'll outline my steps to show how well it works. 1. (emerge -s nut;) emerge sys-power/nut 2. edit all the files under /etc/nut to suit 3. start the right driver(s) 4. start upsd That's it! In other words there doesn't seem to be any need for gentoo-specific doco. nut user and group and tty membership were all done automatically, and a nice standard /dev/ttyS0 was the right device for serial port 1. Kudos to the gentoo folks who made all this happen, and generally to the nut developers. Ciao, Greg the happy new nut user. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance, fixed
serial cable right! Now, onto the finer details of event configuration and working out exactly how to deal with our dual-PSU servers supplied by different UPS: Some work ahead for me. Good to hear that you got things going. As for the dual supply servers on two ups units, this is what lead me to use Nut in the first place. The docs discuss this setup: http://www.networkupstools.org/doc/2.0.1/data-room.html The main thing you need to make sure of is that your server does not freak when it looses power on one unit. We had some ML370 Compaq servers that would boot and run on one supply but if the server booted with all three supplies (yes three) plugged in and the one plug was pulled the server would shut off. Our dual unit servers seem to be fine loosing one supply (DL380) as I have moved the servers between UPS units by moving one plug at a time. In my scenario I used one server (actually a virtual server) to monitor all 20+ UPS units and then let the servers talk to it for status. Doug ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance, fixed
Doug Parsons wrote: http://www.networkupstools.org/doc/2.0.1/data-room.html Yeah I figured I'd stumble across that sort of doco when I start work on it - thanks for the link tho. In my scenario I used one server (actually a virtual server) to monitor all 20+ UPS units and then let the servers talk to it for status. Since you've brought this up, it's something I'm not sure I understand properly. The physical machine behind your virtual server only has one or two serial ports, right? How do you get it talking to so many UPSs? My understanding at the moment is I have two choices: 1: Physically connect each UPS to one (different) server, and have that server do the monitoring and management for that UPS. 2: Physically connect each UPS to one (different) server, and have one central server do the monitoring and management for all UPSs. Clearly it may be possible to physically connect two UPSs to a given server with two serial ports, but that's beside the point. Our UPSs for the most part don't have network support. Greg. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance
Hi Gregory, tis 2007-01-30 klockan 14:43 +0900 skrev Gregory Orange: Hi, I've browsed the archives back for a few months and nothing has jumped out at me as being helpful, but since there doesn't seem to be a search facility it's certainly possible I've missed what I'm looking for. Anyway, I wonder if someone can help me. I've very recently installed nut 2.0.4-r1 on a gentoo box and am in the initial stages of configuration and testing. Our APC Smart-UPS 3000 is connected with a 940-0024C serial cable, which seems to be a good one to use - I firstly removed the 940-1524C cable which happened to be dangling from the UPS. I've configured upsd.conf with [rack1ups] driver = apcsmart cable = 940-0024C port = auto desc = Rack 1 UPS and left most other files as default, except for following some parts of doco on initial setup. The port should be set to /dev/ttyS0 if you use the first com port. Then depending on the udev version the tty is owned by the tty group or the uucp group. Check by ls -al /dev/ttyS0. Add the nut user to the right group in /etc/group. This is more easy then trying to fix the udev rule. The problem: When I /etc/init.d/upsd start, I get this: Network UPS Tools upsd 2.0.4 Can't connect to UPS [rack1ups] (apcsmart-auto): No such file or directory Synchronizing giving up Try to start the driver first. /etc/init.d/upsdrv start Check that it is running and that it don't fail. Then start the deamon if it is ok. /etc/init.d/upsd start I'm running Gentoo ~X86 and use a homemade ebuild for nut-2.0.5 with some patches that i entered into the development trunk. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance
Arjen de Korte wrote: port = auto This won't work. You need to specify a serial port for this driver (see 'man 5 ups.conf' and 'man 8 apcsmart'). Only the 'newhidups' driver accepts 'auto' (anything actually), but that is an USB driver. Ah ok thanks - I won't switch between 'auto' and the serial port any more in my testing. I had just grabbed the idea to use auto from some examples floating about the web, but it's highly likely that they were using newhidups, which I won't be. The problem: When I /etc/init.d/upsd start, I get this: Network UPS Tools upsd 2.0.4 Can't connect to UPS [rack1ups] (apcsmart-ttyS0): No such file or directory Synchronizing giving up I would expect some lines showing that the driver is started, so I doubt that the driver is running. Are you sure that /etc/init.d/upsd is an init script and not a link to the upsd binary? What does the output of 'ps aux|grep ups' show when you've started this? From your tip I did check that - it is indeed a script but as you say, running it gave no reference to the driver starting. So I found /etc/init.d/upsdrv and went directly to /usr/sbin/upsdrvctl start which gave this output: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 Check the cabling, port name or model name and try again Driver failed to start (exit status=1) Charles: thank you for the Google tip - that will be most helpful. As for the port, it is indeed /dev/ttyS0. Kjell: User and group nut were auto-created by the install, and nut belongs to tty group too. Armed with this info, I'll get some serial port help onsite here and report any successes or more queries. Thank you all for your help so far. Greg. -- - - Gregory Orange Phone: +61 8 9387 7955 System AdministatorFax: +61 8 9387 6686 MetOcean Engineers Pty Ltd http://www.metoceanengineers.com System Administrators Guild of Australia http://www.sage-au.org.au - - ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] initial configuration assistance
I've configured upsd.conf with [rack1ups] driver = apcsmart cable = 940-0024C port = auto This won't work. You need to specify a serial port for this driver (see 'man 5 ups.conf' and 'man 8 apcsmart'). Only the 'newhidups' driver accepts 'auto' (anything actually), but that is an USB driver. desc = Rack 1 UPS and left most other files as default, except for following some parts of doco on initial setup. The problem: When I /etc/init.d/upsd start, I get this: Network UPS Tools upsd 2.0.4 Can't connect to UPS [rack1ups] (apcsmart-auto): No such file or directory Synchronizing giving up auto is replaced with ttyS0 when I change 'port' to '/dev/ttyS0' I would expect some lines showing that the driver is started, so I doubt that the driver is running. Are you sure that /etc/init.d/upsd is an init script and not a link to the upsd binary? What does the output of 'ps aux|grep ups' show when you've started this? Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
