similar to: Master Works, Slave Does Not

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 &

[Please use reply-all to keep the discussion on the list, thanks] On Nov 6, 2014, at 10:19 PM, Charles Lepple <clepple at gmail.com> wrote: > 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

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

On Nov 9, 2014, at 7:56 PM, Steve Read <sd_read at hotmail.com> wrote: > 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. I know this sounds incredibly pedantic, but if you run nmap

On Nov 8, 2014, at 1:52 PM, Steve Read <sd_read at hotmail.com> wrote: > 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 > >

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

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

Thank you Charles, I am hoping fiddle with that sometime today or tomorrow. But I have another question, when you ask me to modify various files I am confused as to weather you mean on the server, client or both? So in your statement: "Instead, you want to listen on the wildcard address, so you will want to add "LISTEN 0.0.0.0" to /etc/nut/upsd.conf. After restarting NUT, netstat

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

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

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

On Nov 8, 2014, at 10:34 AM, Steve Read <sd_read at hotmail.com> wrote: > Thank you Charles, I am hoping fiddle with that sometime today or tomorrow. > > But I have another question, when you ask me to modify various files I am confused as to weather you mean on the server, client or both? > > So in your statement: > > "Instead, you want to listen on the

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? Then the slave computer must have this port open and it listens on this port for the shut-down command. 2) Is this correct? On the slave if I run the following: steve at MyDesktop:~$

I am using Rsync to mirror my primary drive to a mounted second drive. I am using a crontab to control it: 30 3 * * * /usr/bin/rsync -rpogl /* /mnt/backup2/systemBackup/ The first run seems fine. But the subsequent running seems to double the original directory size. I notice this by running df -k. The destination size increases two fold, as if each time Rsync runs, it repeats itself, rather

Hi All, I have been using rsync to backup to a central server with a 7 day incremental script on 2 Redhat boxen. #!/bin/sh PATH=/usr/local/bin:/usr/bin:/bin DAY=`date +%A` export PATH DAY [ -d /root/emptydir ] || mkdir /root/emptydir rsync --rsh=/usr/bin/ssh --delete -a /root/emptydir/ CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/$DAY rmdir /root/emptydir rsync --delete

Dir list! I'm using nut for many years on my home "server" without problems running on Debian 6.x nut version 2.4.3 Now I have decided to move to Debian 10. I have started from zero and install new system on a different disk. I have successfully installed new nut version 2.7.4 I've found one issue, that new version see always "low battery" state. Excerpt from syslog:

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

On Tue, 2018-09-11 at 12:56 -0400, Kevin Korb via rsync wrote: > --timeout is about network connection timeouts. You aren't using the > network so it doesn't apply at all. Even if you were networking an > unmounted filesystem is an empty directory as far as rsync is > concerned > and rsync would treat it that way with no idea that you intended to > have > something

Testing out tipc for cluster development, and running into an immediate snag. tipcutils was found in EPEL but despite having a "compatible" kernel, it doesn't seem to actually work. It's a completely updated system, Intel i5 with 16 GB of RAM, nothing remarkable. Any ideas? [root at backup2 ~]# tipc-config -netid=1234 -a=1.1.1 -be=eth:eth0 TIPC module not installed

Hi, Is there any way to debug a failure of NUT to shut a machine down AFTER the even occurs? (Be it a config issue {Though the standard "It hasn't changed since install" applies}, or a UPS failure, or a program failure). Its showing up (after reboot) as : valhalla# upsc robanton at localhost driver.name: genericups driver.parameter.pollinterval: 2 driver.parameter.port: