System now using upstart 1.5 (as per latest updates...). Fix confirmed
as functionnal. thnx!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
T
** Changed in: upstart
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
To manage notifications abou
** Attachment added: "Kernel call-trace when NOT using --no-log parameter"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/912558/+attachment/2859647/+files/Kernel-call-trace.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Perhaps this bug is still present? I'm having the exact same issue at
boot-time
root@th0ma7:/home/th0ma7# ./find_missing_commands.pl
relative command gdm-binary not found
relative command kdm not found
root@th0ma7:/home/th0ma7# dpkg -l | grep -i upstart
ii upstart
This bug was fixed in the package upstart - 1.4-0ubuntu3
---
upstart (1.4-0ubuntu3) precise; urgency=low
[ Stéphane Graber ]
* Mark upstart Multi-Arch:foreign
[ James Hunt ]
* Merge of important logger fixes from upstream lp:upstart
(LP: #912558).
* Reverted temporary f
** Changed in: upstart (Ubuntu Precise)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
To manage noti
** Branch linked: lp:~jamesodhunt/ubuntu/precise/upstart/fix-for-
bug-912558
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
To manage notificat
** Changed in: upstart
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
To manage notifications about t
mike@cornwall:~$ ./find_missing_commands.pl
relative command nmbd not found
relative command smbd not found
relative command ubiquity not found
mike@cornwall:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
@James Hunt: As an aside, I tested the more inclusive perl script
(above). Ran fine -- same result(s)
vindsl@Zuul:~/Downloads$ ./find_missing_commands.pl
relative command NetworkManager not found
vindsl@Zuul:~/Downloads$
Thanks, again!
--
You received this bug notification because you are a me
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Importance: Undecided => High
** Changed in: upstart
Status: New => Incomplete
** Changed in: upstart
Status: Incomplete => Opinion
** Changed in: upstart
Status: Opinion => Confi
I updated the Upstart package to 1.4-0ubuntu2
mrk3004@viny-server:~/Build$ ./find_missing_commands.pl
mrk3004@viny-server:~/Build$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c
@Vinycius: Please could you run the attached "find_missing_commands.pl"
Perl script. This is an improvement over the original shell script since
it now checks for *all* shell meta characters rather than just the most
common ones.
Process:
1) download find_missing_commands.pl script to your system
@VinDSL: no problem. Thank *you* for working with us to identify 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/912558
Title:
log.c Assert failed - err=>number == EIO
To manage notifica
Just got home and updated the Upstart Package from 1.4-0ubuntu1 ->
1.4-0ubuntu2
No more kernel panic!!!
Thanks, for your quick attention to this dire situation, James Hunt!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
mrk3004@viny-server:~$ ./find_missing_commands.sh
mrk3004@viny-server:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
To manage notification
mike@cornwall:~$ ./find_missing_commands.sh
nmbd
smbd
ubiquity
mike@cornwall:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number == EIO
To manage noti
@Kaulbach: Thank you for taking the time to transcribe the panic.
A full fix for this problem has already been written but requires new
test cases to be written too (it also requires the full test suite to be
run extensively).
Rest assured, we intend to put out an updated Upstart package as soon
@VinDSL: Thanks very much! Your result proves the theory. Anyone else
get any results from this script?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log.c Assert failed - err=>number
The pastebin from posting number 2 is mine, and yes the same problem. I
manually wrote down from the kernel panic screen then transcribed it to a file
while in recovery mode, used pastebinit to post.
Installing the upstart version mentioned earlier, it finally allowed me to boot
normally.
Previo
@James Hunt
vindsl@Zuul:~/Downloads$ sh find_missing_commands.sh
NetworkManager
vindsl@Zuul:~/Downloads
I'm running Wicd as my network manager.
network-manager refuses to work (on my PC) under Linux 3.2, e.g. no
network connection(s), and was uninstalled, some time ago.
--
You received this bu
@James Hunt
vindsl@Zuul:~$ ls /etc/init/
acpid.conf networking.conf
alsa-restore.confnetwork-interface.conf
alsa-store.conf network-interface-security.conf
anacron.conf network-manager.conf
apport.conf network-manager.conf~
atd.conf
If you have this problem, it would be *very* helpful to use if you could
run the attached script on your system.
Please report back if you got any output from the script. If the script
produces no output, you should not have a problem.
Process:
1) download script to your system.
2) chmod 755 fin
I think we now understand what is happening here. Essentially, the
problem occurs when jobs refer to binaries that don't exist on the
system. The common case of this scenario is if you've installed a
package with a job file in /etc/init/, but then removed the package. The
binaries have now been rem
To allow us more time to diagnose this issue, we've decided to push out
an updated upstart package where logging has been disabled by default.
Please update your systems to install upstart version '1.4-0ubuntu2'.
** Changed in: upstart (Ubuntu Precise)
Importance: Critical => High
--
You re
@VinDSL: Thanks for reporting. Please could you list the .conf files you
have. In other words, what does the following return:
ls /etc/init/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Tit
** Also affects: upstart (Ubuntu Precise)
Importance: Critical
Assignee: James Hunt (jamesodhunt)
Status: Confirmed
** Changed in: upstart (Ubuntu Precise)
Milestone: None => precise-alpha-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912558
Title:
log
I meant to type 5-Jan-2012 (not 2011) above... sigh!
Anyway, I thought I should also mention, immediately preceding the
kernel panic/core dump, a little flashing white line appears in
Plymouth... and the end of the animated dots. Never saw that before.
After I implemented the --no-log workaroun
I'm having this issue as well, on my Ubu 12.04 alpha 1 install. It
happened after the 5-Jan-2011 update(s). I'm performing forensics now.
The --no-log workaround (above) allowed me to boot into Ubu 12.04
I might also mention...
I have two kernels installed on this machine - Linux 3.1 & Linux 3
It seems that a particular job or combo of jobs is causing this issue,
but unclear why (since all jobs are treated equally by the logger).
I'm currently working with Dave to try and isolate the job(s) causing
the failure. I'll also create a PPA with some extra debug to identify
what err->number is
The output here unfortunately doesn't give many clues as to what's
really going on. James, can we turn up the verbosity for this error
case?
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Tags added: rls-p-tracking
--
You received this bug notificati
Whilst looking for others that have encountered this, I came across an
unreferenced pastebin http://pastebin.com/sPwXJS0x , seems to be the
same issue.
...
init: log.c: 291: Assertion failed in log_io_error_handler: err-> number == EIO
init: Caught abort, core dumped
init: io.c: 1312: Unhandled er
Attached screenshot.
** Attachment added: "precise-init-crash.jpg"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/912558/+attachment/2659418/+files/precise-init-crash.jpg
** Description changed:
Whilst booting, init has an issue and causes a core dump -> kernel
panic.
+
+ Append
34 matches
Mail list logo
