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

If you are trying to use the syslogd daemon to log messages on a Linux system, but nothing is getting logged when you use the /dev/log or /jail/apache/dev/log sockets, there are a few things you can try to troubleshoot the issue:

1. Check if the syslogd daemon is running:

ps aux | grep syslogd

This will show you if the syslogd daemon is running on your system. If it is not running, you will need to start it.

2. Check if the /dev/log socket exists:

ls -l /dev/log

This will show you if the /dev/log socket exists on your system. If it does not exist, you will need to create it.

3. Check the permissions on the /dev/log socket:

ls -l /dev/log

The /dev/log socket should have permissions of srw-rw----, which allows the syslogd daemon to read and write to the socket. If the permissions are not set correctly, you will need to change them.

4. Check if the /jail/apache/dev/log socket exists:

ls -l /jail/apache/dev/log

This will show you if the /jail/apache/dev/log socket exists on your system. If it does not exist, you will need to create it.

5. Check the permissions on the /jail/apache/dev/log socket:

ls -l /jail/apache/dev/log

The /jail/apache/dev/log socket should have permissions that allow the Apache web server to read and write to the socket. If the permissions are not set correctly, you will need to change them.

6. Check the configuration of the syslogd daemon:

grep -v "^#" /etc/syslog.conf

This will show you the current configuration of the syslogd daemon. Make sure that the configuration includes a line that directs messages to the /dev/log or /jail/apache/dev/log sockets.

7. Restart the syslogd daemon:

sudo service syslog restart

This will stop and start the syslogd daemon, which may help resolve any issues with the daemon.

By following these steps, you should be able to troubleshoot any issues that are preventing messages from being logged using the /dev/log and /jail/apache/dev/log sockets.