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: u
On Tue, 13 Oct 2015, Davide Baldini wrote:
Guess I can assume that my OnePower A03-S1001 just doesn't support the
shutdown command. Might this be the case?
If the UPS does shut down, then it will have to do so after a delay and
not immediately on receiving the shutdown command. Does upsc
re
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, 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 Ch
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:
---
r
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 c
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 Lin
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. I
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 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 comma
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, 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:
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
Ap
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 a
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)
/s
?
Roger Price
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
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 non-e
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 d
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:
http://
On Wed, 4 Jun 2014, Mick wrote:
Some of the variables (those with HU_FLAG_ABSENT) are apparently not stored
on the UPS itself-- they are sent to the UPS when the shutdown command is
executed. Sending the value starts the timer, in some cases, but I think
the ups.delay.start value should be safe t
The latest release of openSUSE is 13.1 and it includes NUT 2.6.5. It is a
pleasure to report that this works well when equipped with a working set
of configuration files.
Additionally, the setup requires
1. Something to execute upsdrvctl shutdown to turn off the UPS unit. A
systemd script "
Le 2013-12-06 15:14, Angel Tsankov a écrit :
...if main power comes back within 10 seconds after the UPS has been
shut down, the UPS will power up the PC but the latter will not start.
On Fri, 6 Dec 2013, Rene Garcia wrote:
You can change the parameter ups.delay.start into your UPS to set
preference would be for
upslogx(LOG_DEBUG, "exec_cmd(%s) succeeded"); /* NEW */
to be LOG_INFO.
Roger
On Dec 4, 2013, at 3:35 PM, Roger Price wrote:
I would like nut to become more loquacious, and to log a much more complete
report of its activi
I would like nut to become more loquacious, and to log a much more
complete report of its activity. At present nut reports that its
components have started operation but does not automatically log their
activity when UPS's switch between OB and OL. I believe that this
under-reporting of impor
On Sun, 1 Dec 2013, Roberto Martelli wrote:
In my "upsmon.conf" I've setted this option for shutdown command:
SHUTDOWNCMD "/usr/sbin/pm-hibernate"
but when I pull the plug on my ups in way to test if this command works,
I obtain this error (in /var/log/syslog):
Dec 1 13:39:03 ubux upsmon[4561]:
On Wed Sep 11 10:45:48 PDT 2013 Lennart Poettering wrote:
So, it's a really bad idea to turn off UPS from userspace, simply
because you will race against the kernel's fs sync() code, and you never
know what will finish first: your UPS shutdown timeout or your fs
sync(). Doing this from userspa
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 Sat, 10 Aug 2013, Charles Lepple wrote:
I still haven't messed with systemd yet, so I am in over my head here.
Is this similar to what Kjell posted about? Or is it in addition to
that? http://www.kepstin.ca/blog/networkupstoolsnutandsystemd/
Calvin Walton (kepstin) discusses a complete man
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
/etc/systemd/system/up
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
Nut-upsuse
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 -s"UPS monitor" me@testhost.local
;;
...
..., but no email was generated
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
'upsdrvct
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 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 prog
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 u
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 k
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 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
Nut-upsuser@lists.alioth.
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
Nut-upsuser@lists.alio
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 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 yo
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
overri
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 desel
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 l
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
f
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 plu
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
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 stutdo
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 chan
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, 2 Nov 2009, Arnaud Quette wrote:
The first round on the new NUT website is mostly done:
http://new.networkupstools.org
So, your testing and feedback is welcome to finalize this step. Current
testing have been done using: FireFox 3.5, Chrome 4, IE6, 7 and 8.
Its good to see sites wit
On Tue, 1 Jul 2008, Arjen de Korte wrote:
> > I am trying to build an rpm for nut-2.2.2 on 64 bit opensuse 11.0.
> Why?
I didn't dare hope that opensuse would include nut-2.2.2, so I visited
http://networkupstools.org/packages.html where "SuSE RPMs" goes nowhere.
Perhaps it would be useful to poi
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 downloaded
On Tue, 22 Apr 2008, Manuel Wolfshant wrote:
> Roger Price wrote:
> > I loaded g++ which had not been asked for; it requires package
> > gcc42-c++.
> I'd say that the correct package is gcc-c++
> <http://ftp.iasi.roedu.net/mirrors/opensuse.org/distribution/openS
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
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 dow
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:
> http://opensource.mge
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 bu
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 tol
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/sb
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
http://rogerprice.org/nut-2.2.2/nut-2.2.2-pre2.x86_
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.
>
>
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.
>
>
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_
On Sat, 19 Apr 2008, Arjen de Korte wrote:
> > You're making this far more complex than needed. With the RPMs I sent you,
> > I also included the source RPM for nut (which was built on openSUSE 10.3
> > by the way). Extract that with
> > rpm -Uvh nut-2.2.2-pre2.src.rpm
> > and then rebuild the
On Fri, 18 Apr 2008, Arjen de Korte wrote:
> > However the command
> > ./configure --with-user=ups --with-group=nut add --with-usb add --with-lib
> > add --with-hal
> >
> > is rejected because there is no file "configure". Please excuse my
> > naivete' if I'm doing something noobie stupid.
>
> Y
On Fri, 18 Apr 2008, Carlos Rodrigues wrote:
> The libraries are present, yes, but they are 64bit and you are trying
> to install a 32bit rpm. You can either install the 32bit versions of
> those libraries, or try rebuilding the rpm to obtain a 64bit one.
Aha! I installed the source rpm, read the
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 install
On Thu, 18 Oct 2007, Arjen de Korte wrote:
> > Sorry, I should have been clearer. I replugged the UPS, but still got the
> > same result. I tried rebooting the system, but still got "No matching HID
> > UPS found"
>
> Can you start the driver in debug mode?
>
> /usr/lib/ups/driver/usbhid
On Wed, 17 Oct 2007, Arjen de Korte wrote:
> > I applied the change, and the head of file /etc/udev/rules.d now says:
> >
> ># udev rules for the NUT USB drivers
> >
> >ACTION!="add", GOTO="nut-usbups_rules_end"
> >SUBSYSTEM=="usb_device", GOTO="nut-usbups_rules_real"
> >SUBSYSTEM=
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. :
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]
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 whic
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 se
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. openSUS
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:
/usr/lib/ups/driver/
On Mon, 5 Jun 2006, Gary and Jane Pearce wrote:
> I am trying to get NUT as supplied with SuSE 10.1 working and I think I
> have a USB problem, possibly due to some missing startup scripts
> concerning permissions.
Just a passing thought - What result does the command /sbin/resmgr list
provide
- UPS MGE Premium Ellipse Premium 1200
- SuSE Linux 10.0 OSS, kernel 2.6.13 smp
- gcc version 4.0.2 20050901 (prerelease), glibc-2.3.5-40
- mgeups-psp-3.0.0-3, nut-2.0.2-4
- Dell Dimension 8400 with dual core Intel Xeon. 3.0GHz.
lsusb shows:
Bus 002 Device 003: ID 0463: MGE UPS Systems UP
101 - 178 of 178 matches
Mail list logo
