search for: sdrups

I have made changes but it is still the same. That is when the server gets the lowbat/noAC signal it does shut down as expected but the slave does not. Perhaps it makes sense for me to list the present settings: On the Master: nut.conf MODE=netserver ups.conf [sdrups] driver = genericups port = /dev/ttyS1 desc = "For Server & Backup" upstype=9 upsd.conf LISTEN 0.0.0.0 upsd.users [root] password = mypassword upsmon master instcmds = ALL upsmon.conf MONI...

...ezy hasn't changed much. There are a few things still being sorted out in Debian jessie.) > Now this may be a problem but I don't think it is the only one. I really feel this is a permissions issue. > > For example from the master, if I type: > root at backup2:~# sudo upsc sdrups at localhost ups.status > OL > > Which is the response I expect, but if I type (also from the master): > root at backup2:~# sudo upsc sdrups at 192.168.0.7 ups.status > Error: Connection failure: Connection refused One thing that has changed since NUT 2.4.x is that the ACL...

...netstat" output is independent of the firewall. > Now I am stumped as to why the slave does not shut down? > You should see something like this in /var/log/daemon.log on the slave (and on the master, but you said that was shutting down already): upsmon[1234]: Communications with UPS sdrups at 192.168.0.7 established Once that connection is up, you can run "sudo upsmon -c fsd" on the master to simulate a power failure (to avoid running down the batteries too much). Note that this will shut down the master system, too. Details are in the upsmon man page. -- Charles Lepple...

...ame. That is when the server gets the lowbat/noAC signal it does shut down as expected but the slave does not. > > Perhaps it makes sense for me to list the present settings: > > On the Master: > > nut.conf > MODE=netserver > > ups.conf > [sdrups] > driver = genericups > port = /dev/ttyS1 > desc = "For Server & Backup" > upstype=9 > > upsd.conf > LISTEN 0.0.0.0 > > upsd.users > [root] > password = mypassword &gt...

Hello, I have a UPS connected to my server with the following: Server is Suse 10.1 Nut version is?Network UPS Tools - Generic UPS driver 1.32 (2.0.4) I installed this around 2005 and cannot remember how I installed the software. ups.conf: [sdrups] driver = genericups port = /dev/ttyS0 desc = "For Server & Backup" upstype = 9 upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/255.255.255.0 ACL server 192.168.0.4/255.255.255.0 ACCEPT localhost ACCEPT server REJECT all upsd.users: [root] password = autocad allowfrom = localh...

On 11/10/14 17:52, Steve Read wrote: > Hi Stan, thank you for your help. > > My ups.conf file is: > [sdrups] > driver = genericups > port = /dev/ttyS1 > desc = "For Server & Backup" > upstype=9 > Assuming upsmon is the user and autocadba2 is the password in upsd.users, the monitor line should be MONITOR sdrups at 192.168.0.7 upsmon autocadba2 slave...

On the slave which is 192.168.0.6 in /var/log/daemon.log I see entries of: Nov 10 17:43:03 server2 upsmon[2120]: Poll UPS [root at 192.168.0.7] failed - [root] does not exist on server 192.168.0.7 In upsmon.conf I have one entry: MONITOR root at 192.168.0.7 1 sdrups autocadba2 slave (Yes, I realize I displayed my password some time ago) So I think it is saying that root does not exist on server which is confusing as on the server 192.168.0.7 I have. In upsd.users I have [root] password = autocadba2 upsmon master instcmds = ALL So why is it saying root doe...

...e for years (although I remember many head banging times getting that to run at the time). My new server IP's are: 192.168.0.7 is the master 192.168.0.6 is the client Thank you for any help - Steve On the Master Server I have: nut.conf MODE=netserver ups.conf [sdrups] driver = genericups port = /dev/ttyS1 desc = "For Server & Backup" upstype=9 upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/255.255.255.0 ACL server 192.168.0.6/255.255.255.0 ACCEPT localhost ACCEPT server...

On Nov 6, 2014, at 12:48 PM, Steve Read <sd_read at hotmail.com> wrote: > I am presently upgrading my servers. The old ones are running Suse 10.1 and I am upgrading to the most recent Debian. What version of NUT on the new systems? There are a few changes to the configuration files, mostly related to the ACL lines. -- Charles Lepple clepple at gmail -------------- next part

...ber as well, but wheezy hasn't changed much. There are a few things still being sorted out in Debian jessie.) Now this may be a problem but I don't think it is the only one. I really feel this is a permissions issue. For example from the master, if I type: root at backup2:~# sudo upsc sdrups at localhost ups.status OL Which is the response I expect, but if I type (also from the master): root at backup2:~# sudo upsc sdrups at 192.168.0.7 ups.status Error: Connection failure: Connection refused One thing that has changed since NUT 2.4.x is that the ACL options were removed, and...

Boy, I guess I got that one wrong. When I run nmap on the master it does say that port 3493 is open which is expected. So then what you are telling me means the ports are open. In other words I don't have a firewall issue. Now I am stumped as to why the slave does not shut down? Subject: Re: [Nut-upsuser] Master Works, Slave Does Not From: clepple at gmail.com Date: Sun, 9 Nov 2014 16:31:22

On Nov 9, 2014, at 3:48 PM, Steve Read <sd_read at hotmail.com> wrote: > I would like to verify my understanding keeping in mind I have a one master and one slave computer. > > When the master gets the low batt/noAC signal it initiates a broadcast packet(s) on port 3493. > > 1) Is this correct? No, the slave computer's upsmon process connects to the master (via TCP, so