*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I ran into this on a machine upgraded from Karmic to Lucid. The problem
was that the ifupdown package hadn't been upgraded (it was on 0.6.8nmu+1
IIRC) and the upstart init files for networking weren't in
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
@Mike Bianchi
I just wanted to thank you very much. In the last time I was struggling
hard with boot hangs on all our Ubuntu 10.04 Servers, and after I
followed your advice and commented out the console
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I also had this problem. But the bug was in the script I created to
automate the process of customization[1]. I don't remove the link
/sbin/initctl when exit from chroot as described [2]. I resolved my
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
This bug must be the worst I've come across in my 6-7 years with ubuntu.
Some services not starting is an absolute show stopper security issue that
must surely be treated with the utmost urgency.
--
Some
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
We've just been bitten by this, on a delivery of 20 machines to site; it
does seem to be fixed by #99, fortunately - I think it must be pretty
widespread, also happens on my mini-311c at home, which is
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
So has anyone seen it on a machine which is not a 32-bit install running a
generic (not generic-pae) kernel?
I have an amd64 install here with the same problem. So it's not
specific to 32-bit systems.
--
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I've upgraded about 20 machines from Ubuntu 8.04 to 10.04 and have only
seen this problem on one machine.
That was on a old Pentium 3 machine running a linux-generic kernel on
a 32-bit install. The other
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I'm seeing this issue as well. I don't see the unknown when running
runlevel, but several services aren't starting up automatically.
Any word on a fix for this?
--
Some services not started on boot,
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I should add to my previous comment that I've tried some of the
workarounds mentioned in this thread, including commenting out console
output in all /etc/init/*.conf files. This had no effect, and services
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
On Wed, Jun 30, 2010 at 07:16:47PM -, phireph0x wrote:
I should add to my previous comment that I've tried some of the
workarounds mentioned in this thread, including commenting out console
output in
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I try to PXE boot ubuntu 10.04,it shows runlevel is unknown
initctl list:
mountall-net stop/waiting
rc stop/waiting
rsyslog start/running
test stop/waiting
tty4 stop/waiting
udev start/running, process 4296
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
I found that the problem of runlevel Unknown refers to a problem with
/etc/network/interfaces look and if you can't find this file you maybe need to
install it using aptitude --install
*** This bug is a duplicate of bug 554172 ***
https://bugs.launchpad.net/bugs/554172
** This bug has been marked a duplicate of bug 554172
CUPS and other system services not starting at boot
--
Some services not started on boot, runlevel returns unknown
Finally happened after 10 days (1 boot per day btw).
corresponding syslog attached.
** Attachment added: syslog.fail.log
http://launchpadlibrarian.net/50576717/syslog.fail.log
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/554172?comments=all
--- This bug was initially classified as a CUPS bug, but it has been
moved to an Upstart bug.
It is very similar to this bug. I am posting a link here since there may
be more useful information there.
To summarize what I
My bug is also related/the same:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/584855
There is also some information here.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member
Adding additional confirmation.
Clean Lucid 10.04 Desktop 32-bit install
2.6.32-22-generic
All updates applied
I noticed proftpd and cupsd not starting up on some system restarts. I
did over 50 restarts and there are two absolutely consistent results:
a. On the restarts when proftpd and cupsd
I have one more reproduction.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I also have this problem. Thanks Mike for post #81 and #83. Will try.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I am also still having the problem after commenting all instances of
console output in /etc/init/*. Replacing IFACE=lo by IFACE=eth0 in
/etc/init/rc-sysinit.conf (as suggested in a few posts) did not fix it
either. The only way I can get the system to display the correct
runlevel and have my
So many reproductions, marking this as confirmed.
** Changed in: upstart (Ubuntu)
Status: Incomplete = Confirmed
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Well I added changes for #54, #73 and #79 but no joy - still get
runlevel unknown
I have intel i3 machine with 4GB.
I normally dont complain about free software but the ubuntu quality
control sucks. The upgrade from 8 to 9 was a disaster, the upgrade from
9 to 10 was a disaster so I did a fresh
boot.log and syslog
** Attachment added: logs.tar.gz
http://launchpadlibrarian.net/50181806/logs.tar.gz
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If I follow the instructions in #50
initctl emit filesystem [have to C-C to end]
initctl emit net-device-up IFACE=lo [corrected typo]
I then get runlevel N 2
What a mess - sigg
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You
On Wed, Jun 09, 2010 at 01:06:20PM -, Olivier Debon wrote:
What I could diff from syslog between a successful startup and a no runlevel
situation is that only the 2 following messages are missing in the failure
case:
For many of us, the solution is already in this Bug report. Namely:
Happens to me as well from time to time, really unpredictable. But failure is
related to console existence. This also sometimes make X fail (NVidia card
here).
What I could diff from syslog between a successful startup and a no runlevel
situation is that only the 2 following messages are
I have this problem too and I notice that every time the init scripts
fails I get this lines in the dmesg:
[ 0.00] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 0.00] Fast TSC calibration failed
[ 0.00] TSC: Unable to calibrate against PIT
[ 0.00] TSC: using
On Wed, Jun 09, 2010 at 01:06:20PM -, Olivier Debon wrote:
What I could diff from syslog between a successful startup and a no runlevel
situation is that only the 2 following messages are missing in the failure
case:
For many of us, the solution is already in this Bug report. Namely:
On Fri, Jun 04, 2010 at 02:29:49AM -, Francisco.X wrote:
:
In the old init.d system, it was easy for me to add something like an
echo or syslog message to any script to know when it was being executed.
How can I do the same so I can know if /etc/init/rc-sysinit.conf is even
run
Why have the developer(s) gone totally silent on this issue? Surely
there is enough data in this report now to understand the problem(s) and
issue (a) fix(es), yes?
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
Sigh. I commented out the console output line in the four files in
/etc/init that had it:
/etc/init: grep console output *
mountall.conf:#console output
rc.conf:#console output
rc-sysinit.conf:#console output
ufw.conf:#console output
I have rebooted three times in a row and every time it's the
On Thu, Jun 03, 2010 at 02:36:14PM -, Francisco.X wrote:
Sigh. I commented out the console output line in the four files in
/etc/init that had it:
/etc/init: grep console output *
mountall.conf:#console output
rc.conf:#console output
rc-sysinit.conf:#console output
ufw.conf:#console
/var/log/boot.log:
init: ureadahead-other main process (635) terminated with status 4
There are a number of init messages in /var/log/syslog from my last
reboot, related to ssh respawning too fast. I'll double check the
differences between the default ssh config files and my edited version
to
On Thu, Jun 03, 2010 at 03:32:25PM -, Francisco.X wrote:
/var/log/boot.log:
init: ureadahead-other main process (635) terminated with status 4
There are a number of init messages in /var/log/syslog from my last
reboot, related to ssh respawning too fast. I'll double check the
I have been reading about ureadahead today as well. I was already
thinking of trying to disable it to see if it helps, but I'll try the
reboot with the tweaked rc-sysinit.conf first, so if things work I at
least will know which of the two variables made the difference. Thanks.
--
Some services
No luck. I've tried the suggested rc-sysinit.conf modifications. Tried
other modifications suggested elsewhere. Tried disabling ureadahead.
Tried several other things and I still get the same thing on every
reboot. I haven't tried unplugging all the USB and firewire drives
and/or the second
I'm attaching a syslog from one of the earlier bad bootups. The
/var/log/boot.log file has been empty since I disabled ureadahead.
** Attachment added: syslog of a boot that ended in unknown runlevel
http://launchpadlibrarian.net/49642897/KEEP.syslog.badboot
--
Some services not started on
On Tue, Jun 01, 2010 at 03:49:30PM -, Michael Goetze wrote:
Looking at the ttyX jobs as well as xinetd (a service started by a legacy
initscript), I've so far seen all of the following combinations:
- None started
- xinetd started, but none of the ttys
- both xinetd and all the ttys
Thanks Mike, got so far reliable boots with your workaround! By forcing
ureadahead to reprofile on system boot I was somehow avoiding that race
condition.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification
Same problem here. Runlevel unknown, failed to start most services.
/var/log/boot.log:
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
/dev/sdb1: clean, 151983/499968 files, 714882/1999872 blocks
/dev/sdb3: clean, 1183/29900800 files, 101518470/119596544 blocks
init:
Thanks Mike, I can verify that your workaround is working. This was a
quite annoying bug the last few weeks.
I had the same problem (runlevel unknown, cups not starting) on one of
our office computers. Commenting out console output in all the files
in /etc/init apparently solved the problem for
Looking at the ttyX jobs as well as xinetd (a service started by a legacy
initscript), I've so far seen all of the following combinations:
- None started
- xinetd started, but none of the ttys
- both xinetd and all the ttys started
If this is caused by a race condition, then network-manager is
Thanks for your debugging work Mike, but I've now replaced my rc-
sysinit.conf with the one you provided and I'm still having issues with
services like apache not starting.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
On Fri, May 28, 2010 at 10:08:43PM -, Ash wrote:
Thanks for your debugging work Mike, but I've now replaced my rc-
sysinit.conf with the one you provided and I'm still having issues with
services like apache not starting.
Note that I had to comment out the console output line in rc.conf
Thanks for the clarification Mike, now that I've commented those out
things seem to be working consistently :)
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which
I don't know if this is related or not, since upgrading to 10.04 (64bit
server) I have struggled with the system booting with the runlevel
unknown. My server does not have a console as I don't have a video
card and it doesn't have any serial ports. When necessary I connect to
the server via a
On Fri, May 28, 2010 at 06:22:46PM -, Eric Kennedy wrote:
:
My server does not have a console as I don't have a video card ...
I wonder if the concept of /dev/console is tied to the presence of a video
card, or is it more conceptual?
Should a machine without video have a /dev/console
Thanks Mike, I'm testing your rc-sysinit.conf now and so far I've had
reliable boots.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have found a significant difference between the syslogs of an N 2 boot and
an unknown boot.
See syslog_N2 and syslog_unknown, attached. I find using diffuse to look at
them side-by-side very useful.
I've changed times and process numbers to nn:nn:nn and nnn to make taking diffs
easier.
My final /etc/init/rc-sysinit.conf file is attached.
** Attachment added: rc-sysinit.conf
http://launchpadlibrarian.net/49136524/rc-sysinit.conf
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because
I failed to attach syslog_N2 and syslog_unknown in comment #54.
Here they are.
** Attachment added: syslog_N2
http://launchpadlibrarian.net/49137470/syslog_N2
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
I failed to attach syslog_N2 and syslog_unknown in comment #54.
Here they are.
** Attachment added: syslog_unknown
http://launchpadlibrarian.net/49137473/syslog_unknown
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
/etc/init/rc.conf suffers from the same console output problem as
/etc/init/rc-sysinit.conf,
namely that if it looses the race with /dev/console being writable, then it
fails.
I have submitted Bug Report 585915 documenting that fact.
I have also submitted Bug Report 585908: cross-comment
More that I think about it, the more I think there should be an event when
/dev/console becomes available,
and console output should imply start on /dev/console.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
I think I can give some more light on the subject. If you are having the
same problem as me then it is an intermittent problem that affects ALL
services that are started through rc-sysinit, either all starts or none.
The reason is that rc-sysinit is started when the lo network device is
started,
Kent's analysis and repair (comment #42) sounded right,
and I thought it fixed my machine.
I got runlevel N 2 and all my /etc/rc2.d files seem to be started.
The first time.
But on reboot, I was back to runlevel unknown .
sudo telinit 2 seems to move things forward, but ...
--
Some
Obviously my earlier comment (#39) about using static network configurations
was nonsense. I just got lucky with a few boots in a row.
Furthermore I'm using a minimal installation of lucid and don't have
network-manager installed at all, so it is unlikely to be the culprit.
--
Some services
I am _totally_ confused by the upstart event.
I see startup on filesystem and net-device-up IFACE=lo in
/etc/inti/rc-sysinit.conf
and think I understand that filesystem and net-device-up are
events,
but I have not been able to find _anything_ that would explain where they come
On Tue, 2010-05-25 at 16:51 +, Mike Bianchi wrote:
Where does net-device-up come from?
How does IFACE get set to lo?
Check out /etc/network/if-up.d/upstart.
initctl emit is (one place) where events come from.
--
Some services not started on boot, runlevel returns unknown
The machine expressing this bug is running an AMD 4-core processor.
I see the bug with 4 or 3 cores running.
I'm wondering if all the others seeing this bug are running multi-core machines.
How say you all?
--
Some services not started on boot, runlevel returns unknown
I see this intermittently and have a dual-core machine (AMD Athlon 64
X2 Dual Core Processor 3600+)
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Where does net-device-up come from?
How does IFACE get set to lo?
Check out /etc/network/if-up.d/upstart.
initctl emit is (one place) where events come from.
OK. Now the question is, where do /etc/network/if-up.d/upstart and
/etc/network/if-down.d/upstart get called from?
find /etc
In the mean time, I find that if I issue
sudo initctl emit filesystem
((initctl never exits, so I have to Ctl-C to make it die.))
sudo initclt emit net-device-up IFACE=lo
Then the boot completes and I get runlevel N 2 with all the goodies.
I have 'init=/sbin/init --verbose' on
Ben Lings -- can you turn one of the CPUs off, so the machine acts as a
single-core processor?
Does it change your boot reliability?
My AMD Phenom II X4 955 only allows me 3 cores (in two configurations:
0,1,2 or 0,1,3) or 4 cores (!?).
--
Some services not started on boot, runlevel returns
On Tue, 2010-05-25 at 18:00 +, Mike Bianchi wrote:
OK. Now the question is, where do /etc/network/if-up.d/upstart and
/etc/network/if-down.d/upstart get called from?
They are called from ifup/ifdown.
But this is all pretty basic Debian/Ubuntu network plumbing and not
really
In comment #50 I ask if the filesystem and net-device-up IFACE=lo events
are not issued or
issued when /sbin/init doesn't yet know about /etc/init/rc-sysinit.conf .
I now see, in a runlevel unknown boot _AND_ a runlevel N 2 boot that each
/var/log/boot.log records that both events happen _and_
I reconfigured my network interface to use static settings and seem to
get reliable boots now.
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
All my network interfaces were configured static by default, still I get the
'runlevel unknown'. There might be different problems around, each resulting in
a 'runlevel unknown'.
As I posted already, for it looks like reinstalling of the reloveconf-package
each time really helps. Haven't had a
After fault-finding for a couple of days I came across this thread, and
realised I was experiencing the same problem. My system was upgraded from
Koala, but I'm sure the problem did not occur until some time after the upgrade
(ie after an update). I've done a quick'n'dirty fix that fixes it by
Problem occured after 10.04 upgrade...
The details:
$ cat /var/log/boot.log
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
/dev/mapper/Odin-root: clean, 113846/29908992 files, 3292621/119608320 blocks
/dev/sda5: clean, 33/124496 files, 32040/248976 blocks
init: ureadahead-other
First boot of the morning: apache2 not started
lvanb...@navets:~$ runlevel
unknown
lvanb...@navets:~$ cat /var/log/boot.log
fsck from util-linux-ng 2.17.2
/dev/sda1: clean, 182097/915712 files, 980283/3661824 blocks
fsck from util-linux-ng 2.17.2
/dev/sda6: clean, 85816/1917600 files,
On Mon, 2010-05-17 at 17:41 +, Oscar Forsström wrote:
runlevel
N 2
Was this a working boot?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because
No, it wasn't. For me it's often like this.
1. Non-working boot with runlevel N 2.
2. Reboot. Non-working boot. runlevel unknown.
3. Reboot. Non-working boot. runlevel unknown.
4. Reboot. Working boot. Runlevel N 2
--
Some services not started on boot, runlevel returns unknown
** Summary changed:
- Upstart not starting jobs on boot
+ Some services not started on boot, runlevel returns unknown
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs,
initctl list attachment
from an AMD 64-bit quad core, running 3 cores
** Attachment added: initctl_list
http://launchpadlibrarian.net/48606312/initctl_list
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
I'm moving my participation in the runlevel unknown problem to here
from Bug #581291.
See that bug for my partial success with using init='/bin/sbin
--verbose' .
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug
cat /var/log/boot.log
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
udevd[345]: BUS= will be removed in a future udev version, please use
SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device,
in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:9
runlevel
N 2
initctl list
alsa-mixer-save stop/waiting
avahi-daemon start/running, process 753
mountall-net stop/waiting
nmbd start/running, process 995
rc stop/waiting
rsyslog start/running, process 697
tty4 start/running, process 794
udev start/running, process 353
upstart-udev-bridge
And now, after another restart, I get: runlevel: unknown
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Runlevel unknown, initctl see attachement.
** Attachment added: initctl.txt
http://launchpadlibrarian.net/48618329/initctl.txt
--
Some services not started on boot, runlevel returns unknown
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of
80 matches
Mail list logo
