Linux Syslogd: Nothing Gets Logged Using /dev/log And /jail/apache/dev/log

by

If you’re having trouble getting log messages to be recorded using /dev/log or /jail/apache/dev/log in a Unix or Linux system, there are several potential causes and solutions to consider:

  1. Check the syslog configuration: Make sure that the syslog daemon (e.g., rsyslogd or syslog-ng) is configured to log messages to the correct file or socket. You can check the syslog configuration by looking at the configuration files in the /etc/rsyslog.d or /etc/syslog-ng directory.
  2. Check permissions: Make sure that the syslog daemon has permission to write to the log file or socket. You can check the permissions by using the ls -l command on the log file or socket.
  3. Check disk space: Make sure that there is enough disk space for the log messages. If the disk is full, the syslog daemon may be unable to write to the log file or socket.
  4. Check the log file: If you are logging to a file, make sure that the file is not being truncated or rotated by another process. You can check the log file by using the tail command.
  5. Restart the syslog daemon: If you’ve made changes to the syslog configuration or permissions, you may need to restart the syslog daemon for the changes to take effect.
  6. Check the application: Make sure that the application that is generating the log messages is configured to log messages to the correct file or socket. You can check the application configuration by looking at the application’s configuration files or by using the strace command to trace the application’s system calls.
  7. Check the firewall: Make sure that the firewall is not blocking the connection to the syslog daemon. You can check the firewall rules by using the iptables or ufw command.

Leave a Comment