Dear List, Sorry if this is a FAQ - I've been looking at
http://lists.alioth.debian.org/pipermail/nut-upsuser/ but I havn't yet
found the answer.
I have an MGE Ellipse 1500. I run openSUSE 10.2, kernel 2.6.18, nut
2.0.5. ps shows that the following processes are running:
On Fri, 8 Jun 2007, Charles Lepple wrote:
CMDSCRIPT /usr/sbin/upssched-cmd
PIPEFN /var/state/ups/upssched.pipe
LOCKFN /var/state/ups/upssched.lock
Is /var/state/ups owned and writeable by the NUT user?
Have the pipe and lock files been created?
That was the problem. openSUSE uses
Dear List, I have an MGE Ellipse 1500. I run openSUSE 10.2, kernel
2.6.18, libusb 0.1.12, nut 2.0.5. ps shows that the following processes
are running:
/usr/lib/ups/driver/newhidups -a mgeups
/usr/sbin/upsd -u root
/usr/sbin/upsmon
/usr/sbin/upsmon
NUT operates correctly, shutting down the
Dear List, I thought it might be useful if I wrote up my notes on getting
an MGE UPS to work with NUT and openSUSE.
The MGE UPS (an Ellipse 1500 USB) will work well with NUT and openSUSE
10.2, but not out-of-the-box: there are some things you need to do:
Intro. MGE have built rpms of NUT which
Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500.
I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2,
nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!)
lsusb shows:
Bus 001 Device 004: ID 0463: MGE UPS Systems UPS
/etc/ups/ups.conf says:
[myups]
On Wed, 17 Oct 2007, Arjen de Korte wrote:
This is a known problem with the new kernel in openSUSE 10.3:
https://bugzilla.novell.com/show_bug.cgi?id=331749
Unfortunately, this is apparently not very high on the list of priorities.
So for now, I suggest to apply the changes by hand. :-(
I
Dear list, I would like to test version 2.2.2-pre2 on openSUSE 10.3. On
this machine uname -a reports
Linux glacon2 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC x86_64
x86_64 x86_64 GNU/Linux
I removed the current rpm's (2.2.0) with rpm -e and tried to
On Sat, 19 Apr 2008, Charles Lepple wrote:
On Sat, Apr 19, 2008 at 6:52 AM, Roger Price [EMAIL PROTECTED] wrote:
On Sat, 19 Apr 2008, Arjen de Korte wrote:
+ autoreconf -f -i
configure.in:69: error: possibly undefined macro: AC_PROG_LIBTOOL
Roger,
Do you have libtool installed
On Sat, 19 Apr 2008, Charles Lepple wrote:
On Sat, Apr 19, 2008 at 9:16 AM, Roger Price [EMAIL PROTECTED] wrote:
On Sat, 19 Apr 2008, Charles Lepple wrote:
Do you have libtool installed?
No, it wasn't asked for.
Hence, my question to Arjen about whether autoreconf needs
I started testing the 64 bit rpms of 2.2.2-pre2 on openSUSE 10.3 with an
MGE Ellipse 1500 USB. Here is my writeup of the test, with my apologies
for a long post. It looks as if I have a problem with upssched.
My 64 bit rpm's are available at
On Sun, 20 Apr 2008, Arjen de Korte wrote:
Roger Price wrote:
# /etc/ups/upsmon.conf
MONITOR [EMAIL PROTECTED] 1 monuser mgepass master
MINSUPPLIES 1
SHUTDOWNCMD /sbin/shutdown -h +2 Arret systeme!
NOTIFYCMD /usr/sbin/upssched
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME
On Sun, 20 Apr 2008, Arjen de Korte wrote:
Hello Arjen, I live in the Alpes Maritimes in the south of France. This
is an area with frequent electrical storms, plenty of lightning and it is
common to have several short power cuts in succession during a storm. My
strategy is to tolerate
On Sun, 20 Apr 2008, Roger Price wrote:
# /etc/ups/upssched.conf
CMDSCRIPT /usr/sbin/upssched-cmd
PIPEFN /var/run/ups/upssched.pipe
LOCKFN /var/run/ups/upssched.lock ...
No surprise here, it's just more n00b fumbling. The correct answer, which
is provided by the rpm but which I wrongly
On Mon, 21 Apr 2008, Arnaud Quette wrote:
Also note that the PSP 3.0.4 is the one provided by MGE *UPS Systems*.
I don't think this one is maintained anymore, so you really want to
switch to the MGE *Office Protection Systems which is the 3.0.6 one,
available here:
On Mon, 21 Apr 2008, Roger Price wrote:
On Mon, 21 Apr 2008, Arnaud Quette wrote:
A source RPM for SuSE is also available, but I'm not sure it's x64 ready!
http://opensource.mgeops.com/stable/sources/suse/
I had confused mgeups and mgeops. I downloaded the source rpm and ran
On Tue, 22 Apr 2008, Arnaud Quette wrote:
right. the API used is an old one, to have a wide platform support spectrum.
You'll find a 3.0.7 archive here:
http://opensource.mgeops.com/stable/sources/projects/psp/
- Retrieve the .bz2
- extract it, and get into the dir
- call configure a
I am trying to build an rpm for nut-2.2.2 on 64 bit opensuse 11.0.
0. Packages previously built for opensuse 10.x have to be rebuilt since
opensuse 11.0 now compresses package payloads using lzma, which
according to the opensuse 11.0 release notes makes 10.x rpms unusable.
1. I
Hi, its only a minor wrinkle, but repeated %s in NOTIFYMSG seem to
be ignored. In /etc/ups/upsmon.conf I specified:
NOTIFYMSG NOCOMM UPS %s is unavailable +++ Onduleur %s indisponible
but the message I received said:
Broadcast Message from u...@sandrane
(somewhere) at 18:33 ...
UPS
On Mon, 4 Jan 2010, Dimitris Mandalidis wrote:
I have an MGE Ellipse 500 UPS for about 8 years,...
Suddenly, there was a power failure last week, the UPS was serving
the two PCs ... for 30 secs and then it went off,
Does anybody have an idea what's going wrong?
Hi, When did you last
Hi, The Eaton/MGE Pulsar Ellipse ASR 1500 USBS runs well with NUT
2.4.1 on openSUSE 11.2, and I expect that many other Eaton/MGE UPS's
will also run equally well, but this is not a simple click and go
experience. Since it takes a while to set up and test a process for
automatic system
Hello Arjen, thanks for the comments. I have taken the liberty of
adding them to my page.
Roger
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
I'm using NUT 2.4.1 with openSUSE 11.2, my UPS is an MGE/Eaton
Ellipse ASR 1500 USBS. The set-up is as described at
http://rogerprice.org/NUT.html.
Since NUT uses TCP wrappers, I have the /etc/hosts.allow entry
upsd :10.0.0/24, localhost, LOCAL, 127.0.0.1 : ALLOW
When I pull the
On Thu, 30 Sep 2010, Charles Lepple wrote:
rpr...@glacon2:~ upsc -l
Eaton-66781
rpr...@glacon2:~ upsc -L `upsc -l`
Error: No such host
The -l and -L options can be considered the short and long versions
of the list UPSes option (where the long version also shows the description
from
Charles Lepple wrote:
... It looks like the same ERR ACCESS-DENIED code is returned
for a problem with upsd.users/upsmon.conf versus a TCP wrappers
match failure.
What if you run 'tcpdchk' against your hosts.allow file? I am not
terribly familiar with TCP wrappers, and your configuration
Dear List, I'm running NUT 2.4.1 on openSUSE 11.3 64 bits, kernel
2.6.34. The UPS is an Eaton Ellipse ASR 1500 USBS. With driver
usbhid-ups NUT works perfectly _until_ I turn off IPv6.
By default IPv6 is turned on in openSUSE 11.3. I visited YaST -
Network Settings - Global options and
On Sun, 7 Nov 2010, Arjen de Korte wrote:
The fix for this problem is to turn IPv6 on again, but I wondered
if there was a way of specifying to NUT no IPv6.
Yes Alternatively, you can enter the sockets it should listen
to with the LISTEN directive in 'upsd.conf'. This will then
On Thu, 11 Nov 2010, Rémi Lavergne wrote:
I have recently installed nut to manage a DELL USB UPS
Which model? What does lsusb report?
on a DELL server running UBUNTU Server. I have installed nut via
apt-get and then configured following several tutorials found on
the web.
Which one did
On Tue, 16 Nov 2010, Rémi Lavergne wrote:
/etc/nut/upssched.conf :
CMDSCRIPT /etc/nut/sched/upssched.sh (this script exists but seems never to
be executed...)
Hello Rémi, what are the ownership and permissions on file
/etc/nut/sched/upssched.sh ? Try adding the lines
# Debugging: Log all
On Tue, 15 May 2012, Stefan Kuhn wrote:
May 13 21:50:34 s-monitor1 upssched[855]: exec_cmd(/etc/nut/upssched-cmd
ONBATT) returned 126
Hi, What are the permissions on /etc/nut/upssched-cmd ?
Roger
___
Nut-upsuser mailing list
On Tue, 15 May 2012, Stefan Kuhn wrote:
-rw-r--r-- 1 root root 4555 2012-05-13 22:31 upssched-cmd
Hi Stefan, Shouldn't upssched-cmd be executable ? I would expect to
see -rwxr--r--.
Roger
___
Nut-upsuser mailing list
On Wed, 23 May 2012, Stefan Kuhn wrote:
I don't know where to look for the problem.
If you add the lines
# Debugging: Log all calls to this script
logger -t upssched-cmd Calling upssched-cmd $1
at the top of the script upssched-cmd, does any message get logged?
If YES: look in the script.
On Wed, 23 May 2012, Stefan Kuhn wrote:
May 23 10:58:07 s-monitor1 upssched-cmd: Calling upssched-cmd ONBATT
This is good news, since it says that the script gets called with
the parameter ONBATT. Now you need to find out what the script does
with this parameter. Two suggestions:
1. At
On Mon, 25 Jun 2012, Anna Skorokhodova (Yandex) wrote:
Can't make upssched notify me on event occured.
Hello Anna, Does the script /usr/local/bin/upssched-cmd get called?
What happens if you place a command such as
# Debugging: Log all calls to this script
logger -t upssched-cmd Calling
On Sun, 15 Jul 2012, Gene Ulmer wrote:
I installed NUT version 2.6.3-1ubuntu1.1 w/the client and server and the nut
monitor. When I open the monitor, I get an error: error connecting to 'local
host' ([Errno] connection refused). What can I do to get NUT to work? I can
not tell if the NUT
Dear List, I'm trying to perform an automatic server shutdown and restart
with NUT 2.6.3, openSUSE 12.2 and an Eaton Eco 1600. The server shutdown
works but there is no automatic restart when wall power returns. Unlike
successful tests with earlier versions of openSUSE, the UPS unit is never
On Fri, 26 Oct 2012, Kris Jordan wrote:
Did you install NUT from a package? Note, 2.6.5 is the current
version and 2.6.4 had fixed a vulnerability.
I'm using the nut 2.6.3 package included in the openSUSE 12.2
distribution.
Check that your distribution's shutdown script is running
On Fri, 4 Jan 2013, Thomas Laus wrote:
My CMDSCRIPT /usr/local/bin/upssched-cmd:
#!/bin/sh
case $1 in
upsbatt)
echo The UPS has been on battery for awhile \
| mail -sUPS monitor me@testhost.local
;;
...
..., but no email was generated nor
My upssched.conf:
PIPEFN /var/db/nut/upssched/upssched.pipe
LOCKFN /var/db/nut/upssched/upssched.lock
I'm sure you've checked permissions already, but what does ls -alF
/var/db/nut/upssched report?
Roger
___
Nut-upsuser mailing list
OpenSUSE 12.3 has fully embraced systemd, but to get NUT working correctly
now requires some further systemd engineering in addition to the usual NUT
configuration files. A new systemd service unit is needed to power off
the UPS.
The service unit consists of a new file
On Wed, 14 Aug 2013, Michal Hlavinka wrote:
The service unit consists of a new file
/etc/systemd/system/ups-delayed-shutdown.service
What exactly is this supposed to do?
The proposed service unit fixes an openSUSE 12.3 problem, in which the UPS
is not powered off on system shutdown.
When
On Mon, 8 Sep 2014, Charles Lepple wrote:
On Sep 8, 2014, at 2:26 AM, flavio.boschig...@infineon.com wrote:
I would like connect it by usb on my server raspberry pi.
Someone knows a simple tutorial to send me? I did some test without success.
We try to collect tutorial links here:
On Fri, 10 Oct 2014, flavio wrote:
I follow all the instructions without problem.
Now how can I test it?
Ups is connected to raspberry by ups.
I have an Ubuntu 14.04 client on my lan.
When you pull the UPS power cord from the wall to simulate a building
power failure, does the rasberry shut
On Tue, 14 Oct 2014, Sebastian Sztamblewski wrote:
upssched.conf
CMDSCRIPT /usr/local/ups/bin/upssched-cmd
AT ONLINE * EXECUTE online
AT ONBATT * EXECUTE shutdown
# i tested with pipe/locked but without effect
I've had a similar problem, In my case because PIPEFN and LOCKFN pointed
to
?
Roger Price
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
On Mon, 27 Apr 2015, James Hammond wrote:
Hi Roger, I get:
Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on battery
Apr 27 20:50:05 unifi upssched[2688]: Timer daemon started
Apr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)
Apr 27 20:50:26 unifi upssched[2688]: Event: onbatt
On Mon, 27 Apr 2015, James Hammond wrote:
... Not too sure where to start with assigning the correct permissions.
If it is of any help, you will see a full list of the permissions and
owners I use in Table 1 at http://rogerprice.org/NUT.html#SOFT
Cheers, Roger
On Mon, 27 Apr 2015, James Hammond wrote:
I am unable to get upssched working correctly as my UPS calls low
battery too late and there is no way to change it. I am running Nut
2.7.3 on Ubuntu 14.04 I have made this script, called
/sbin/upssched-cmd.sh
#!/bin/sh
case $1 in
onbatt)
On Mon, 27 Apr 2015, James Hammond wrote:
Roger, I did and it didnt work.
Aha!, what does your upssched.conf look like? If you add the lines:
# Debugging: Log all calls to this script
logger -t upssched-cmd.sh Calling upssched-cmd.sh $1
to your /sbin/upssched-cmd.sh , what is reported if
On Wed, 27 May 2015, Rob Groner wrote:
I have noticed, however, that the command to the UPS to do the delayed
shutdown comes RIGHT as openSUSE is shutting down. While that is a good
thing as far as timing and the potential race is concerned, I have seen
it once where the UPS received the
On Fri, 22 May 2015, Rob Groner wrote:
So I'm pursuing the strategy of issuing the upsdrvctl shutdown command
script when the OS (Porteus, in this case) is shutting down. I so far
can't get it to do it, but I'm sure I'll overcome it, but I realized
something else might be a problem.
Won't
On Mon, 26 Oct 2015, George Anchev wrote:
Hello,
I have been following the details in this article to configure my UPS:
http://rogerprice.org/NUT.html
However the system won't shutdown although file permissions look ok:
ls -alF /usr/sbin/ups*
-rwxr--r-- 1 upsd daemon 64984 Oct 15 2014
On Mon, 26 Oct 2015, George Anchev wrote:
> The best way to shut down becomes a power disconnection.
Hm. Not quite convenient for a dual boot system. Actually that
contradicts the very idea of being the power being non-interrupted.
Isn't there any way to reporgram the service to distinguish
On Wed, 28 Oct 2015, George Anchev wrote:
Beautiful! The shutdown succeeded.
Did you see a line in the journal similar to this ?
Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]:
nut-delayed-ups-shudown.service calling
upsdrvctl to shut down UPS unit
On Wed, 28 Oct 2015, George Anchev wrote:
P.S. There is a typo in your nut-delayed-ups-shutdown.service. Line:
ExecStart=/usr/bin/logger -t upsdrvctl "nut-delayed-ups-shudown.service calling
upsdrvctl to shut down UPS unit"
shudown is missing a 't'. It is in the log message but might still be
On Thu, 29 Oct 2015, George Anchev wrote:
Today I experienced something weird. As I was working, the system
started a shutdown and did shut down, then the UPS got powered off and
then back on - an expected behavior for a power fail situation. However
there was no power failure!
...
Oct 29
On Wed, 28 Oct 2015, George Anchev wrote:
${sbinPath}upsmon -c fsd
In 'upsmon --help' I read: "- fsd: shutdown all master UPSes (use with
caution)". What exactly does this line do?
My understanding is that it calls upsmon running as root to execute the
command specified by SHUTDOWNCMD in
On Tue, 27 Oct 2015, George Anchev wrote:
Oct 26 21:02:56 i7 upsd[2227]: Startup successful
...
Oct 26 21:02:56 i7 upsmon[2229]: Startup successful
...
Oct 26 21:04:51 i7 upsmon[2230]: UPS myups@localhost on battery
Oct 26 21:05:11 i7 upsmon[2230]: UPS myups@localhost on line power
Power
On Tue, 27 Oct 2015, George Anchev wrote:
Yes, that was the power off test. However the upssched-cmd script gave
absolutely no signs of activity. Even it's logger lines don't show up in
journalctl. No any permission error messages - nothing. Only the 2
messages from upsmon - on battery and
On Wed, 14 Oct 2015, Davide Baldini wrote:
Is there any command in the list provided by "upscmd -l myups" which is
accepted by this UPS?
None of the command sin the list successfully completes, not even
beeper.toggle.
It looks as if the problem is more general than turning off the UPS. The
On Wed, 14 Oct 2015, Davide Baldini wrote:
the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ;
in particular:
ups.delay.shutdown: 30
ups.delay.start: 180
However, the UPS does not shut down, not immediately nor well after the
timeout of the command:
On Wed, 14 Oct 2015, Davide Baldini wrote:
upsdrvctl shutdown
...
instcmd(shutdown.return, [NULL])
instcmd: FAILED
Shutdown failed!
Driver failed to start (exit status=1)
This time /var/log/syslog doesn't register anything about the UPS after
issuing the command above. Instead, It logged
I have been looking closely at using NUT with openSUSE 13.2. Here is
a quick summary.
1. Like the alien plant in the Quatermass Experiment, systemd is
reaching into every corner of the distribution. New systemd service
units exist in /usr/lib/systemd/system:
Power devices information server,
On Tue, 7 Jul 2015, Rob Groner wrote:
This is being run in Porteus 3.1 with nut 2.7.2.
My first thought was that this is more systemd wierdness, but I believe
that Porteus is based on Slackware which doesn't use systemd - is that
correct? Roger
On Thu, 3 Sep 2015, Rob Groner wrote:
I’ve followed your excellent guide for setting up NUT in openSUSE 13.1.
I’ve had great luck IN THE PAST, but for some reason now that I am
trying to set it up again from scratch, I’m getting a weird error.
Everything works except for the UPS shutdown.
Hello Bob,
I had preferred the shutdown script method because it was a little more
straight-forward, and possibly more portable. This guide is meant to
help people get the UPS up and running, whatever their Linux distro. I
don't know how common the systemd implementation is across various
On Fri, 4 Sep 2015, Rob Groner wrote:
Well, I tried the same script method with openSUSE 13.2, and it still did not
execute.
So I tried the system method, and it worked 1 time out of 3 attempts. I
captured the last failure:
2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't
On Tue, 8 Sep 2015, Rob Groner wrote:
I executed lsusb to verify the USB device is there, and it is. I tried
the shutdown command again with debug enabled, but it didn't seem to
reveal much more:
---
On Tue, 8 Sep 2015, Rob Groner wrote:
Roger,
rtd@linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD
Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD)
USB communication driver 0.32
0.00 debug level is '3'
0.000405 upsdrv_initups...
...
0.004555
On Wed, 2 Dec 2015, Olav Seyfarth wrote:
I'd ideally set it to "shut down when only 20% battery left" (which
should give at least five minutes power left, shutdown takes far less
than one minute). BUT:
# upsc eaton@localhost
battery.charge: 89
*battery.charge.low: 20*
...
... but mine does
On Wed, 2 Dec 2015, George Anchev wrote:
Did find a solution regarding the wall notifications?
Hello George, I'm still struggling to install openSUSE 42.1 with KDE.
When I have this (almost) working, I will have a look at the effect of
wall on KDE.
Roger
On Wed, 28 Oct 2015, George Anchev wrote:
> However there was no any notification on desktop at
I'm guessing you use KDE and this may be a problem in the default way
KDE treats the output of the "wall" program. I don't have a KDE setup
to test with,
Hi George, I finally have a 42.1 Leap
On Sat, 4 Jun 2016, Charles Lepple wrote:
On Jun 3, 2016, at 6:48 AM, Roger Price <ro...@rogerprice.org> wrote:
... the timer. I don't see it in /var/lib/ups where the locate tool
finds upsd.pid, and I don't see it in /run or /var/run where I see
upsmon.pid.
... it seems that the
Hi, I'm trying to get a better understanding of what a timer is, so I
added the following line to upssched.conf
# Debug - turn on long-running timer to find out where upssched puts it
AT ONBATT * START-TIMER where-am-I 1000
I can then start this timer by pulling the power cord from the wall
On Tue, 14 Jun 2016, Philippe Le Mesle wrote:
Voici ma configuration :
**
3/ le script /usr/bin/upssched-cmd
#!/bin/bash
case $1 in
upssms)
logger -t upssched-cmd "The UPS has been gone for 30 secs. Warn by sms..."
/bin/echo "Power
On Tue, 14 Jun 2016, Philippe Le Mesle wrote:
"essayer la commande /usr/bin/upssched-cmd upssms manuellement sans
passer par NUT." Là je ne comprends pas (je débute en Linux). Comment
puis-je exécuter cette commande ,
PS: préférez-vous que cet échange soit en anglais ?
It is better to
On Tue, 14 Jun 2016, Philippe Le Mesle wrote:
Roger? Can your read me?
I receive a single e-mail from you via the list. Remember that the
mailing list very probably removes duplicates. If you do not receive a
copy of your own messages to the list, check your options on the list
On Tue, 14 Jun 2016, Philippe Le Mesle wrote:
I finally received a delayed SMS saying power was back.
I'm guessing that your test action is to disconnect the building power
from the UPS for a certain time and then re-connect. How long do you
wait?
Even when all the gear is permanently
On Wed, 22 Jun 2016, André Hänsel wrote:
Now, what I see is that when the UPS feeding server-1 goes LB, server-1 is
indeed shut down, but it seems that the UPS is never switched off.
This is a problem because when power is restored after shutdown, but before
the battery runs out (with no load,
On Sun, 8 May 2016, Min Wang wrote:
Hi
centos 6.3 uses traditional SysV script ( not systemctl)
here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown
File /etc/init.d/ups is an administrative script which is used to set up
the nut daemon - I was looking for a run-time
On Fri, 13 May 2016, Kamran Khan wrote:
I have a TrippLite SMART2200RM2UN UPS. I have installed and configured
NUT as instructed on the website, and am able to monitor the status of
the UPS without much problem. The only problem I am seeing is that I
cannot get the machine to actually send
On Sat, 7 May 2016, Min Wang wrote:
I am using centos 6.3, and nut-2.6.5-2.el6.x86_64.
could you explain why not sending "a delayed command to the UPS to turn it off"
may cause that issue?
You need to stop the UPS from beeping. Only then can you get a clear
restart when power returns.
On Sat, 7 May 2016, Min Wang wrote:
Hi I have CP825AVR-G UPS. sometimes the UPS is shutdown due to
whatever reason.
But the annoying thing is even if the electrical power is back, that UPS
will continue to beep, and I have to manually turn on the switch button
in order for it to supply
On Thu, 14 Jul 2016, Dmitri Stepanov wrote:
Some of those hosts haven't NUT including upsmon (and other software
which is not included by suppliers of the hosts) for a number of
reasons. I don't need to inform not-NUT hosts about any UPS events,
etc... but only shutdown all the hosts after
On Wed, 13 Jul 2016, Dmitri Stepanov wrote:
Hi
I need to shutdown a number of hosts which has not NUT from one which has it.
I tried to do it from upssched script (after upssched's timer) like this:
case $1 in
earlyshutdown)
logger -t upssched-cmd "Early
Sorry if this is a duplicated message.
On Tue, 12 Jul 2016, Barbieri, Matteo wrote:
... a new model "Inform Sinus SS 230". Obviously I already saw on the
official NUT website that the model is not supported, but I was wondering if
there are some compatible drivers or maybe someone who are
On Wed, 13 Jul 2016, Dmitri Stepanov wrote:
shutdown-all-hosts.sh contains:
# Linux hosts
HOSTLIST="sim iogate br"
for host in $HOSTLIST
do
...
ssh $host halt -p
...
done
shutdown-all-hosts.sh works fine if it runned manually.
But it does not work even if I insert sleep 30 sec
On Sun, 5 Feb 2017, Tim Richards wrote:
Setup: Active/Passive Two Node Cluster. Two UPSes (APC Smart-UPS 1500 C)
with USB communication cables cross connected (ie UPS-webserver1
monitored by webserver2, and vice versa) to allow for stonith/fencing
OS OpenSuse Leap 42.2
NUT version
On Wed, 17 Aug 2016, Brian Hilmers wrote:
Hello, I am looking for good instructions on how to configure NUT to receive
SNMP Trap signals and how to shutdown a server. My setup is:
NUT: version 2.7.1-1ubuntu1, from package
OS: Ubuntu 14.04.5 LTS
UPS: Tripp Lite SMART3000RM2U
The only thing I
On Thu, 8 Sep 2016, Jeff Bowman wrote:
I’ve been able to get the latest Windows port installed on my Hyper-V 2012 R2
instance and start the service.
But as I’m an absolute beginner I’m not sure how to proceed further. I’ve
browsed the archives, but discussions here tend to assume at least an
On Sun, 11 Sep 2016, Jeff Bowman wrote:
But first I have to get it working :-)
Have you seen
https://grafenthal.de/wiki/index.php/Installation_Network_UPS_Tools_%28NUT%29_unter_Windows_Server_2012_USB
which shows a working NUT configuration under Windows Server 2012. It's in
german, but
On Thu, 8 Sep 2016, Jeff Bowman wrote:
That said, is there a way to manually poll the driver for UPS/power line
status? I ask because I can foresee a scenario such as this:
...
So I'd like to be able to remote in and check the status to make sure
everything is OK. If not, then I can manually
On Fri, 9 Sep 2016, Jeff Bowman wrote:
All of this leads me to the conclusion that NUT isn't working on my system.
Here is my configuration:
What command(s) do you use to start NUT? Do usbhid-ups, upsd and upsmon
start up?
Roger
___
Nut-upsuser
On Mon, 12 Sep 2016, Jonah Naylor wrote:
I have two linux servers both with static IPs not using NAT.
My slave can't connect to my host. Whatever I try.
I assume that these two machines are on the same LAN, so here are a few
suggestions. Can you ping from each one to the other? Can you ssh
On Wed, 5 Oct 2016, Jeff Bowman wrote:
I’m trying to better understand OffDelay and OnDelay:
http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments
My server requires ~3½ minutes to shut itself down. Considering this I’m
comfortable setting OffDelay to 300 (five minutes).
How
On Sat, 17 Sep 2016, Yevgeniy Kuksenko wrote:
Hello all, I have been having a problem with upsmon on Fedora 24 on boot. NUT
is configured as a netclient to a Raspbian NUT server. After boot up upsmon
repeatedly says "connect failed: No such host". It is not able to connect at
all until the
On Fri, 25 Nov 2016, Jonah Naylor wrote:
I'm still getting "Connection refused on the client cgi screen as well
as in the shell it gives me UPS upsname@ipaddresshere is unavailable...
You reported that access works correctly from elsewhere on the master
subnetwork. Does access from the
On Thu, 24 Nov 2016, Jonah Naylor wrote:
I installed Nut via apt-get, not from source (which I'd rather stick
with if possible just for ease of security updates etc) - so I'm not too
sure if TCP wrappers are there or available...
This could be the problem, am I still able to add the wrappers
On Thu, 24 Nov 2016, Jonah Naylor wrote:
Hi can anyone please help.
Although I have two servers in the same cabinet/room and sharing the same UPS -
they're on different networks.
I've tried everything I can find online, but whatever I do I can't get the
slave nut client to connect to the
On Fri, 25 Nov 2016, Jonah Naylor wrote:
I don't think nut is built with TCP wrappers support, although the
package is listed as depending on libwrap...
Why would you have such a dependency if nut didn't use TCP Wrappers?
I ran this command: ldd /sbin/upsd | grep libwrap.so and it has
On Fri, 25 Nov 2016, Jonah Naylor wrote:
upsd : ipaddressofclientgoeshere
If it were me I would write
upsd : ipaddressofclient :\
spawn (/bin/mail -r hosts.allow@localhost\
-s '%s@%h accepted access to %d from %c'\
sysadmin@somedomain) &
1 - 100 of 152 matches
Mail list logo
