All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Steinberger <trefalgar@realitybytes.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Power Supply Monitoring
Date: Wed, 03 Jun 2009 03:09:49 +0000	[thread overview]
Message-ID: <4A25E97D.9080800@realitybytes.net> (raw)
In-Reply-To: <20090602164941.uz55en9rms0okkg0@blastoid.drak.net>

My hope is that if one power supply is no longer working, thus no longer 
producing any DC output, I could alarm on that value being 0. Again, 
this is just a hope.

> UPSes tend to have various amounts of AC power monitoring available,
> and that might be a better place to look.  Network UPS Tools
> http://www.networkupstools.org/ runs on Linux and can talk to many
> types of UPSes.
>
Tend to, but since the guy that does the monitoring rarely has the 
ability to make the purchases of said device, you tend to end up with 
old refurbished devices that don't have the ability to be monitored 
without a laptop and a console cable.

> Beyond that, the next step is usually to go to the site and look for
> any obvious problems - do half the machines reboot when the machine
> shop downstairs fires up the arc welder?  Did somebody set up 42U of
> servers on a 100 foot 16 gauge (30 m 1.0 mm^2) extension cord?  Then
> you start poking at it... depending on how subtle the problem is and
> your budget, you start with a $30 Kill-a-Watt meter, then move up to
> a $200 Fluke multimeter, and then maybe a multi-thousand-dollar Fluke
> or Dranetz data logger.
>
I'm really just looking for a way to do a simple function check on the 
power supplies to detect when they're operational. Not necessarily to 
find out what voltage is going through, but to see if it's even working 
or not. For example, we have one power supply on grid, the other is on 
UPS - the easiest way to detect if there's a problem with UPS or grid 
power is to monitor the power supplies on the boxes. This would function 
as a dual monitor if there was ever an issue with just a power supply.

Jacob

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2009-06-03  3:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 21:49 [lm-sensors] Power Supply Monitoring Jacob Steinberger
2009-06-02 22:15 ` Mark E. Hansen
2009-06-03  3:00 ` Matt Roberds
2009-06-03  3:09 ` Jacob Steinberger [this message]
2009-06-03  8:06 ` Jean Delvare
2009-06-03 14:31 ` Mark E. Hansen
2009-06-03 14:55 ` Jacob Steinberger
2009-06-03 15:05 ` Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A25E97D.9080800@realitybytes.net \
    --to=trefalgar@realitybytes.net \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.