unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Page:
Section:
Apropos / Subsearch:
optional field

 @(#) ups_mond.1m $Date: 2001/09/25 17:51:18 $Revision: r11.11/2 PATCH_11.11
 (PHCO_24173)




























































				    - 1 -	  Formatted:  August 2, 2006






 ups_mond(1M)							ups_mond(1M)




 NAME
      ups_mond - HP PowerTrust Uninterruptible Power System monitor daemon

 SYNOPSIS
      /usr/lbin/ups_mond [-f configfile] [-s] [-t]

 DESCRIPTION
      When it detects a loss of AC power for a period of time exceeding a
      configured limit, ups_mond ensures file system integrity by shutting
      down HP-UX.  To do this, ups_mond uses the device special files
      specified in its configuration file (/etc/ups_conf by default) to
      monitor the state of each HP PowerTrust Uninterruptible Power System
      (UPS) attached to the system.

      Use the -f option to specify a configuration file other than
      /etc/ups_conf.  See ups_conf(4) for a description of the configuration
      file format.

      By default, ups_mond is locked into memory (see plock(2)).  That is,
      ups_mond is not swappable.  Although extreme caution is required, you
      can make ups_mond swappable if all swap disks are powered by an
      uninterruptible power system (assured to have power when the primary
      power source fails).  To make ups_mond swappable, use the -s option.

      When ups_mond is forced to shutdown the system, it executes the
      /usr/sbin/shutdown command with real-time priority.  This can be
      modifed to execute with a timeshare (non-real-time) priority by use of
      the -t option.

      ups_mond is started by init (see init(1M)) by means of an entry in the
      file /etc/inittab (see inittab(4)).  The inittab entry uses the
      respawn option to automatically restart ups_mond if ups_mond is
      terminated by the kill command (see kill(1)).  This entry should
      follow the entry:

	   sqnc::wait:/sbin/rc <&lt&lt&lt;/dev/console >&gt&gt&gt;/dev/console 2>&gt&gt&gt;&&amp&amp&amp;1
					  # system initialization

      so that ups_mond is started after the system logging daemon (syslogd).
      It should also be run with real-time priority to assure its execution
      (see rtprio(1)).

      ups_mond logs messages, and when appropriate invokes
      /usr/sbin/shutdown using the -h option, or /usr/sbin/reboot.  For each
      configured UPS, ups_mond can be instructed (in /etc/ups_conf) to log
      messages only, without taking shutdown or reboot action.	See MSG_ONLY
      in ups_conf(4).  By default ups_mond performs the shutdown and reboot
      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



				    - 1 -	  Formatted:  August 2, 2006






 ups_mond(1M)							ups_mond(1M)




      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 ups_conf to tell the UPS not to come back up when AC line
      voltage is restored (see ups_conf(4)).

      ups_mond uses the syslog message logging facility to log these
      occurrences (see syslog(3C)).  Messages are written to the console if
      ups_mond is unable to send them to syslogd.  Critical messages (see
      DIAGNOSTICS section) are also sent to the console.

 RETURN VALUE
      ups_mond returns the following values:

	   zero (0)	Successful Completion
	   non-zero	Error encountered.  See ERRORS below.

 EXAMPLES
      The entry in /etc/inittab should be similar to this:

	   ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf

 DIAGNOSTICS
      Messages resulting from normal operation:

	   UPS Monitor daemon starting; using configuration file
	   <&lt&lt&lt;configfilename>&gt&gt&gt;.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK: AC Power back on.

	   AC Power to all recognized, system critical UPS's OK! System will
	   not shutdown.

      Messages resulting in exit of daemon:

	   usage: ups_mond [-f configfile].

	   cannot exec /usr/lbin/ups_mond -f <&lt&lt&lt;configfilename>&gt&gt&gt; -e
	   ups_monchild due to <&lt&lt&lt;error>&gt&gt&gt;.

	   permission denied; must be superuser.

	   exiting; unable to lock process in memory: <&lt&lt&lt;errno>&gt&gt&gt;.

	   aborted, configfile <&lt&lt&lt;configfilename>&gt&gt&gt; open received error:
	   <&lt&lt&lt;errno>&gt&gt&gt;.

	   aborted, configfile <&lt&lt&lt;configfilename>&gt&gt&gt; fseek error: <&lt&lt&lt;errno>&gt&gt&gt;.

	   aborted, malloc error: <&lt&lt&lt;errno>&gt&gt&gt;.





				    - 2 -	  Formatted:  August 2, 2006






 ups_mond(1M)							ups_mond(1M)




	   terminated by signal <&lt&lt&lt;decimal value of signal>&gt&gt&gt;.

      Messages for which shutdown might be run (depends on UPS
      configuration):

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; AC POWER FAILURE - running on UPS
	   battery.

	   If power is not returned within previously configured time
	   period, your system will automatically go to graceful shutdown.

	   If power is not returned within previously configured time
	   period, your system will automatically go to graceful shutdown.
	   System will not come back up after shutdown.

      Messages for which reboot might be run (depends on UPS configuration):

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; battery low.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; no output - either switch setting
	   wrong on UPS or bad UPS.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; failed - requires repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; current overload; UPS turned itself
	   off - either UPS bad or too many devices connected.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; ambient temperature too high; UPS
	   turned itself off - reduce heat in area.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; output voltage too high; UPS turned
	   itself off - requires repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; output voltage too low; UPS turned
	   itself off - requires repair.

	   cannot exec shutdown due to <&lt&lt&lt;errno>&gt&gt&gt;.

	   The above messages are followed by the following message:

	   reboot -halt invoked due to UPS error cited in previous syslog
	   message.

      Messages that are only logged (no shutdown/reboot action is taken):

	   warning - no upstty: UPS's found in configfile <&lt&lt&lt;configfilename>&gt&gt&gt;;
	   daemon running for no purpose.

	   warning - shutdown delay or shutdown timeout parameter in
	   configfile <&lt&lt&lt;configfilename>&gt&gt&gt; missing or not greater than zero;
	   using default.



				    - 3 -	  Formatted:  August 2, 2006






 ups_mond(1M)							ups_mond(1M)




	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; in bypass-mode; no AC Power-loss
	   protection.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; interrupted, but read of ups status
	   failed - possible UPS hardware problem.

	   upstty <&lt&lt&lt;tty special file name>&gt&gt&gt; failed open: <&lt&lt&lt;errno>&gt&gt&gt;; ignoring
	   that tty and continuing.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; ioctl(TCGETA) failed: <&lt&lt&lt;errno>&gt&gt&gt;;
	   ignoring that UPS.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; ioctl(TCSETAF) failed <&lt&lt&lt;errno>&gt&gt&gt;;
	   ignoring that UPS.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; line too noisy; ignoring that UPS.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; could not enable; loss of power would
	   not be detectable.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; read failed: <&lt&lt&lt;errno>&gt&gt&gt;; Uninterruptible
	   Power Supply has not been connected correctly; loss of power
	   would not be detectable.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; write failed: <&lt&lt&lt;errno>&gt&gt&gt;; ignoring that
	   UPS.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; read of status received ILLEGAL CMD
	   or NOISY LINE.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; read of status received <&lt&lt&lt;number>&gt&gt&gt;
	   bytes of unexpected data (octal: <&lt&lt&lt;octal returned>&gt&gt&gt;): <&lt&lt&lt;string
	   returned>&gt&gt&gt;.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; read of status failed: <&lt&lt&lt;errno>&gt&gt&gt;.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; write failed: <&lt&lt&lt;errno>&gt&gt&gt;.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Failure Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Inverter Failure
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off No Battery Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Battery Charger Fault
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Current Overload
	   Alarm.




				    - 4 -	  Formatted:  August 2, 2006






 ups_mond(1M)							ups_mond(1M)




	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off High Ambient
	   Temperature Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Battery Failure Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off High Battery Voltage
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Low Battery Voltage
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off High Output Voltage
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off Low Output Voltage
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; OK; turned-off UPS Communication Lost
	   Alarm.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; Inverter Failure requires repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; No Battery - ensure UPS battery
	   installed.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; Battery Charger Fault- requires
	   repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; Current Overload - either UPS bad or
	   too many devices connected.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; High Ambient Temperature-reduce area
	   temperature.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; Battery Failure- requires repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; High Battery Voltage - requires
	   repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; Low Battery Voltage - requires
	   repair.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; Communication Lost - At least one or
	   more components of the UPS subsystem has lost communications.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; UNKNOWN status/alarm <&lt&lt&lt;hex number>&gt&gt&gt; -
	   may require repair.

	   write to UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; of command <&lt&lt&lt;cmd string>&gt&gt&gt;
	   Failed: <&lt&lt&lt;errno>&gt&gt&gt;.




				    - 5 -	  Formatted:  August 2, 2006






 ups_mond(1M)							ups_mond(1M)




	   read from UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; after sending command <&lt&lt&lt;cmd
	   string>&gt&gt&gt; to it failed; <&lt&lt&lt;errno>&gt&gt&gt;.

	   UPS <&lt&lt&lt;tty special file name>&gt&gt&gt; could not execute command <&lt&lt&lt;cmd
	   string>&gt&gt&gt;; returned (octal: <&lt&lt&lt;octal returned>&gt&gt&gt;): <&lt&lt&lt;string returned>&gt&gt&gt; -
	   possible bad signal cable.

      Messages relating to Timer Controlled Power On and Off:

	   Timer Controlled On/Off information invalid; ignored.

	   mknod error: <&lt&lt&lt;errno>&gt&gt&gt; for Timed On/Off fifo file
	   /var/tmp/timed_off; continuing without.

	   open error: <&lt&lt&lt;errno>&gt&gt&gt; for Timed On/Off fifo file
	   /var/tmp/timed_off; continuing without.

	   Timer Controlled On value exceeds UPS <&lt&lt&lt;tty special file name>&gt&gt&gt;
	   maximum. The maximum value of <&lt&lt&lt;maximum supported decimal value>&gt&gt&gt;
	   will be used for this UPS.

 ERRORS
      ups_mond returns the following error values:

	   EINVAL	ups_mond encountered an incorrect parameter.
	   EPERM	Insufficient privileges.  ups_mond must be started
			by a superuser.
	   EINTR	ups_mond was interrupted (terminated) by signal() or
			kill().	 See signal(2) and kill(1).
	   one (1)	For all other error conditions.

 FILES
      /dev/tty*
      /etc/ups_conf
      /var/tmp/timed_off
      /var/adm/syslog/syslog.log

 SEE ALSO
      kill(1), init(1M), plock(2), signal(2), syslog(3C), inittab(4),
      ups_conf(4).














				    - 6 -	  Formatted:  August 2, 2006