[Nut-upsuser] "Master privileges unavailable on UPS" after upgrade to Debian Lenny
Hi all, I've just upgraded my debian box from etch to lenny, and am now having Nut problems. I have read through the UPGRADING text (which helped fixed my first ups driver related problem), but have now hit another problem, which seems quite common, but non of the responses I've found on Google apply, so I'm coming to you for help. On issuing a "/etc/init.d/nut start" I get the following in my syslog: Mar 7 00:27:19 copstick3 upsd[26316]: Connection from 127.0.1.1 Mar 7 00:27:19 copstick3 upsd[26316]: Client monu...@127.0.1.1 logged into UPS [copstick_ups] Mar 7 00:27:19 copstick3 upsmon[26319]: Master privileges unavailable on UPS [copstick_...@copstick3] Mar 7 00:27:19 copstick3 upsmon[26319]: Response: [ERR ACCESS-DENIED] Also, the following: # upsc -L copstick3 copstick_ups: Unavailable Google suggests that the common cause for this is not having a 'upsmon master' in my upsd.users file, but I've checked that. I'm now just going round in circles, and so would really appreciate any suggestions. My config files (passwords altered) as as follows (the ups is on a machine called 'copstick3.nobody with an ip of 10.9.2.9): hosts.conf ## MONITOR copstick_...@copstick3 "Copstick APC" ups.conf [copstick_ups] driver = usbhid-ups port = /dev/usb/hiddev0 upsd.conf # ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL localhost2 127.0.1.1/32 ACL nobodynet 10.9.2.0/24 #ACCEPT all ACCEPT localhost ACCEPT nobodynet ACCEPT localhost2 REJECT all upsd.users ## [admin] password = blarblarblarblar allowfrom = localhost actions = SET instcmds = ALL [monuser] password = blarblar allowfrom = localhost actions = SET instcmds = ALL upsmon master upsmon.conf ### RUN_AS_USER nut MONITOR copstick_...@copstick3 1 monuser blarblar master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/local/scripts/upsshout POLLFREQ 60 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 180 POWERDOWNFLAG /etc/killpower NOTIFYMSG ONLINE "%s is back on mains power" NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYMSG ONBATT "%s is on battery power" NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYMSG LOWBATT "%s battery is critical" NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYMSG COMMOK "I have re-established comms with %s" NOTIFYFLAG COMMOK SYSLOG+WALL NOTIFYMSG COMMBAD "I have lost comms with %s" NOTIFYFLAG COMMBAD SYSLOG+WALL NOTIFYMSG SHUTDOWN "System being shutdown by the UPS monitor" NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC NOTIFYMSG REPLBATT "%s UPS battery is bad and needs replacing" NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 2 Any suggestions would be gratefully received. Cheers, --Dave -- David Smith nobody...@fastmail.fm ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Question about Tripplite SU10KRT3U
Citeren Dave Gibson : > Hello list! I can't seem to get this running via RS232 monitoring; I've > been told that NUT won't support serial connections, and find this hard > to verify. Does anyone else have this running on the SU10KRT3U via > RS232? If so, what driver did you use? I'm getting no satisfaction from > the "tripplite" driver; upon upsdrvctl start, I get "Failed to find UPS > - giving up..." You may have better luck with the 'tripplitesu' driver for Tripp Lite SmartOnline (SU*) models. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Question about Tripplite SU10KRT3U
NUT definitely supports serial connections - I have an APC connected that way. Des On 6 Mar 2009, at 11:49, Dave Gibson wrote: > Hello list! I can’t seem to get this running via RS232 monitoring; > I’ve been told that NUT won’t support serial connections, and find > this hard to verify. Does anyone else have this running on the > SU10KRT3U via RS232? If so, what driver did you use? I’m getting no > satisfaction from the “tripplite” driver; upon upsdrvctl start, I > get “Failed to find UPS – giving up…” > > TIA, > Dave > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser -- Des Dougan, Principal Dougan Consulting Group Inc. Office: 604-628-5434 Cell: 604-866-2848 Email: des at DouganConsulting dot com www.DouganConsulting.com Peace of Mind, One Computer at a Time. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Question about Tripplite SU10KRT3U
Hello list! I can't seem to get this running via RS232 monitoring; I've been told that NUT won't support serial connections, and find this hard to verify. Does anyone else have this running on the SU10KRT3U via RS232? If so, what driver did you use? I'm getting no satisfaction from the "tripplite" driver; upon upsdrvctl start, I get "Failed to find UPS - giving up..." TIA, Dave ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut with megatec_usb
Citeren Gabriel Hahmann : > I tried your sugestion, changing the protocol to megatec and putting the > port with /dev/ttyUSB0. > > This didn't work, the output is as follows: > > r...@comserver:/lib/nut# ./megatec -a sms -DD > Network UPS Tools 2.2.1- - Megatec protocol driver 1.5.13 [megatec] > Carlos Rodrigues (c) 2003-2007 > > debug level is '6' > Starting UPS detection process... > Asking for UPS status [Q1]... > Q1 => FAILED [timeout] > Asking for UPS status [Q1]... > Q1 => FAILED [timeout] > Asking for UPS status [Q1]... > Q1 => FAILED [timeout] > Asking for UPS status [Q1]... > Q1 => FAILED [timeout] > Asking for UPS status [Q1]... > Q1 => FAILED [timeout] > 5 out of 5 detection attempts failed (minimum failures: 2). > Megatec protocol UPS not detected. Assuming that the usbserial port is working correctly (there have been issues with m8_cypress in some kernels in the past), it doesn't look like this device is speaking Megatec/Q1 protocol. If you upgrade NUT, you might also try out the blazer_ser driver, which also speaks some variations. But it might very well be something completely different. > I think that maybe, this version doesn't use the megatec protocol, maybe > some variation. Could you or somebody help me to find wich protocol this > nobreak uses? I have another server running the windows version of the > manuftaturer software, maybe I could sniff or find something. The old > version of this manufturer with serial interface uses megatec. Sniffing the output on a Windows box while monitoring the UPS might indeed help us finding out which protocol it uses. If you need instructions on how to do that (for either USB or RS-232 connections), search the archives. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
