Hi Charles, Charles Lepple wrote: > On Wed, Jul 30, 2008 at 3:21 AM, Riccardo Magliocchetti > <[EMAIL PROTECTED]> wrote: >> Hi, >> >> this is my first nut installation, i see lot of connection failure and when >> i tried >> the configuration removing the power chord from the ups i expected tha >> machine will >> power itslef down but this has not happened. >> >> I'm using nut 2.2.2-2 from debian lenny, ups is a mustek powermust 2000 with >> usb cable. > > Which machine is the UPS connected to?
mybox is the same machine as localhost >> All config files are root:nut and 640, i've had to add nut user to nut group >> manually. > > You might want to file a bug with Debian about adding the nut user to > the nut group. That should happen automatically. will do >> ups.conf: >> [bongups] >> driver = megatec_usb >> port = auto >> desc "UPS Mustek PowerMust 2000" >> >> upsd.conf: >> ACL all 0.0.0.0/0 >> ACL localhost 127.0.0.1/32 >> ACL mybox 192.168.10.75/32 >> >> ACCEPT localhost >> ACCEPT mybox >> REJECT all >> >> upsd.users: >> [admin] >> password = pass >> allowfrom = localhost >> upsmon master >> >> [monuser] >> password = pass >> allowfrom = mybox >> upsmon master >> >> upsmon.conf: >> POWERDOWNFLAG /etc/nut/killpower >> MONITOR [EMAIL PROTECTED] 1 monuser pass master >> SHUTDOWNCMD "/sbin/shutdown -h +0" >> >> syslog (daemon.log): >> >> Jul 30 09:13:18 bong upsd[2819]: listening on 0.0.0.0 port 3493 >> Jul 30 09:13:18 bong upsd[2819]: Can't connect to UPS [bongups] >> (megatec_usb-bongups): No such file or directory >> Jul 30 09:13:18 bong upsd[2820]: Startup successful >> Jul 30 09:13:28 bong upsmon[2823]: Startup successful >> Jul 30 09:13:32 bong megatec_usb[2829]: Startup successful >> Jul 30 09:13:32 bong upsd[2820]: Connected to UPS [bongups]: >> megatec_usb-bongups >> Jul 30 09:13:34 bong upsd[2820]: Data for UPS [bongups] is stale - check >> driver >> Jul 30 09:13:43 bong upsd[2820]: UPS [bongups] data is no longer stale > > At this point in the log, it looks like megatec_usb has finally > connected. Can you retrieve status data with 'upsc [EMAIL PROTECTED]' > on that machine? yeah, i missed to say that uspc works fine >> Jul 30 09:16:37 bong upsmon[2824]: UPS [EMAIL PROTECTED]: connect failed: >> Connection failure: Connection timed out >> Jul 30 09:16:37 bong upsmon[2824]: Communications with UPS [EMAIL PROTECTED] >> lost >> Jul 30 09:19:51 bong upsmon[2824]: UPS [EMAIL PROTECTED]: connect failed: >> Connection failure: Connection timed out >> Jul 30 09:19:51 bong upsmon[2824]: UPS [EMAIL PROTECTED] is unavailable > > Here it looks like you are trying to connect to another machine. > > If you have a single machine that you are trying to monitor, you can > use e.g. [EMAIL PROTECTED] in the upsmon.conf file. It's on the same machine, will retry using localhost instead > If you are monitoring an UPS on a remote machine, be sure that you > have network connectivity between the two, and that the NUT port is > not firewalled. You can check this with e.g. 'upsc > [EMAIL PROTECTED]' from the machine where the UPS is not > connected. thanks, Riccardo _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
