I updated to upstart 0.6.5-7, rebooted, and have the same issues with
services not starting. Specifically, nginx doesn't start, and I have
two CGI services that interact with nginx, that don't start on boot.
I've checked with rcconf, and all 3 are labelled to start on boot.
Checking some of the lo
Status returns start/running , services start which is nice tho not
conclusive, just the runlevel is unknown.
On 17 Aug 2010 03:12, "Steve Langasek" wrote:
> "runlevel unknown" is a separate error. Please check that your
> /etc/network/interfaces is correct and has successfully initialized your
"runlevel unknown" is a separate error. Please check that your
/etc/network/interfaces is correct and has successfully initialized your
loopback interface (as shown by 'status network-interface
INTERFACE=lo').
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You rec
On one machine I have applied the later upstart from lucid-proposed
0.6.5.-7 and still get runlevel unknown on reboot.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package upstart - 0.6.5-7
---
upstart (0.6.5-7) lucid-proposed; urgency=low
* Apply patch from trunk to use /dev/null when /dev/console is unavailable
due to kernel bugs. This isn't a fix for those bugs, but it does work
around it for now. LP: #55
** Tags added: verification-done
** Tags removed: verification-needed
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Can also confirm this working. The system is taking longer to boot now -
who wonders: all services start now. However, I had no chance to do
excessive reboots since the machine is in production.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug n
The patched version of upstart looks so far. 25 reboots on the dual CPU
Pentium 3 machine and it has entered runlevel 2 each time.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Serge, please file a separate bug against the samba package for your
issue. This is not related to this bug preventing the startup of cups.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, w
Oops! My mistake! All services start but since smb start before cups,
printers are still not available in samba! I thought at first that the
new upstart package would solve that!
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification beca
CUPS still not starting after update of the proposed upstart package
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
I installed the proposed upstart binary, and since then booted my system
several times: the bug didn't reappear. All services started well.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Ditto
> Seems to work fine on my PC, all services start now.
>
> --
> system services not starting at boot
> https://bugs.launchpad.net/bugs/554172
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (543506).
>
> Status in “linux” package in Ubuntu: Confir
Seems to work fine on my PC, all services start now.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
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
** Changed in: upstart (Ubuntu Lucid)
Milestone: None => ubuntu-10.04.1
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Branch linked: lp:ubuntu/lucid-proposed/upstart
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
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
h
Accepted into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: linux (Ubuntu Lucid)
Statu
FYI, the fix for Lucid has been uploaded into -proposed:
http://launchpadlibrarian.net/53562040/upstart_0.6.5-7_source.changes
and is waiting for approval.
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member
Andy: if we can change the returned error code so it's not EIO, and
something more like EAGAIN that unequivocoably tells userspace that it
can loop, we can deal with that in userspace. That's just a one-line
change.
For example we could patch libc to always loop on those open()s, which
would fix
> Though open(2) does indeed not document this error, it is a documented
> POSIX return and it has been possible that this could get returned on
> open for a TTY for a very long time.
>
No it isn't, the current and previous editions of POSIX don't document EIO as a
return for open() - are you sur
Robbie: Way ahead of you on that one, I put a workaround in Upstart
together yesterday, and just uploaded it - now we understand the bug,
and the implications, it's safe to do so.
Upstart will now fallback to using /dev/null for jobs with "console
output" -- "console owner" will still fail, becaus
This bug was fixed in the package upstart - 0.6.6-2
---
upstart (0.6.6-2) maverick; urgency=low
* Apply patch from trunk to use /dev/null when /dev/console is unavailable
due to kernel bugs. This isn't a fix for those bugs, but it does work
around it for now. LP: #554172.
I am running a rack-mounted remote server that I was going to upgrade
while the students are away. I cannot rely on ssh to start, or apache2
or mysql so I am somewhat stuffed chaps. Any news on this getting
sorted or should I leave it with 7.04 server?
--
system services not starting at boot
htt
> open(2) does not document EIO as a valid return from this function, and
> I'm not even sure this error is appropriate - where it's used elsewhere it
> nearly always refers to a filesystem error - there are few exceptions. If
> the intent is that the calling process should just try again, shouldn'
Scott,
Could we consider carrying a short-term hack in Lucid/Maverick for
upstart (but not put in the main upstart tree), and then remove it for
11.04...when the issue is supposedly fixed in the kernel?
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received t
Another point to consider (I discussed this with a few people here at
LinuxCon):
open() is supposed to be an inherently blocking system call, just like
connect(), creat(), etc. If the kernel hasn't finished hanging up the
tty from last time, it's *okay* for the subsequent open() to block for a
wh
Also, let's consider the other effects of this kernel change. For
example, the following code from the initramfs that actually exec's init
in the first place:
exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console
>${rootmnt}/dev/console 2>&1
This opens /dev/console to be bound to init'
More robust, how?
If the job is configured to require its standard three file descriptors
to the system console, and Upstart is unable to open the system console,
it is unable to satisfy the requirements of the job configuration so
will terminate the attempt to start the job.
Read through the ent
Having talked to upstream and clarified the plans with the BTM, it
seems that they are intending on closing some of the races as they are
deemed unhelpful. Overall however some slow TTY devices will indeed
still legitimatly return EIO when a slow close is in operation. That is
expected behaviour.
Similar symptoms for me on fully upgraded Ubuntu 10.04 on Dell Inspiron
laptop dual-booting with Win7 using grub2. A triple-workaround that
worked for others here (but not me) is listed below.
sudo -s
for file in /etc/init/*.conf; do sed -i 's/^console output/\#console output/'
$file; done
sed -i
@Phil -- setting quiet would likely make things more likely as it simply
prevents visible printing of the output, it does not reduce the
contention on the console_sem its likely to increase it. Commenting out
the open of /dev/console however from the upstarts configuration files
should have an eff
If I can reproduce the bug when the quiet kernel option is set (this
disables console output to speed up boot), does this analysis still hold
water? Same for commenting out output to /dev/console in init files. There
may be an issue according to the analysis, but am not sure whether it is the
root
Many thanks to Andy Whitcroft for his truly excellent analysis above in
comment #245.
REPRODUCING THE BUG: It looks to me as though what is required to
reproduce this bug is a fast multi-core machine with a slow video card.
It just so happens that is exactly what my machine is like. When I build
a
** Changed in: linux (Ubuntu Lucid)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft
(apw)
** Changed in: linux (Ubuntu Maverick)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft
(apw)
--
system services not starting at boot
https://b
First some background. Analysis above indicates that upstart jobs are
failing because opens of /dev/console are failing, and that this should
not be possible:
"... open("/dev/console") is _not_supposed_to_fail_."
As previously indicated /dev/console is a virtual device which represents
t
My twopennies.
I'm running 10.04 server w. the following kernel:
2.6.32-21-generic-pae #32-Ubuntu SMP
The machine is an old Thosiba laptop w: 250 Mb and a Pentium III processor
(~600 Mhz).
It has worked flawlessly w-out the recommended fixes as a printerserver for
some months.
--
system servic
Thanks Robbie.
This problem shows up more often on faster systems.
every quad phenom/nvidia box I have put together does it.
all quad opteron servers (NO GUI) does it regardless of video card.
Sometimes on the servers bind9 will fail. ddclient also fails
vboxdrv also fails to start on boot an
Scott,
I've done some investigation based on the hypothesis that this bug is
> caused by open("/dev/console") returning the EIO error, this is
> supported by comments including this log message from Upstart and by
> evidence that removing "console output" from Upstart jobs appears to
> correct the
I've installed Ubuntu on 20 machines for individual desktop use. Most
have been on AMD processors, and most of those have been on dual core
and 1 quad core. The single core machines have rarely been used to print
from. I've seen the issue on both dual core and quad core.
I hope this helps.
O
akaname, I've only seen it on one machine and that had two Pentium 3
CPUs (separate chips).
Of the machines which have not seen this problem, the virtual machines
are all single processor and the servers all had multiple core CPUs
(Pentium D, AMD X2, Core2 Duo and Quad).
There were a few desktop
It should be noted that the commentary is #238 is from the fix which
eliminated that error, not introducing that error. This fix is also
already applied to both Lucid and Maverick kernels.
commit f278a2f7bbc2239f479eaf63d0b3ae573b1d746c
Author: Dave Young
Date: Sun Sep 27 16:00:42 2009 +
The kernel patch that introduces this regression is
f278a2f7bbc2239f479eaf63d0b3ae573b1d746c, which even notes in the commit
log:
Due to tty release routines run in a workqueue now, error like the
following will be reported while booting:
INIT open /dev/console Input/output error
** Tags added: kernel-core kernel-needs-review
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
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
** Also affects: Ubuntu Maverick
Importance: High
Status: Confirmed
** Changed in: Ubuntu Maverick
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: Ubuntu Lucid
Assignee: Canonical Foundations Team (canonical-foundations) => Robbie
Willia
Hey folks,
I've done some investigation based on the hypothesis that this bug is
caused by open("/dev/console") returning the EIO error, this is
supported by comments including this log message from Upstart and by
evidence that removing "console output" from Upstart jobs appears to
correct the pro
#39 broken here after 3 boots:
mdo...@doris:~$ runlevel
unknown
mdo...@doris:~$ uname -a
Linux doris 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 05:14:15 UTC 2010
x86_64 GNU/Linux
Also have a suspend-to-ram failure since 2.6.32-23, bug #602049
Vaio SZ6 notebook, Core 2 Duo + Intel graphics + Inte
@Robbie Williamson:
Just upgraded to #39, and I was lucky this time:
m...@bluebird:~$ runlevel
N 2
m...@bluebird:~$ uname -a
Linux Bluebird 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 05:14:15 UTC 2010
x86_64 GNU/Linux
First boot was ok, while #38 always failed.
--
system services not starting
@John Edwards
A Question to your machines (real and virtual) that are not affected by this
bug: How many processor cores or virtual processors cores do they have?
--
system services not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a m
48 matches
Mail list logo
