Re: [Nut-upsuser] memory leak in newhidups 0.28 (2.0.3)
There is a memory leak in newhidups. After 23 days uptime it used 138M memory. Apart from the memory leak, the system works ok. Is there anything I can do to help fix this problem? Sure. Please upgrade to the latest version and see if the problem still exists. The version you're using now is well beyond its 'use by date'. 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] Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon ?
You can't start a driver multiple times for the same UPS. So if you ran 'upsdrvctl start', the script '/etc/init.d/nut start' (that will do so also) will fail. You need to run 'upsdrvctl stop' first, if the driver is running already for whatever reason. Thank you Arjen for pointing this out. After reading up on the man pages, I also fixed the MONITOR line in upsmon.conf to pointing to [powerware] as defined in ups.conf. So I redid this having stopped upsdrvctl and then starting nut, now without the upsdrvctl problem but still with the lost communications problem (see below). Do you have any leads what might cause this or places to look/check? # /etc/init.d/nut start Starting Network UPS Tools: upsd upsmon. Broadcast Message from [EMAIL PROTECTED] (somewhere) at 12:35 ... Communications with UPS [EMAIL PROTECTED] lost Broadcast Message from [EMAIL PROTECTED] (somewhere) at 12:35 ... UPS [EMAIL PROTECTED] is unavailable Thanks, --theo ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon ?
Theo G. Kanter wrote: Thank you Arjen for pointing this out. After reading up on the man pages, I also fixed the MONITOR line in upsmon.conf to pointing to [powerware] as defined in ups.conf. Ooops. I missed that one, but you've found that out yourself already. Good! So I redid this having stopped upsdrvctl and then starting nut, now without the upsdrvctl problem but still with the lost communications problem (see below). Do you have any leads what might cause this or places to look/check? You're still using nut-2.0.4, do you? It might be helpful to upgrade to the latest stable version (nut-2.0.5), since some startup problems (the server starting when the driver isn't ready yet) were resolved. Unfortunately, your /etc/init.d/nut script sends all information startup to /dev/null, so I'm not sure if this is the problem. It may help to see if you can connect to the server, to see if it is showing information from the driver upsc [EMAIL PROTECTED] If all is well, this will display the variables your UPS supports. Please post the output here. 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] Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon ?
Hi Theo, You can try to run the driver only with the ups.conf. Locate the bcmxcp_usb driver. then run this command. /path/to/bcmxcp_usb -DD -a powerware (exchange the /path/to with the right path) Now it should spit out som debug info if the communication is ok. You should also upgrade to the 2.0.5 version as (think it was) Arjen found one bad typo in the shutdown functions. Also you should set the shutdown_delay to 60 in the ups.conf as it warns that it could not run more than 60 sec after it signaling low battery. This time is used to power off the ups after a low battery warning. So it should give a shutdown -h now on battery low, then run for 60 sec and power off. Normal a machine should manage to go down to halt in this time. But with 2.0.4 it would not power off (se above). Regards Kjell lör 2007-03-24 klockan 10:35 +0100 skrev Theo G. Kanter: 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 [EMAIL PROTECTED] is unavailable). I wonder whether this communication error message may be related to the howto assuming that a user 'upsl' exists, while 'nut' only configures a user 'nut'. I am new to 'nut' so any hints are welcome. I have no clue why upsdrvctl fails when I start nut when it first starts properly by itself. Below I included the configuration files (found in /etc/nut/*) Please advise me on how to deal with both these issues. # upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Model = POWERWARE UPS1000VA Firmware = 00.50 Shutdown delay = 120 seconds Shutdown delay longer than battery capacity when Low Battery warning is given. (max 60 seconds) # /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon. Broadcast Message from [EMAIL PROTECTED] (somewhere) at 9:48 ... Communications with UPS [EMAIL PROTECTED] lost --- /etc/nut/ups.conf --- [powerware] driver = bcmxcp_usb port = auto desc = PowerWare 5110, USB --- /etc/nut/upsd.conf --- ACL all 0.0.0.0/0 ACL remote 192.168.0.0/24 ACL localhost 127.0.0.1 ACCEPT localhost ACCEPT remote REJECT all --- /etc/nut/upsd.users [monuser] password = PASSWORD allowfrom = localhost actions = SET instcmds = ALL upsmon master --- /etc/nut/upsmon.conf MONITOR [EMAIL PROTECTED] 1 monuser PASSWORD master SHUTDOWNCMD /sbin/shutdown -h +0 Thanks in advance. --theo ([EMAIL PROTECTED]) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
