Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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??

share|improve this question
up vote 12 down vote accepted

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

# auth,authpriv.none;\
# cron,daemon.none;\
# mail,news.none -/var/log/messages


        mail,news.none -/var/log/messages

and then restart rsyslog:

sudo service rsyslog restart


share|improve this answer
Success. Thanks for your assistance. – wam Jul 12 '11 at 20:28
@fossfreedom, Thank you. I have some problem with /ets/rsyslog.d/50-default.conf, when i try to save the edits in, it give me error: Error writing /etc/rsyslog.d/50-default.conf: Read-only file system – shgnInc Feb 13 '14 at 8:20
@shgnInc - a read-only file system is symptomatic of other issues - usually your filesystem needs to be fsck'd. – fossfreedom Feb 13 '14 at 8:59

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
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.