Pedro Côrte-Real wrote:
> When I start or restart nut I get three spurious messages as
> everything starts up:
>
> UPS [EMAIL PROTECTED] is unavailable
> Communications with UPS [EMAIL PROTECTED] lost
> Communications with UPS [EMAIL PROTECTED] established
I see the same stuff when I use my USB p
To prevent system shutdown on LB while testing you may set
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. Whith this
one you can check if the other parts of nut getting
When I start or restart nut I get three spurious messages as
everything starts up:
UPS [EMAIL PROTECTED] is unavailable
Communications with UPS [EMAIL PROTECTED] lost
Communications with UPS [EMAIL PROTECTED] established
Any way around this?
Pedro.
_
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 cab
Peter Selinger skrev:
Yes, this has been fixed some time ago in the SVN version. -- Peter
Thank you! I got the trunk and installed it, one thing that is a bit
strange to me, restarting can cause newhidups to eat up a whole lot of
memory or not restart at all...
[EMAIL PROTECTED] trunk]# /et
Yes, this has been fixed some time ago in the SVN version. -- Peter
Magnus Johansson wrote:
>
> Hi!
>
> I'm running NUT 2.0.4 and occasionally I get a segfault when starting
> newhidups and if I don't get a segfault when starting newhidups the
> process starts eating away at my memory. I sat d
Dear Michael,
it looks like your efforts were unnecessary. The instructions in
hid-subdrivers.txt are intended for devices that are not *already*
supported by newhidups. On the other hand, your UPS was made by Cyber
Power Systems, and is already supported by the APC/CyberPower
subdriver. Note the
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 t
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 w
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 [E
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
Hi!
I'm running NUT 2.0.4 and occasionally I get a segfault when starting
newhidups and if I don't get a segfault when starting newhidups the
process starts eating away at my memory. I sat down trying to genererate
-D debug info, but just because of that I can't get it to do a
segfault. S
12 matches
Mail list logo
