Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am looking for a better way to log cronjobs. Most cronjobs tend to spam email or the console, get ignored, or create yet another logfile.

In this case, I have a Nagios NSCA script which sends data to a central Nagios sever. This send_nsca script also prints a single status line to STDOUT, indicating success or failure.

0 * * * * root    /usr/local/nagios/sbin/nsca_check_disk

This emails the following message to root@localhost, which is then forwarded to my team of sysadmins. Spam.

forwarded nsca_check_disk: 1 data packet(s) sent to host successfully.

I'm looking for a logging method which:

  1. Doesn't spam the messages to email or the console
  2. Don't create yet another krufty logfile which requires cleanup months or years later.
  3. Capture the log information somewhere, so it can be viewed later if desired.
  4. Works on most unixes
  5. Fits into an existing log infrastructure.
  6. Uses common syslog conventions like 'facility' and 'priority'
  7. Can work with third party scripts which don't always do logging internally.
share|improve this question

2 Answers 2

up vote 14 down vote accepted

In the process of writing this question, I answered myself. So I'll answer myself "Jeopardy-style". This expands on the answer provided by Dennis Williamson.

The following will send any Cron output to /usr/bin/logger (including stderr, which is converted to stdout using 2>&1), which will send to syslog, with a 'tag' of nsca_check_disk. Syslog handles it from there. Since these systems (CentOS and FreeBSD) already have built-in log rotation mechanisms, I don't need to worry about a log like /var/log/mycustom.log filling up a disk.

*/5 * * * * root    /usr/local/nagios/sbin/nsca_check_disk 2>&1 | /usr/bin/logger -t nsca_check_disk

/var/log/messages now has one additional message which says this:

Apr 29, 17:40:00 192.168.6.19 nsca_check_disk: 1 data packet(s) sent to host successfully.

I like /usr/bin/logger , because it works well with an existing syslog configuration and infrastructure, and is included with most Unix distros. Most *nix distributions already do log rotation and do it well.

share|improve this answer
    
What does the 2>&1 command do? what does it mean? Thank you. –  Brettski Oct 5 '13 at 0:07
1  

Pipe the output through logger.

0 * * * * root    /usr/local/nagios/sbin/nsca_check_disk | logger -p local0.notice

Edit: Your update looks like the right way to go.

share|improve this answer
    
Thanks! After I posted my question, I saw that Apache pipes log output to /usr/bin/logger . I didn't realize that we could pipe output to logger(1) -- it's not in the manpage! –  Stefan Lasiewski Apr 30 '10 at 17:10
1  
"message - Write the message to log; if not specified, and the -f flag is not provided, standard input is logged." –  Dennis Williamson Apr 30 '10 at 17:39

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.