upsd appears to send the FSD command to the UPS, upsmon then runs my
NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off.
Here are the /var/log/daemon.log entries:
I have seen a similar problem with usbhid-ups on an MGE Pulsar
Evolution with Ubuntu 7.04. The machine shuts down on
I am thinking about using the existing NUT software to tell the slave
servers to shutdown if the temperature in the server room becomes too
high.
If your UPS has a temperature sensor, that's possible. You could script
something that polls 'ups.temperature' every minute and call 'upsmon -c
Hi
I am thinking about using the existing NUT software to tell the slave
servers
to shutdown if the temperature in the server room becomes too high.
I was thinking of monitoring the temperature on the master NUT server
and
then just letting the slave clients shut down. But the slaves (and
Paul Mogren wrote:
Sorry, I forgot to CC the list.
--- Paul Mogren [EMAIL PROTECTED] wrote:
Which version of NUT is this? This shouldn't
happen
anymore with nut-2.2.0.
I'm using a SUSE-managed package which is based on
nut-2.0.4. I didn't find a 2.2 RPM for SUSE, so I
guess I'd have
Sorry, I forgot to CC the list.
--- Paul Mogren [EMAIL PROTECTED] wrote:
Which version of NUT is this? This shouldn't
happen
anymore with nut-2.2.0.
I'm using a SUSE-managed package which is based on
nut-2.0.4. I didn't find a 2.2 RPM for SUSE, so I
guess I'd have to compile from
I'm using NUT with an MGE Ellipse USB, which I
understand to be rather slow to respond. Every time I
start the NUT services, I get the Communications
lost notifications at first, but then it starts to
work normally.
Which version of NUT is this? This shouldn't happen anymore with nut-2.2.0.
Hello,
I'm using NUT with an MGE Ellipse USB, which I
understand to be rather slow to respond. Every time I
start the NUT services, I get the Communications
lost notifications at first, but then it starts to
work normally. I've increased polling frequencies in
upsmon.conf to the point that I get
I have a plan to do the same thing. The approach I was going to take is to
use several fake ups units that use contact closure style drivers. The use
a contact closure from the temp sensor to send the fake UPS units into LB
status. If the are fake units and all servers monitor for these in
My thought was not to worry about shutting down the UPS. Since I want to
manually start the servers after a temp shutdown then if the server powers
off as a slave monitoring the fake UPS the server will never reboot as the
UPS will stay powered on. Or I could just be totally out in left field.
[...]
Is the shutoff working otherwise (ie calling upsdrvctl -k (CAUTION: no
sensitive load on the UPS; only light bulbs or alike))?
We have no '-k' option in upsdrvctl. The proper command to test this is
either
upsdrvctl shutdown upsname
or
bcmxcp_usb -a upsname -k
Best regards,
Den torsdag 26.jul kl. 14:18 skrev Doug Parsons:
I have a plan to do the same thing. The approach I was going to
take is to
use several fake ups units that use contact closure style drivers.
The use a
contact closure from the temp sensor to send the fake UPS units
into LB
status. If
Do you really need a fake thing? cant you fake it in software and
once the
temperature goes too high you just run a script which hooks into NUT and
sets the TemperaturUPS to NO battery or something and shut it down using
that? I was planning to use lmsensors to monitor the temperature and
2007/7/26, Stuart Rackham [EMAIL PROTECTED]:
Hi
I'm having a problem with the bcmxcp_usb driver FSD command: everything
seems to work apart from:
upsmon -c fsd
Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105
UPS.
upsd appears to send the FSD command to the
Den torsdag 26.jul kl. 12:19 skrev Arjen de Korte:
The problem here is that once you've switched off all your
equipment, it
will stayoff until someone intervenes.
true, but thats okay
Then noone will tell the NUT slave clients to shut down gracefully.
I am open to other suggestions if
I have a plan to do the same thing. The approach I was going to take is to
use several fake ups units that use contact closure style drivers. The use a
contact closure from the temp sensor to send the fake UPS units into LB
status. If the are fake units and all servers monitor for these in
Do you really need a fake thing?
No.
cant you fake it in software and once the temperature goes too high you
just run a script which hooks into NUT and sets the TemperaturUPS to NO
battery or something and shut it down using that? I was planning to use
lmsensors to monitor the temperature
If not, you could still use a 'fake' UPS that is monitored by your upsmon
master and use the NOTIFYCMD to create a flag that prevents 'upsdrvctl
shutdown' from being called.
Or even easier, by using the undocumented '-f configfile' option for
upsmon, to specify an alternate upsmon.conf file,
Den Thursday 26 July 2007 01.19.00 skrev Stuart Rackham:
Hi
Hi Stuart,
I'm having a problem with the bcmxcp_usb driver FSD command: everything
seems to work apart from:
upsmon -c fsd
8snip
This part have been answered.
One peculiarity --
18 matches
Mail list logo
