Displaying 20 results from an estimated 6000 matches similar to: "Master Works, Slave Does Not"
2014 Nov 08
0
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 &
2014 Nov 08
4
Master Works, Slave Does Not
[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
2014 Nov 07
0
Master Works, Slave Does Not
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
2014 Nov 10
3
Master Works, Slave Does Not
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
2014 Nov 08
2
Master Works, Slave Does Not
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
>
>
2014 Nov 10
0
Master Works, Slave Does Not
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
2014 Nov 11
0
Master Works, Slave Does Not
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
2014 Nov 08
0
Master Works, Slave Does Not
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
2014 Nov 09
2
Master Works, Slave Does Not
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
2014 Nov 10
0
Master Works, Slave Does Not
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
2012 Feb 26
1
Server Does Not Shut Down
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
2014 Nov 08
1
Master Works, Slave Does Not
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
2014 Nov 09
0
Master Works, Slave Does Not
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:~$
2017 Jun 06
2
Apple Mac slave
Hello,
I am running NUT on a Synology NAS with attached a USB APC UPS.
I am trying to connect and shutdown a Mac OS X system.
I have installed the NUT software and it looks like there is connection with the master but when battery gets low the Mac is not shutdown.
I don't know if I have to configure upssched.conf and where? On the slave (Mac) ?
It will be great to know before I will start
2017 Jun 15
2
Apple Mac slave
I deleted the plist file and rebooted:
sudo /sw/sbin/upsmon -D
Network UPS Tools upsmon 2.7.4
0.000000 fopen /sw/var/run/upsmon.pid: No such file or directory
0.044649 UPS: ups at ip address (slave) (power value 1)
0.081597 Using power down flag file /etc/killpower
0.162720 debug level is '1'
0.538410 Trying to connect to UPS [ups at ip address]
0.540345 Logged into UPS
2017 Jun 12
4
Apple Mac slave
On Jun 11, 2017, at 7:15 AM, Robbie van der Walle <rvanderwalle at gmail.com> wrote:
>
> I see only a reboot. Not a shutdown. But is this normal because shutdown -u -h +0 is used?
>
To be honest, I haven't experimented much with this, but I saw a normal shutdown/reboot when I just tried this from the command line (10.12):
reboot ~ Mon Jun 12 08:36
2001 Sep 23
2
destination dir doubles in size
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
2013 Jun 26
1
dumb slave
Hi list,
I?ve been struggling with nut some time to get it to do as I wish
without any succes.
Nut configured as a "client": Can upsmon catch events and do actions in
upssched-cmd?
Like " onbatt)
shutdown blabla"
After a reload configs of upsmon syslog gives me:
Jun 26 16:06:44 pascal-desktop upsmon[1037]: Reloading configuration
Jun 26 16:06:44
2017 Jun 15
2
Apple Mac slave
> sudo launchctl list|fgrep -v com.app
returns for me(10.12.5):
PID Status Label
- 78 org.networkupstools.upsmon
system log:
Jun 15 16:27:07 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jun 15 16:27:17 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon[4259]): Service could not initialize: 16F73:
2017 Jun 15
1
Apple Mac slave
Ok rebooted
All running ok now. Great thanks a lot!
In system.log
Jun 15 21:38:54 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): Unknown key for Boolean: SuccessfulExit
Jun 15 21:38:54 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): This service is defined to be constantly running and is inherently inefficient.
What is the purpose of Boolean: SuccessfulExit?