Why do we get "Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/*.conf file" error messages from Cron?

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 4.0

Issue

  • Getting "Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/*.conf file" from Cron. Snippets from the error messages are given below.

    /etc/cron.daily/00-logwatch:

*** Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/messages.conf file ?
*** Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/maillog.conf file ?
*** Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/autorpm.conf file ?
*** Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/cisco.conf file ?
*** Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/clam-update.conf file ?
*** Error: There is no logfile defined. Do you have a /etc/log.d/confconf/logfiles/cron.conf file ?

Resolution

  • This error occurs due to the files mentioned in error message are missing from the system.
  • Make sure that all the files mentioned in the error messages are present under '/etc/log.d/conf/logfiles' directory.
  • If those files are missing, copy the missing files from any other system.

/etc/log.d/conf/services/* : Configuration files for the various services whose log entries LogWatch can process.
/etc/log.d/conf/logfiles/* : Configuration files for the various logfiles that the above service’s log entries are stored in.

Root Cause

  • The files mentioned in the error messages are missing from the system.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments