Hello list.
I'm contemplating buying new batteries and putting an older APC
Smart-UPS 3000XL back into service. Would that work well with NUT? Any
drawbacks to consider?
Thank you,
Tobias
--
Tobias Balle-Petersen
Kontrapunkt Group / System Administ
Hello
I'm testing the functionality of my NUT-setup (NUT 2.0.4-4 - Debian
stable). The system is connected to the UPS, but is not powered by it.
When running "upsmon -c fsd", upsmon says "Auto logout and shutdown
proceeding". This is all well and good, but I never see the machine
waiting f
Hello Arjen.
Arjen de Korte wrote:
> Still, it would be a good idea to test with 'upsmon -c fsd' first. You
> want to make sure that shutdown command is sent to the UPS when going
> down. Preferably when the system is *not* powered by the UPS, to see that
> the system is halted before the power is
Hello Arjen.
Arjen de Korte wrote:
> In general, shutdown will be triggered when the UPS is both on battery
> *and* reporting low battery. The latter may or may not be user
> configurable. In your case, it looks like the driver has no way of
> changing this level, so when this actually happens dep
Hello.
I have a PW9120 hooked up via a serial cable running NUT 2.0.4.
When running upsc I cant see any parameter that looks like it would trigger a
shutdown. Theres is
nothing like "battery.charge.low: 30" or "battery.charge.warning: 30".
I get:
ambient.temperature
battery.(charge|runtime|volt
Hello Arjen.
Arjen de Korte wrote:
> This is done through the initialization of the bcmxcp driver. It doesn't
> require you to do anything, other than running this driver at least once
> with the UPS. After that, the UPS should remember this setting.
This does not seem to be the case. Switching t
Hello Kjell.
Kjell Claesson wrote:
> You have been busy i see. OK it is possible to set the 9120 to requsted mode
> only, and this is done by the serial driver part. And it should remain so
> after power cycling.
How is this accomplished? Any chance of a step by step tutorial?
> One thing tha
Hello Arjen.
Arjen de Korte wrote:
> No, it should be in the UPS section since it is a driver specific thing.
> That is, if you fix the typo I made. The variable is called 'baud_rate',
> not 'baudrate'.
OK. Thanks.
Tobias
___
Nut-upsuser mailing list
Tobias Balle-Petersen wrote:
> Hello Arjen.
>
> Arjen de Korte wrote:
>> Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should fix
>> this.
>
> Strange, it tells me this is not supported. I'm on 2.0.4.
A
Hello Arjen.
Arjen de Korte wrote:
> Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should fix
> this.
Strange, it tells me this is not supported. I'm on 2.0.4.
Tobias
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
Hello all.
I have now connected the UPS via a serial-cable to a PC running Debian Etch and
Nut 2.0.4.
When running "upsdrvctl -u root start" I get:
Communications with UPS lost: Error executing command
Communications with UPS lost: Error executing command
Communications with UPS lost: Error exec
Hello Ken.
[EMAIL PROTECTED] wrote:
> FYI, I had this problem about a year ago w/ the 9120 and I believe that
> was the same conclusion. It'd be really nice to get the USB port working.
> I've been using a serial->USB cable.
What is the name of the converter you are using?
> Also, AFAIK, you c
Hello Arjen.
Arjen de Korte wrote:
> Have you tried the serial connection?
No, there is no serial port on my machine.
> 1) Apparently, this UPS needs to be told only to reply to specific
> requests and not send unsollicited status updates. The bcmxcp (serial)
> driver supposedly does this, the
Hello
Arnaud Quette wrote:
> we'll need to have more verbose info.
> please exec "export USB_DEBUG=3 && /lib/nut/bcmxcp_usb -DDD -a ups1"
> and send us the gzip'ed output
My machine cant seem to find the export command.
Thanks,
Tobias
___
Nut-upsuse
Hello...
Just to make sure I did a clean install of debian etch and tested. I still get
the same errors. Nut
2.0.4.
Tobias
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Hello
Kjell Claesson wrote:
> Then you should get new version of nut as 2.0.4 is past date.
I have updated to nut 2.2.0-1 as suggested. Unfortunately I still get the same
type of errors:
Network UPS Tools - UPS driver controller 2.2.0-
Network UPS Tools - BCMXCP UPS driver 0.11 (2.2.0-)
W
Tobias Balle-Petersen wrote:
> Hmmm... I guess I need a kernel newer than the one in atable:
Just realized I dont have the etch stable kernel on my testing system. Igonre
the above.
Thanks,
Tobias
___
Nut-upsuser mailing list
Nut-upsu
Arnaud Quette wrote:
> the source repository is also there (now) if you will to rebuild the package
> ;-)
Hmmm... I guess I need a kernel newer than the one in atable:
Unpacking nut (from nut_2.2.0-1_powerpc.deb) ...
Setting up nut (2.2.0-1) ...
udev requires a kernel >= 2.6.15, not started.
Th
Hi Arnaud.
Arnaud Quette wrote:
> the source repository is also there (now) if you will to rebuild the package
> ;-)
Great, sounds good. I was just about to compile from the source on the site. I
guess this way is
better/easier. I'll give it a try and report back.
Thanks,
Tobias
_
Hi Kjell.
Kjell Claesson wrote:
>> I have tried two different USB-cables. The one that came with the UPS and
>> another one I had lying around. I have tried both ports on the computer
>> (Apple mac G4).
>>
>
> Was there any difference in the communication ?
Just checked again. The communication
Hi Arnaud.
Arnaud Quette wrote:
> add this line to your /etc/apt/sources.list:
> deb http://opensource.mgeops.com/stable/debian binary/
I'm running on a PowerPC. The repository only has i386 packages as far as I can
tell.
Tobias
___
Nut-upsuser mail
Kjell Claesson wrote:
> Was there any difference in the communication ?
No.
> Both yes and no. It should work but as no one have give a positive feedback on
> this we can not enter it into the chart.
OK, so we don't actually know it works.
>> Does communicating with the UPS demand more of the
Hi Kjell.
Kjell Claesson wrote:
> > It looks like you have a problem with the usb connection. Check the cabling.
> > The driver is using a binary protocol with checksum, and is hard on bit
> > errors.
I have tried two different USB-cables. The one that came with the UPS and
another one I had lyi
ding is that the NUT
SNMP-driver does not allow the
UPS to be shut down. This is why I am now turning to USB.
Any ideas as to how I can get my setup running?
Thank you,
Tobias Balle-Petersen
___
Nut-upsuser mailing list
Nut-upsuser@lists.al
Hello
I'm wondering what happens in this scenario:
There is a power failure. UPS supports machines for some time.
NUT tells all machines to shutdown.
Power is restored after machines have shut down but before UPS battery runs out.
The power is thus never lost but the machines were shut down.
25 matches
Mail list logo