Power monitoring and logging with Apcupsd and Cacti


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Power monitoring and logging with Apcupsd and Cacti
# 1  
Old 09-04-2008
Power monitoring and logging with Apcupsd and Cacti

09-04-2008 11:00 AM
For some time I have been using the American Power Conversion (APC) uninterruptible power supply (UPS) daemon Apcupsd to interface my desktop computer with my APC Back-UPS ES 550. Available for Linux, Windows, Mac OS X, and Solaris 10, Apcupsd reliably warns me when the power goes out and gives me time to get my box properly shut down before data is lost, or does so automatically if I am not there to supervise.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Linux

Syslog not logging successful logging while unlocking server's console

When unlocking a Linux server's console there's no event indicating successful logging Is there a way I can fix this ? I have the following in my rsyslog.conf auth.info /var/log/secure authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies

2. UNIX and Linux Applications

Apcupsd crashes

I am trying to run apcupsd, but it will not retain contact the UPS root@meow:/home/ethan/UPS/gapcmon-0.8.9# /etc/init.d/apcupsd start Starting UPS power management: A copy of the daemon is still running. If you just stopped it, please wait about 5 seconds for it to shut down.... (0 Replies)
Discussion started by: Meow613
0 Replies

3. Infrastructure Monitoring

How to install Cacti (a system monitoring and graphing solution) with Nginx?

Here's a short tutorial on installing Cacti with Nginx on Linux. (0 Replies)
Discussion started by: notblog
0 Replies

4. UNIX and Linux Applications

Cacti Getting Error

Dear Expert, I just succesfully installed cacti for monitoring my all of device in my office. But i got the strange, when i was pointing to the browser to run cacti there is a message like this. Invalid PHP_SELF Path What happen on my cacti configuration. Thanxs for your suggestion... (2 Replies)
Discussion started by: tpx99
2 Replies

5. HP-UX

How to shutdown Power Trust UPS Monitoring?

Hi, We had a HP Power Trust UPS connected to our HP Server using HP Unix 11. The UPS has died, and been taken off the server. The / filesystem runs out off space (100% full) as a core file is made in /etc/opt/resmon. The core file mentions monitoring of the UPS. Removing this file, another one... (3 Replies)
Discussion started by: kanpatel
3 Replies
Login or Register to Ask a Question
ups_mond(1M)															      ups_mond(1M)

NAME
ups_mond - HP PowerTrust Uninterruptible Power System monitor daemon SYNOPSIS
configfile] DESCRIPTION
When it detects a loss of AC power for a period of time exceeding a configured limit, ensures file system integrity by shutting down HP-UX. To do this, uses the device special files specified in its configuration file by default) to monitor the state of each HP PowerTrust Unin- terruptible Power System (UPS) attached to the system. Use the option to specify a configuration file other than See ups_conf(4) for a description of the configuration file format. By default, is locked into memory (see plock(2)). That is, is not swappable. Although extreme caution is required, you can make swappable if all swap disks are powered by an uninterruptible power system (assured to have power when the primary power source fails). To make swappable, use the option. When is forced to shutdown the system, it executes the command with real-time priority (default behavior). can be configured to execute command with a timeshare (non-real-time) priority by using the option. is started by (see init(1M)) by means of an entry in the file (see inittab(4)). The entry uses the option to automatically restart if is terminated by the command (see kill(1)). This entry should follow the entry: so that is started after the system logging daemon It should also be run with real-time priority to assure its execution (see rtprio(1)). logs messages, and when appropriate invokes using the option, or For each configured UPS, can be instructed (in to log messages only, with- out taking or action. See MSG_ONLY in ups_conf(4). By default performs the and actions. Note that when the shutdown is performed, UPSs that have lost AC line voltage will be turned off once the shutdown_timeout_mins time has expired (see ups_conf(4)). By default the system will power on when the AC line voltage is restored. The kill_after_shutdown line can be added to to tell the UPS not to come back up when AC line voltage is restored (see ups_conf(4)). uses the message logging facility to log these occurrences (see syslog(3C)). Messages are written to the console if is unable to send them to Critical messages (see DIAGNOSTICS section) are also sent to the console. RETURN VALUE
returns the following values: zero(0) Successful Completion non-zero Error encountered. See ERRORS below. EXAMPLES
The entry in should be similar to this: DIAGNOSTICS
Messages resulting from normal operation: Messages resulting in exit of daemon: Messages for which might be run (depends on UPS configuration): Messages for which might be run (depends on UPS configuration): The above messages are followed by the following message: Messages that are only logged (no action is taken): Messages relating to Timer Controlled Power On and Off: ERRORS
returns the following error values: encountered an incorrect parameter. Insufficient privileges. must be started by a superuser. was interrupted (terminated) by or See signal(2) and kill(1). one(1) For all other error conditions. FILES
SEE ALSO
kill(1), init(1M), plock(2), signal(2), syslog(3C), inittab(4), ups_conf(4). ups_mond(1M)