On 11/11/06, Arjen de Korte [EMAIL PROTECTED] wrote:
The problem was the serial cable.
That why I recommended to try it under Windows with the bundled
software, to rule out a problem like this.
I see.
For contact closure type UPSes, they almost never are.
Ok, I will remember that!
I
On 11/12/06, Sergiy Kazakov [EMAIL PROTECTED] wrote:
To prevent system shutdown on LB while testing you may set
powervalue value in MONITOR line (in upsmon.conf) to 0 (zero). But
don't forget to set MINSUPPLIES to zero too. See comments in
upsmon.conf and man upsmon.conf for further details.
On 11/10/06, Arjen de Korte [EMAIL PROTECTED] wrote:[...]
If you're willing to try a few more things, comment out the part in theNUT startup script where 'upsmon' is started/stopped and fire it up. With'upsc [EMAIL PROTECTED]' you should be able to see the status of the UPS,
without the risk of
Ok, I 've done some more testing. I did comment out the upsmon entry in /etc/default/nut
Then loaded the driver like:
/lib/nut/genericups -x upstype=7 /dev/ttyS0It loaded and according syslog:Nov 11 10:19:47 radius1 genericups[8469]: Startup successfulHowever when I tried: radius1:/etc/nut# upsc
On 11/11/06, YvesDM [EMAIL PROTECTED] wrote:
[...]
We move on...
Ok, I think it's working. The problem was the serial cable. I had 2, one came with the ups, the other came with another ups. During my tests I changed the original cable with the other one.
I never changed it back, thinking they
On 11/11/06, YvesDM [EMAIL PROTECTED] wrote:
I don't know if the ups will actually shutdown the system now on low
battery.
If the status changes to OB LB, then it should shut your system down
(assuming everything else is still configured properly).
upsc ain't showing much information on the
YvesDM wrote:
Ok, I think it's working.
The problem was the serial cable.
That why I recommended to try it under Windows with the bundled
software, to rule out a problem like this.
I had 2, one came with the ups, the other came with another ups.
During my tests I changed the original cable
Disconnecting a UPS from a live server and testing it at a separate
workstation is a MUST if you're not absolutely sure the configuration is
correct. I would never use an UPS on a production system without double
checking that monitoring works. Otherwise your investment gives you a
false
radius1:/etc/nut# /lib/nut/genericups -a ups_name
Network UPS Tools - Generic UPS driver 1.30 (2.0.1)
No upstype set - see help text / man page!
The last line should ring a bell, don't you think so?
radius1:/etc/nut# /lib/nut/genericups upstype=7 -a ups_name
Network UPS Tools - Generic UPS
On 11/9/06, Arjen de Korte [EMAIL PROTECTED] wrote:
radius1:/etc/nut# /lib/nut/genericups -a ups_name Network UPS Tools - Generic UPS driver 1.30 (2.0.1) No upstype set - see help text / man page!The last line should ring a bell, don't you think so?
Yes so I've tried man nut :-) Honestly, you
PS Some logfiles from the instant shutdowns:The ups was NOT running on battery power. Nov 9 14:37:16 radius1 genericups[1640]: Startup successfulNov 9 14:37:16 radius1 upsd[1641]: /etc/nut/upsd.conf is world readable
Nov 9 14:37:16 radius1 upsd[1641]: Connected to UPS [ups_name]:
[ups_name]
driver = genericups
upstype = 7
port = /dev/ttyS0
desc = Sweex 1000VA UPS
Ok, I tried this.
The driver was loaded and. the server shutdown immediately.
Lesson #1: Always first test whether the driver is producing good results
(you must be able to read the
YvesDM wrote:
On 11/8/06, *Udo van den Heuvel* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Try Powermust.
radius1:/etc/nut# cat ups.conf
# Network UPS Tools: example ups.conf
#
user = nut
[ups_name]
driver = powermust
port = /dev/ttyS0
desc =
YvesDM wrote:
So what is your upsdrvctl problem?
Are we talking the same UPS here?
I have a Sweex, 800VA or so?
If yes, I wish I knew !
Maybe try the source to see what the function does that is mentioned in
the error?
___
Nut-upsuser
YvesDM wrote:
Are you absolutely sure that the UPS is connected to /dev/ttyS0? For
'upstype=7' the signals for 'on battery' and 'low battery' are -CTS and
-DCD (both zero). I wouldn't be surprized at all if this is the same as
nothing connected to the port you're monitoring
On 11/9/06, Arjen de Korte [EMAIL PROTECTED] wrote:
YvesDM wrote: Are you absolutely sure that the UPS is connected to /dev/ttyS0? For 'upstype=7' the signals for 'on battery' and 'low battery' are -CTS and -DCD (both zero). I wouldn't be surprized at all if this is the same as
nothing connected
I'm trying to get a sweex ups working with nut on debian sarge.
Good luck! Sweex is notorious for changing their products internally,
without telling you. Have you noticed that their online documentation
still mentions the SafeNet software? And that they even have the guts to
mention that their
On 11/7/06, YvesDM [EMAIL PROTECTED] wrote:
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=59artikel=95
It's shipped with UPSmart and according to the compatibility list it should
work with the
genericups
On 11/8/06, Charles Lepple [EMAIL PROTECTED] wrote:
genericups does not have very many ways to fail. What if you trystarting the driver directly, such as: /lib/nut/genericups -a ups_nameHi,When I do:radius1:/etc/nut# /lib/nut/genericups -a ups_name
Network UPS Tools - Generic UPS driver 1.30
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=59artikel=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
20 matches
Mail list logo
