rsyslog won't start with upstart on chromebook

Bug #1390962 reported by Ferry Toth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rsyslog (Ubuntu)
New
Undecided
Unassigned

Bug Description

On utopic (14.10) I have the following probllem:
Each time I reboot rsyslogd is not running.

#lsb_release -rd
Description: Ubuntu 14.10
Release: 14.10
#uname -a
Linux chromium 3.17.2-031702-generic #201410301416 SMP Thu Oct 30 18:18:02 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
#apt-cache policy rsyslog
rsyslog:
  Geïnstalleerd: 7.4.4-1ubuntu11
  Kandidaat: 7.4.4-1ubuntu11
  Versietabel:
 *** 7.4.4-1ubuntu11 0
        500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status

When I do:
#sudo service syslog start

the system responds that the service is already running. However using:
#ps -ef | grep syslog

shows that there is no such procesa.

When doing:
#sudo service syslog restart

the (non-existing service) is stopped and started and runs normally.

Finally (after many frustrating hours) I found the following line in /var/log/upstart/rsyslog:
ERROR: Could not determine network interfaces, you must use a interfaces config line

 I suddenly realized old problems in the past getting smbd started before the network becomes available. Appearantly that is the case here as well. So I went ahead and changed /etc/init/rsyslog.conf (copied the line from /etc/init/smbd.conf):

#sudo servicestart on filesystem
start on (local-filesystems and net-device-up)

Now rsyslogd starts properly.

Note that a chromebook has no ethernet port, only wifi.

I have no idea if this is the optimal start on event.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.