Public bug reported:

Binary package hint: sysvinit

Hi Guys,

I have a problem with Lucid Lynx after upgrading one of our servers
today.

Other servers have had a couple of problems, but unrelated to this one.

The server boots fine and starts SSH, but various services are not
started (sysklogd, cron, heartbeat, DRBD, our startup scripts at various
rc run-levels).

After some review, I found that /etc/init.d/rc S is running, and that it
is stuck on /etc/rcS.d/S90console-screen.sh

I have been able to reproduce the problem on every reboot.

This is a server, so there is no graphical interface involved, and we
connect over SSH exclusively.

If I kill the rc process, most of the services start up (run-level 2
processes at least).

As a workaround, I've added "exit" at the top of the S90console-
screen.sh script, and now after a reboot everything completes correctly.

Unfortunately, if I run that script myself, it completes without
hanging, so I can't track down where the problem is occurring manually.
Also, since sysklogd is either not started, or gets killed at some
point, I can't get any useful logs from syslog.

Version: 2.6.32-22-generic-pae
Upgraded from 2.6.31-19-generic-pae using do-release-upgrade
Server: PowerEdge 2650

Sorry if this is being reported in the wrong package.  It seemed to be
related to initscripts, and LaunchPad has filed that under sysvinit.
Hopefully that's correct.

Best Regards,
Neale

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: initscripts 2.87dsf-4ubuntu17
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
Architecture: i386
Date: Fri May 14 19:28:24 2010
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: sysvinit

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


** Tags: apport-bug i386 lucid

-- 
Services not starting after reboot, due to hung rc script S90console-screen.sh
https://bugs.launchpad.net/bugs/580416
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to