Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD
happy new year fellows, 2006/12/29, Arjen de Korte [EMAIL PROTECTED]: It looks like the connection between driver and upsd is continuously dropping. This could be a driver problem or an upsd problem. Since the driver is not reporting anything out of the ordinary, I suggest to checkout the latest version from SVN. There were a couple of problems with the staleness checks in upsd which were fixed in the trunk. Alternatively to SVN, you may upgrade to 2.0.5-pre1, which was released on Dec 20. I think this contains all of the relevant bugfixes. Ah, I forgot about that. Indeed, the fixes are in nut-2.0.5-pre1, so that one should be fine also. Never mind that remark, it looks like I have some backporting to do from the trunk if we want to include these changes. The changes to server/upsd.c and server/sstate.c are currently *not* in Testing and therefor, *not* in nut-2.0.5-pre1. Other than that, I think that some recent changes to common/state.c should be backported too, to fix a memory leak in state_delcmd(). Arnaud, what do you think about that? bug fixes are definitely welcome for the final 2.0.5... so don't hesitate to backport theses change. More generally, I'll start a discussion about the driver polling rate (2 sec) which was accurate with the dumb and old smart units, but which is really too high for recent / verbose units (that also support an interrupt / notification mechanism, allowing to lower the polling rate, while not missing events). thanks for the MGE support during my vacation ;-) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD
bug fixes are definitely welcome for the final 2.0.5... so don't hesitate to backport theses change. I already did. :-) More generally, I'll start a discussion about the driver polling rate (2 sec) which was accurate with the dumb and old smart units, but which is really too high for recent / verbose units (that also support an interrupt / notification mechanism, allowing to lower the polling rate, while not missing events). That is a no-brainer. We already support changing the polling rate through the -i command line option for the drivers. Just advise people to set this to 30 seconds or so for the drivers in question and we should be fine. thanks for the MGE support during my vacation ;-) The bill is in the mail. ;-) 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] Help with nut 2.0.4, MGE Ellipse 1000 and FreeBSD
2007/1/2, Arjen de Korte [EMAIL PROTECTED]: bug fixes are definitely welcome for the final 2.0.5... so don't hesitate to backport theses change. I already did. :-) ok, thanks. I've not yet digged the commit list... More generally, I'll start a discussion about the driver polling rate (2 sec) which was accurate with the dumb and old smart units, but which is really too high for recent / verbose units (that also support an interrupt / notification mechanism, allowing to lower the polling rate, while not missing events). That is a no-brainer. We already support changing the polling rate through the -i command line option for the drivers. Just advise people to set this to 30 seconds or so for the drivers in question and we should be fine. I'll be back on that later... thanks for the MGE support during my vacation ;-) The bill is in the mail. ;-) ;-) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Geek Squad UPS Systems
Kory Hamzeh wrote: We are interested in using Nut on our Federa 6.0 servers. However, our UPS systems are sold under the name Geek Squad (sold through the Best Buy chain of department stores). I'm pretty certain Geek Squad does not manufacture these units and they just rebrand them. Does anyone know who makes these units or what they are compatible with in terms of driver level protocol? The ones we use are the 1500VA capacity model. If this is not the proper forum for this question, please let me know. According to this link, the 1285VA (and the 1500VA) model uses PowerPanel, which happens to be the same software as my cyberpower ups does.. http://www.bestbuy.com/site/olspage.jsp?skuId=7383985type=productproductCategoryId=cat08029id=1122654249041 The lower prices models ( 1000VA) looks like the old contact-closure APC ups, and come with a power management application for windows 98/xp/nt if the ups uses the cyber power command set, you might be in luck, as Arjen and I finally have a working cpsups driver... an easy way to test it is: open your serial port to your ups with cu (ie cu -s 2400 -l /dev/serialdevicename) once it is opened, hit enter (a couple times if needed). if you see a #2, type in P4enter, and post back the info it returns. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] ownership of pid directory
On Tue, 02 Jan 2007 09:53:46 -0500, Doug Reynolds wrote: I have an answer to your question now (i don't recall if you got an answer now) since I run freebsd, I finally secure nut on my system. my /var/db/nut dir looks like this: drwxr-x---2 nutmon nut 512 Jan 2 09:17 nut/ I run my driver as user nutmon, group nut. If you goto your /etc/group file, add user UUCP to the nut group.. then add: user = nutmon It sounds like the permission on your /var/db/nut are probably 700 or 740.. on my system orignially it was owned by uucp:dialer, that could be your problem if it is own by uucp:uucp I ran into the same thing when I switch over to a non-root setup. I sure you trouble has something to do with permissions.. Also, don't forget to put: # Insert other shutdown procedures here if (test -f /etc/killpower) then echo Killing the power, bye! /usr/local/libexec/nut/upsdrvctl shutdown fi right before the: echo '.' exit 0 in your /etc/rc.shutdown for freebsd, as if you don't, your ups won't shutdown, and could cause a race condition. Thanks a million! I am now past that hurdle and as near as I can tell, it all now works. -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
RE: [Nut-upsuser] Geek Squad UPS Systems
an easy way to test it is: open your serial port to your ups with cu (ie cu -s 2400 -l /dev/serialdevicename) once it is opened, hit enter (a couple times if needed). if you see a #2, type in P4enter, and post back the info it returns. Doug, Thanks for the info. I will give it a try. It has both a USB and a serial port. Eventually, I'd like to use the USB interface instead of the serial. Few questions: 1. Off hand, do you know the name of the serial device for Com1 on Fedora Core 6.0? 2. If this works, do I need to download the latest development version to get your drive? 3. Also, how do I tell the drive to use the USB interface? Thanks, Kory ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Revive support for HP PowerTrust?
Hi everyone. I'm currently looking for a monitoring program for a HP PowerTrust UPS (A2998A) for Linux. It seems that nut supported these UPSs until version 1.4.3. What was the reason for the driver being removed from nut? Are there plans to reintegrate it? I was playing around with the UPS and put the results here: http://www.project-athlon.org/wiki/index.php/HP_PowerTrust_A2998A They seem to be consistent with the docs inside the former hp.c Greetings, Jakob Haufe (sur5r) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Geek Squad UPS Systems
Kory Hamzeh wrote: Thanks for the info. I will give it a try. It has both a USB and a serial port. Eventually, I'd like to use the USB interface instead of the serial. We have not tested the USB connection, but based on other drivers, this likely is not going to work. Unless the serial-to-USB converter that is most likely used in the UPS is recognized by the kernel (in is installed as a /dev/ttyUSB* device), this requires 'serial_usb.o' which is not yet available. Few questions: 1. Off hand, do you know the name of the serial device for Com1 on Fedora Core 6.0? 2. If this works, do I need to download the latest development version to get your drive? Yes, you do. You need the version from the SVN trunk which I'm about to submit in a couple of minutes from now. 3. Also, how do I tell the drive to use the USB interface? If you connect the USB cable and a /dev/ttyUSB* interface is made available, you could use that. Otherwise, you don't (it won't work). Best regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] SNMP/management front-ends
On 1/2/07, Eric A. Hall [EMAIL PROTECTED] wrote: I've been using TrippLite's PowerAlert software with my RM2200XL2U rack system and my APC BackUPS desktop systems. Unfortunately it doesn't work with openSUSE 10.2 (the software has problems with the serial port and UPS interfaces on openSUSE 10.2), so I've been looking at other options. I see that openSUSE 10.2 includes NUT, and it appears to work with my TrippLite UPS via the USB driver (thanks!). It looks like upsc is reporting most of the data, although it's missing a couple of things like battery charge, and the ability to control the four independent loads. The equipment that I was testing against has been put away, so I can't test much myself. I have a vague idea of the changes necessary for load control and battery charge, so if you want, you can try building from source, and we can work on that in the SVN tree. Bear in mind that bugs in driver testing could shut your system down at a bad time, so caveat emptor. SVN instructions: http://www.networkupstools.org/source.html I can hack up a Cacti PHP script to monitor UPS state via the upsc client in the meantime. I'll have to manually enumerate the UPS names associated with a host target (is there a way to probe for them with upsc now?), but otherwise it ought to be pretty straightforward scripting. Here is some information on the protocol, and specfically enumerating UPSes: http://boxster.ghz.cc/projects/nut/browser/trunk/docs/protocol.txt#L128 -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Revive support for HP PowerTrust?
On 1/2/07, Jakob Haufe [EMAIL PROTECTED] wrote: Hi everyone. I'm currently looking for a monitoring program for a HP PowerTrust UPS (A2998A) for Linux. It seems that nut supported these UPSs until version 1.4.3. What was the reason for the driver being removed from nut? Are there plans to reintegrate it? Quoting from the FAQ: Q: My favorite UPS driver disappeared after an upgrade. What now? A: Drivers are occasionally removed from the tree if they are no longer receiving maintenance. There have been several architectural changes to the driver code in recent times, and drivers which were not converted by someone are eventually dropped. This is called progress. We do this in order to avoid a situation where someone believes that a driver is being maintained when it is actually rotting slowly in the tree. It also keeps the tree free of old compatibility hacks for code that nobody actually uses anyway. To get a driver back into current releases, you need to convert it yourself or get someone to do it for you. This is not difficult. The hardest part of any driver is decoding the protocol, and that's already been done in the old version. So, If you don't mind doing some testing (and you're prepared to deal with any side effects, like accidentally turning the UPS output off while debugging), then we can work with you to try and resurrect the driver. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
