The cron log won't be outputted anymore if rsyslogd is listening /dev/log instead of /run/systemd/journal/syslog.

Solution Unverified - Updated -

Issue

  • After changing the log socket to "/dev/log" with commenting out the following setting in /etc/rsyslog.d/listen.conf,
    the messages of executing cron job won't be outputted any more.
#$SystemLogSocketName /run/systemd/journal/syslog
  • The logs whose tag are "crontab" will be outputted as normal. However, the logs of "CROND" won't be outputted any more.
Nov 19 16:17:54 R74 <cron:info> crontab[6534]: (root) LIST (root)
Nov 19 16:17:54 R74 <cron:err> crontab[6534]: PAM pam_end: NULL pam handle passed
Nov 19 16:18:30 R74 <cron:info> crontab[6571]: (root) LIST (root)
Nov 19 16:18:30 R74 <cron:err> crontab[6571]: PAM pam_end: NULL pam handle passed
//after changing listening socket:
Nov 19 16:28:47 R74 <cron:info> crond[6878]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 27% if used.)
Nov 19 16:28:47 R74 <cron:info> crond[6878]: (CRON) INFO (running with inotify support)
Nov 19 16:28:47 R74 <cron:info> crond[6878]: (CRON) INFO (@reboot jobs will be run at computer's startup.)
Nov 19 16:29:01 R74 <cron:info> CROND[6884]: (root) CMD (logger test)   <<<<<

Environment

  • Red Hat Enterprise Linux 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content