CUPS
This template assesses the status and performance of a CUPS service installed on a Linux/Unix system. Perl scripts are used for retrieving performance data.
Prerequisites: SSH and Perl installed on the target server.
Credentials: Root credentials on the target server.
Monitored Components:
Daemon CUPS status
This monitor returns the status of a Linux/Unix print server daemon.
Possible values:
0 - CUPS daemon is stopped.
1 - CUPS daemon is running.
Print queue
This monitor returns the current length of the default print queue.
Total pages printed
This monitor returns the number of printed pages by retrieving data from the CUPS page_log file.
Note: By default, the script retrieves this information from the /var/log/cups/page_logfile. If this file has another location on the target server, you should correct the path in the script argument box.
New emergency messages in CUPS error log
This monitor returns the number of new emergency messages by retrieving data from the CUPS error_log file. All emergency events begin with the "X" symbol.
This monitor should be zero all times. If it is not, you should manually examine this log file.
Note: By default, the script retrieves this information from the /var/log/cups/error_logfile. If this file has another location on the target server, you should correct the path in the script argument box.
New warning messages in CUPS error log
This monitor returns the number of new warning messages by retrieving data from the CUPS error_log file. All emergency events begin with the "W" symbol.
This monitor should be zero all times. If it is not, you should manually examine this log file.
Note: By default, the script retrieves this information from the /var/log/cups/error_logfile. If this file has another location on the target server, you should correct the path in the script argument box.
New alert messages in CUPS error log
This monitor returns the number of new alert messages by retrieving data from the CUPS error_log file. All emergency events begin with the "A" symbol.
This monitor should be zero all times. If it is not, you should manually examine this log file.
Note: By default, the script retrieves this information from the /var/log/cups/error_logfile. If this file has another location on the target server, you should correct the path in the script argument box.
New critical error messages in CUPS error log
This monitor returns the number of new critical error messages by retrieving data from the CUPS error_log file. All emergency events begin with the "C" symbol.
This monitor should be zero all times. If it is not, you should manually examine this log file.
Note: By default, the script retrieves this information from the /var/log/cups/error_logfile. If this file has another location on the target server, you should correct the path in the script argument box.
CUPS listening TCP port
This component monitor tests the ability of a CUPS service to accept incoming sessions.
By default, it monitors the TCP 631 port. If your CUPS server listens on another port, you should manually change it.
Portions of this document were originally created by and are excerpted from the following sources:
Oracle Corporation, “Oracle System Administration Guide: Printing,” Copyright 
2012 Oracle Corporation. All rights reserved. Available at http://download.oracle.com/docs/cd/E19963-01/html/821-1457/printref-18623.html
IBM Corporation, “AIX Documentation,” Copyright 2012 IBM Corporation. All rights reserved. Available at http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds6/vmstat.htm
Gurudatta Blog, Solaris and Linus, “Solaris SPARC Boot Sequence,” Copyright @ 2009-2012 gurudatta. All rights reserved. Available at http://gurudatta-solaris.blogspot.com/2009/12/solaris-notes.html
