System Log Error When Running Firestarter Configuration Program

System Log Error When Running Firestarter Configuration Program

Running latest Ubuntu ver. 11.04. Using Firestarter firewall configuration (ver.1.0.3). When Firestarter is run, an error message is returned, "Failed to open the system log. No event information will be available". Also same error msg. is returned in the "Events" tab within Firestater, "Error reading system log (null), file does not exist."

How is the system log opened/created/started to prevent this error msg??

2 Answers

Ubuntu 11.04 installs rsylogd rather than syslogd which Firestarter was expecting.

rsyslogd is configured using the file /etc/rsyslog.d/50-default.conf.

You can edit this file

gksu gedit /etc/rsyslog.d/50-default.conf

and change the lines commented out that create the relevant logfile

#*.=info;*.=notice;*.=warn;\
# auth,authpriv.none;\
# cron,daemon.none;\
# mail,news.none -/var/log/messages

to

*.=info;*.=notice;*.=warn;\
        auth,authpriv.none;\
        cron,daemon.none;\
        mail,news.none -/var/log/messages

and then restart rsyslog:

sudo service rsyslog restart

source

2

As an alternative to the other methdods posted about here, you can just put a symbolic link in /var/log that points messages to syslog:

cd /var/log
sudo ln -s syslog messages

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

David Miller
Author

David Miller

David Miller brings 15 years of experience in global economics, personal finance strategy, and market dynamics. He specializes in turning complex economic trends into actionable insights for everyday readers.