[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 /etc/init (which meant that lo was never started and so rc-sysvinit was never started). Installing Lucid's ifupdown package fixed the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543506 Title: Some services not started on boot, runlevel returns "unknown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 output" in /etc/init/*.conf, our servers are booting normally. Finally! I hope I won't get into any problems with that thing called "upstart" in future any more... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543506 Title: Some services not started on boot, runlevel returns "unknown" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 problem by removing this link. [1] - https://help.ubuntu.com/community/LiveCDCustomization [2] - https://help.ubuntu.com/community/LiveCDCustomization#Cleanup -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 up2date with lucid-updates. Must give one hell-of-a-bad user experience to the user-base though! -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 machines which do not show this problem were either running a 64-bit install or a "linux-generic-pae" kernel. So has anyone seen it on a machine which is not a 32-bit install running a "generic" (not "generic-pae") kernel? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 all /etc/init/*.conf files. This had no effect, and services > such as lighttpd aren't automatically starting that should be. You said "some of the workarounds". I found that -ALL THREE- specific workarounds spelled out in https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/81 were necessary for success, at least in my circumstance. Did you try that specific combination? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 such as lighttpd aren't automatically starting that should be. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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, 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 upstart-udev-bridge start/running, process 4291 console-setup stop/waiting hwclock-save stop/waiting plymouth-log stop/waiting tty5 stop/waiting plymouth stop/waiting ssh start/running, process 4298 control-alt-delete stop/waiting hwclock stop/waiting network-manager stop/waiting module-init-tools stop/waiting cron stop/waiting mountall stop/waiting plymouth-stop stop/waiting rcS stop/waiting mounted-varrun stop/waiting rc-sysinit stop/waiting tty2 stop/waiting udevtrigger stop/waiting mounted-dev stop/waiting tty3 stop/waiting udev-finish stop/waiting hostname stop/waiting mountall-reboot stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (lo) start/running network-interface (eth0) start/running network-interface (eth1) start/running plymouth-splash stop/waiting tty1 stop/waiting udevmonitor stop/waiting dmesg stop/waiting network-interface-security start/running procps stop/waiting tty6 stop/waiting ttyS0 stop/waiting if I change 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 upstart-udev-bridge start/running, process 4291 console-setup stop/waiting hwclock-save stop/waiting plymouth-log stop/waiting tty5 stop/waiting plymouth stop/waiting ssh start/running, process 4298 control-alt-delete stop/waiting hwclock stop/waiting network-manager stop/waiting module-init-tools stop/waiting cron stop/waiting mountall stop/waiting plymouth-stop stop/waiting rcS stop/waiting mounted-varrun stop/waiting rc-sysinit stop/waiting tty2 stop/waiting udevtrigger stop/waiting mounted-dev stop/waiting tty3 stop/waiting udev-finish stop/waiting hostname stop/waiting mountall-reboot stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (lo) start/running network-interface (eth0) start/running network-interface (eth1) start/running plymouth-splash stop/waiting tty1 stop/waiting udevmonitor stop/waiting dmesg stop/waiting network-interface-security start/running procps stop/waiting tty6 stop/waiting ttyS0 stop/waiting I do a little change in /etc/init/rc-sysinit.conf from start on filesystem and net-device-up IFACE=lo to start on filesystem runlevel is N 2 is there any final solution for this issue? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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 ifupdown_0.6.8ubuntu29_amd64.deb" to force to rewrite and create mising files download from http://packages.ubuntu.com/es/lucid/amd64/ifupdown/download this file define eth0 and lo interfaces. excuse for my english. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
*** 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" 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 start up successfully the output of the runlevel command looks normal i.e. gra...@gt-desktop:~$ runlevel N 2 b. On the restarts when proftpd and cupsd do not start up the output of the runlevel command is not normal, it gives this: gra...@gt-desktop:~$ runlevel unknown The services can be started manually fine after startup in situation b. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 observe in both bugs: -services sometimes do not start on boot. irqbalance, winbindd, cupsd are the major ones. runlevel command will report 'unknown' -on some boots, all services will start ok. runlevel command will report 'N 2' -if you think you have it fixed, boot 10 times at least to see if you can get it to fail. -if you have a bad boot, 'sudo start rc-sysinit' seems to start the services that did not start. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: 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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 services started correctly is by removing completely the " and net-device-up IFACE=lo" condition from "start" in /etc/init/rc-sysinit.conf (ie: start on filesystem and started rsyslog) and commenting all instances of "console output". Probably not a good idea but it works for now. Hope an adequate fix is coming soon. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 install and now just when I thought I had my system working again I have this problem. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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: From comment #54 Comment out "console output" in all /etc/init/*.conf files that have it. From comment #73 Add "started rsyslog" to the "start on" stanza in /etc/init/rc-sysinit.conf: start on ( filesystem and started rsyslog and net-device-up IFACE=lo ) From comment #79 Add "init='/sbin/init --verbose'" to the linux boot line in grub. Folks: Have any of you found this insufficient? Was there anything else you had to do to achieve reliable boots? I can imagine that items in /etc/init.d/* and/or /etc/rc2.d/* that attempt to write to /dev/console could get caught in the race condition between /dev/console becoming writable and them running. To my mind there should be an event when /dev/console _is_ writable, but I don't know if one exists or how to make it happen. -- Mike Bianchi Foveal Systems 973 822-2085 mbian...@foveal.com http://www.AutoAuditorium.com http://www.FovealMounts.com -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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: From comment #54 Comment out "console output" in all /etc/init/*.conf files that have it. From comment #73 Add "started rsyslog" to the "start on" stanza in /etc/init/rc-sysinit.conf: start on ( filesystem and started rsyslog and net-device-up IFACE=lo ) From comment #79 Add "init='/sbin/init --verbose'" to the linux boot line in grub. Folks: Have any of you found this insufficient? Was there anything else you had to do to achieve reliable boots? I can imagine that items in /etc/init.d/* and/or /etc/rc2.d/* that attempt to write to /dev/console could get caught in the race condition between /dev/console becoming writable and them running. To my mind there should be an event when /dev/console _is_ writable, but I don't know if one exists or how to make it happen. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 HPET reference calibration [ 0.00] Detected 1994.959 MHz processor. [ 0.514332] tty tty28: hash matches [ 0.849208] ATL1E :09:00.0: enabling device ( -> 0003) [ 0.849490] ATL1E :09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 0.849689] ATL1E :09:00.0: setting latency timer to 64 [ 46.072567] ov519: Can't determine sensor slave IDs [ 46.072570] ov519: OV519 Config failed [ 46.072584] ov519: probe of 2-4.4:1.0 failed with error -16 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 missing in the failure case: - lp: driver loaded but no devices found - Console: switching to colour frame buffer device 80x30 Sure that lp driver has nothing to do here. I'll add suggested verbose init option above and come back with log if that happens again. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 during boot? See Bug #581291. To get entries in /var/log/boot.lob I've been running with init='/sbin/init --verbose' added to the linux /boot/vmlinuz/... line in /boot/grub/grub.cfg . Modifying /etc/default/grub is one way to do that. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 network card, but since those are the main functions of this particular computer it wouldn't be a satisfactory solution for me anyway. Wiping the OS partition and reinstalling 08.04 seems like the most pain free way to go. 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 during boot? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 > differences between the default ssh config files and my edited version > to see if there's anything there. > > I have made the change to rc-sysinit.conf and will try rebooting tonight > and see how it goes. Thank you. There seems to be some sort of issue with ureadahead : https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/501715 You might want to read that bug and see if there is a related issue there. (I know nothing about it, except that we have seen it mentioned in comments #28 and #69). -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
/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 see if there's anything there. I have made the change to rc-sysinit.conf and will try rebooting tonight and see how it goes. Thank you. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 output > > I have rebooted three times in a row and every time it's the same > runlevel unknown. So that wasn't a fix. > : Look at /var/log/boot.log and /var/log/syslog after a runlevel unknown boot and see if there are any error messages labeled "init:" Also, my fix included making /etc/init/rc-sysinit.conf sensitive to rsyslog . start on ( filesystem and started rsyslog and net-device-up IFACE=lo ) Please try that. If it still fails, attach /var/log/boot.log and /var/log/syslog to this Bug. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 same runlevel unknown. So that wasn't a fix. Other bits of info (in case they help): - this machine has several firewire and usb hard drives attached. the OS is on an internal SATA drive. - this machine has two network interfaces, one is static IP, the other dynamic (DSL - this is my firewall) I just installed the OS a few days ago and I don't think I've had a successful boot even once. I'll give this a few more days before I just blow away 10.04 and reinstall 08.04 which took longer to boot but was rock solid. In the meantime, I could do some tests on Saturday and try to dig up more clues. It does appear my case is 100% repeatable at the moment. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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: ureadahead-other main process (625) terminated with status 4 This is on a single core Celeron, fresh 10.04 install + apt-get upgrade. Posting in response to Mike's question #47 wondering if it only happens on multi-core machines. I've commented out the "console output" in /etc/init/*.conf files and will reboot when I am able to. Hopefully that will help until a proper fix is rolled out. Any updates from the devs on a real fix? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 started > If this is caused by a race condition, then network-manager is not involved, > as that is not installed on my servers. Look at earlier comments in this Bug about commenting out "console output" in /etc/init/*.conf files. -- Mike Bianchi Foveal Systems 973 822-2085 mbian...@foveal.com http://www.AutoAuditorium.com http://www.FovealMounts.com -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 not involved, as that is not installed on my servers. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 me. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 also to get my boots reliable, and the evidence is that it makes sense to do it in mountall.conf and ufw.conf . -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 that is linked to /dev/null ? Or to /var/log/console ? > Based on this bug report I thought it might have something to do with > not having a console. In response, I commented out all "console output" > statements in upstart scripts. For me these were in the following > scripts: mountall.conf, rc.conf, rc-sysinit.conf, ufw.conf. How did I miss the mountall.conf and ufw.conf (!). -- Mike Bianchi Foveal Systems 973 822-2085 mbian...@foveal.com http://www.AutoAuditorium.com http://www.FovealMounts.com -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 USB serial port. When I run "initctl list" many upstart scripts are in a stop/waiting status including "mountall". The system does boot, however, the runlevel is "unknown" and many services are not started. Based on this bug report I thought it might have something to do with not having a console. In response, I commented out all "console output" statements in upstart scripts. For me these were in the following scripts: mountall.conf, rc.conf, rc-sysinit.conf, ufw.conf. This seems to have resolved the problem for me and the system is now booting properly. FYI, I did not use the updated rc-sysinit.conf script included with this bug report. As I said I don't know it this is related or not but hoped that it might provide another data point to help understand the issue. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
/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 events and *.conf files" I am also reattaching rc-sysinit.conf and marking it as a solution to this bug. ** Attachment added: "modified rc-sysinit.conf fixes bug 543506" http://launchpadlibrarian.net/49145771/rc-sysinit.conf -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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. Start at line 702 in syslog_N2 (S2 below) and syslog_unknown (SU below). In the SU we see "... init: rpc_pipefs post-stop process (821)" In the S2 log, we don't see an "init:" entry until line 741, and it is "... init: rsyslog state changed from post-start to running" In fact we don't see an "init:" line for rsyslog state change in SU! And rsyslog is the last state changes we see in /var/log/boot.log. Is that the race condition? To find out, I added ... and started rsyslog ... to the "start on" stanza. The syslog said: : : May 26 09:37:42 autoaud-broad1 kernel: [0.901105] ACPI: Power Button [PWRF] May 26 09:37:42 autoaud-broad1 init: Failed to spawn rc-sysinit main process: unable to open console: Input/output error May 26 09:37:42 autoaud-broad1 init: rc-sysinit goal changed from start to stop May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from spawned to stopping May 26 09:37:42 autoaud-broad1 init: Handling stopping event May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from stopping to killed May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from killed to post-stop May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from post-stop to waiting May 26 09:37:42 autoaud-broad1 init: Handling stopped event May 26 09:37:42 autoaud-broad1 init: Handling net-device-up/failed event May 26 09:37:42 autoaud-broad1 init: Handling started/failed event : : ((more experimentation attempting to detect the presence of /dev/console)) I commented out the "console output" stanza in /etc/init/rc- sysinit.conf and I seem to have a reliable boot. I suspect the race condition was with whatever makes /dev/console writable. Suggestion: failure of the console stanza should cause an error message, not stop the *.conf file. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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_ the rc-sysinit state goes from "waiting" to "starting". Both boot files are the same length: 730 lines. >From examining the boot.log files I think that, although the order is >different, all the same activities are accomplished before the filesystem event is asserted. The end of the boot.log file, in either case, reads: init: rpc_pipefs goal changed from stop to start init: rpc_pipefs state changed from waiting to starting init: Handling starting event init: rpc_pipefs state changed from starting to pre-start init: rpc_pipefs pre-start process (835) init: Handling filesystem event <<< init: rsyslog goal changed from stop to start init: rsyslog state changed from waiting to starting init: plymouth-log goal changed from stop to start init: plymouth-log state changed from waiting to starting init: ssh goal changed from stop to start init: ssh state changed from waiting to starting init: rc-sysinit goal changed from stop to start init: rc-sysinit state changed from waiting to starting <<< init: Handling starting event init: rsyslog state changed from starting to pre-start init: rsyslog state changed from pre-start to spawned Next stop, pulling apart the syslogs. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 appropriate for this bug I think. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 "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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 the linux line that I am booting, so I see log entries about plymouth-log changing goals and state when I "emit filesystem". Then, when I "emit net-device-up IFACE=lo", I see lots of things starting, I've attached the syslog with blank lines inserted where the first and second "initctl emit ..." commands were run. I think this demonstrates that the events "filesystem" and "net-device-up IFACE=lo" EITHER are not being issued OR are being issued when the /etc/init/rc-sysinit.conf file has not yet been read by /sbin/init . ** Attachment added: "syslog" http://launchpadlibrarian.net/49092522/syslog -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
> > 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 -type f | xargs grep '\' 2>/dev/null does not find anything by /lib/init/upstart-job and that does not appear to have a path back to /etc/network/if-up.d/upstart -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: 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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: 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" 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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" 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 from. The /etc/init/mountall,conf file has a line that reads "emits filesystem" but I strongly doubt that it's presence causes that event to be asserted just because the file has been read. And " grep net-device /etc/init/* " only finds net-device-up as an event in the " start on " lines in /etc/init/mountall.conf /etc/init/protmap.conf /etc/init/rc-sysinit.conf Where does net-device-up come from? How does IFACE get set to "lo"? Is there documentation I'm missing? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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, se bug 543506 for a related problem, and now upstart is sometimes not getting the event that it has happened. Steve Langasek noted that NetworkManager is starting "lo" if it is not already started but not notifying upstart. (https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/461725/comments/18) So now we have two entities that will start "lo" /etc/init/network- manager.conf and /etc/init/networking and their starting order is not defined causing a race condition. If networking is started before network-manager then it works otherwise not. Three options exist: 1. correct NetworkManager so that it is notifying upstart 2. set NetworkManager to wait for networking. 3. both I have personaly opted for #2 and changed /etc/init/network-manager.conf to contain: start on (local-filesystems and started dbus and started networking) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 having upstart run a "telinit 2" 90 seconds after booting (details below) - so it appears that init never sees the entry into run level 2 (and its not in utmp?) and so doesnt fire off the relevant jobs. In my case, atd (from upstart) and cups (from System-V rc2.d) were failing (as well as others). Here's some output which shows what's happening: $ runlevel unknown sfra...@sierra:~$ od -x /var/run/utmp 000 0007 033a 7474 3779 020 040 303a 6673 6172 060 6573 0072 100 303a 120 * 520 55c8 4bf7 7fd2 0008 540 * 600 0007 0568 7470 2f73 0030 620 640 302f 6673 6172 660 6573 0072 700 303a 302e 720 * 0001320 55d5 4bf7 4f89 0005 0001340 * 0001400 sfra...@sierra:~$ ps ax|egrep "atd|cups" 1415 pts/0S+ 0:00 egrep atd|cups sfra...@sierra:~$ initctl list|egrep "atd|rc" rc stop/waiting atd stop/waiting .wait the 90 secondsthen re-check $ runlevel N 2 sfra...@sierra:~$ od -x /var/run/utmp 000 0007 033a 7474 3779 020 040 303a 6673 6172 060 6573 0072 100 303a 120 * 520 55c8 4bf7 7fd2 0008 540 * 600 0007 0568 7470 2f73 0030 620 640 302f 6673 6172 660 6573 0072 700 303a 302e 720 * 0001320 55d5 4bf7 4f89 0005 0001340 * 0001400 0002 007e 0001420 0001440 7e7e 6572 6f62 0001460 746f 0001500 2e32 2e36 0001520 3233 322d 2d32 6567 656e 6972 0063 0001540 * 0002120 5602 4bf7 4dd9 0003 0002140 * 0002200 0001 0032 007e 0002220 0002240 7e7e 7572 6c6e 0002260 7665 6c65 0002300 2e32 2e36 0002320 3233 322d 2d32 6567 656e 6972 0063 0002340 * 0002720 5602 4bf7 7669 0003 0002740 * 0003000 0006 058f 7474 3479 0003020 0003040 0034 4f4c 4947 0003060 004e 0003100 * 0003520 5602 4bf7 0003540 * 0003600 0006 0594 7474 3579 0003620 0003640 0035 4f4c 4947 0003660 004e 0003700 * 0004320 5602 4bf7 0004340 * 0004400 0006 059c 7474 3279 0004420 0004440 0032 4f4c 4947 0004460 004e 0004500 * 0005120 5602 4bf7 0005140 * 0005200 0006 059e 7474 3379 0005220 0005240 0033 4f4c 4947 0005260 004e 0005300 * 0005720 5602 4bf7 0005740 * 0006000 0006 05a2 7474 3679 0006020 0006040 0036 4f4c 4947 0006060 004e 0006100
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 single runlevel failure after doing so. Figuring out what happens during the (re)install of the resolvconf-package might help fixing the runlevel-problem... -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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, 3940320/7670272 blocks lvanb...@navets:~$ initctl list alsa-mixer-save stop/waiting avahi-daemon start/running, process 787 mountall-net stop/waiting rc stop/waiting rsyslog start/running, process 758 tty4 stop/waiting udev start/running, process 325 upstart-udev-bridge start/running, process 323 ureadahead-other stop/waiting apport stop/waiting console-setup stop/waiting hwclock-save stop/waiting irqbalance stop/waiting plymouth-log stop/waiting tty5 stop/waiting atd stop/waiting dbus start/running, process 773 failsafe-x stop/waiting plymouth stop/waiting control-alt-delete stop/waiting hwclock stop/waiting network-manager start/running, process 782 module-init-tools stop/waiting cron stop/waiting gdm start/running, process 778 mountall stop/waiting acpid stop/waiting plymouth-stop stop/waiting rcS stop/waiting ufw start/running mounted-varrun stop/waiting rc-sysinit stop/waiting anacron stop/waiting tty2 stop/waiting udevtrigger stop/waiting mounted-dev stop/waiting tty3 stop/waiting udev-finish stop/waiting hostname stop/waiting mountall-reboot stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (lo) start/running network-interface (eth0) start/running network-interface (wlan0) start/running plymouth-splash stop/waiting tty1 stop/waiting udevmonitor stop/waiting dmesg stop/waiting network-interface-security start/running networking stop/waiting procps stop/waiting tty6 stop/waiting ureadahead stop/waiting -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 main process (875) terminated with status 4 Attached is a file containing two initctl list outputs, the first one after booting into runlevel unknown and the second after a working boot. However, on my system, each time after reinstalling the resovconf package via sudo apt-get install --reinstall resolvconf, I ended up with a working boot (it was not installed any more after the upgade). There is also a bug/question with this package under Bug #488945. Don't know if this helps at all... ** Attachment added: "initctrllist.txt" http://launchpadlibrarian.net/48702895/initctrllist.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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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" 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 start/running, process 343 ureadahead-other stop/waiting apport stop/waiting console-setup stop/waiting hwclock-save stop/waiting irqbalance stop/waiting plymouth-log stop/waiting smbd start/running, process 683 tty5 start/running, process 797 atd start/running, process 811 dbus start/running, process 737 failsafe-x stop/waiting plymouth stop/waiting ssh start/running, process 979 control-alt-delete stop/waiting hwclock stop/waiting module-init-tools stop/waiting cron start/running, process 810 mountall stop/waiting acpid start/running, process 809 plymouth-stop stop/waiting rcS stop/waiting ufw start/running mounted-varrun stop/waiting rc-sysinit stop/waiting tty2 start/running, process 801 udevtrigger stop/waiting mounted-dev stop/waiting tty3 start/running, process 802 udev-finish stop/waiting hostname stop/waiting mountall-reboot stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (lo) start/running network-interface (eth0) start/running plymouth-splash stop/waiting tty1 start/running, process 997 udevmonitor stop/waiting dmesg stop/waiting network-interface-security start/running networking stop/waiting procps stop/waiting tty6 start/running, process 804 ureadahead stop/waiting -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:9
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:10
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:10
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:12
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:12
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:13
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:13
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:15
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:15
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:16
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /lib/udev/rules.d/40-alsa-firmware-loaders.rules:16
/dev/sda1: clean, 80063/1221600 files, 553749/4883752 blocks (check in 3 mounts)
/dev/sda5: clean, 49534/1160992 files, 786663/4638760 blocks (check in 5 mounts)
udevd[345]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/70-persistent-lirc.rules:1
udevd[345]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/70-persistent-lirc.rules:2
init: ureadahead-other main process (616) terminated with status 4
lircd-0.8.6[649]: lircd(default) ready, using /var/run/lirc/lircd
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"
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 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
[Bug 543506] Re: 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
