I have a problem with my Ubuntu server installation :/ The server runs several services, e.g. postfix, dovecot (as a mailserver), apache2, mysqld, elasticsearch. Normally on startup, these services should start automatically, unhappily they don't do it anymore after upgrading to Ubuntu 14.04.1 LTS from 12.04.

I have no wide knowledge of ubuntu startup and services, so i don't know what to do. I have checked, if the runlevel is correct after startup (yes it is, N 2), but that's all i did.

What i find out is, that it seems, that only upstart services (which has a config in /etc/init/) starting automatically (e.g. mysqld, dovecot). Services which using sysvinit (/etc/init.d) doesn't start (e.g. postfix, apache2).

I can start the services manually via an ssh (upstart service) connection without any problems, so i don't think, that's a problem of the services itself.

Hope someone can help me :(

Thanks in advance.



dmesg: http://pastebin.com/uwrwhVmT

syslog: http://pastebin.com/8fczRUE1

boot.log: empty

kern: pastebin.com/TA9GiG95


I have read and looked into it a little bit more and it seems, that all services, which can be started via upstart, are starting, while services using sysvinit instead doesn't start anymore.

rc-sysvinit.conf script: pastebin.com/77sMbBy0


For a test i moved apache2 to rcS, too, and it starts automatically. I did this, because i saw the following line in rc-sysinit.conf:

[ -n "${FROM_SINGLE_USER_MODE}" ] || /etc/init.d/rcS

I checked the entiere file against 14.04 source, but can't find any difference. It's frustraiting, i can't be a solution to move all required services to rcS?! :)


Now i had a tip from rbasak in #ubuntu-server irc, and followed the steps of the startup.

/etc/init/rc-sysinit.conf successfully calls (tracked with logger) /etc/init.d/rcS which executes /etc/init.d/rc S (the run level S i have tracked with logger). Aftter this, /etc/init/rc-sysinit.conf executes telinit "${DEFAULT_RUNLEVEL}" (DEFAULT_RUNLEVEL is 2, tracked with logger), but /etc/init.d/rc isn't executed after this (it should run and the logger statement should log the runlevel 2). Any suggestions?

closed as off-topic by Seth Oct 15 '14 at 14:28

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This describes a problem that can't be reproduced that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Seth
If this question can be reworded to fit the rules in the help center, please edit the question.

  • You should search errors in dmesg, syslog, boot.log and kern.log in /var/log folder, if you want post this file on pastebin.com and update your question with link. – Lety Oct 12 '14 at 15:30
  • Thanks for the fast comment. I added the log files to pastebin and edited my question. I can't find anything :/ – Thor500 Oct 12 '14 at 16:02
  • Did you modify /etc/rsyslog.conf? There are errors about Bad file descriptor If not, could be related to this bug. Could you reboot your server and post /var/log/syslog immediately after boot ends? – Lety Oct 12 '14 at 19:40
  • Thanks again for your answer. I forgot to say: The logs are taken directly after a reboot (i cleaned the existing logs after taking a backup and copied the complete logs to the pastebin). Should i take new logs? And rsyslog.conf i haven't changed. Hope that helps you to help me, if you need more information, please say :) – Thor500 Oct 12 '14 at 20:14
  • Okey, log files are strange, may be due to problem in /etc/rsyslog.conf, could you post it? – Lety Oct 12 '14 at 21:40

After several tries to fix the problem or find out, what the problem is, i have now reinstalled with the actual Ubuntu 14.04 image and all is working now. Unhappily i can't say, what the problem was :(

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