touch-packages team mailing list archive

[Ferry Toth <ftoth@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: rsyslog (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1390962

Title:
  rsyslog won't start with upstart on chromebook

Status in “rsyslog” package in Ubuntu:
  New

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1390962/+subscriptions