> There are currently no plans to implement such policy in the upstart
package.
Is that an answer?
How is booting to "text" mode any different from booting to Unity, KDE,
Gnome, or any of a dozen other possible modes? Demanding that each of
those implement the "text" mode sounds wrong to me.
De
Wow! After the long silence in this bug I figured nothing was happening.
It wasn't linked to anyplace where the ongoing discussion of Upstart's
evolution was clearly happening.
I have a lot of reading to do.
I would like acknowledgment of my contribution in the Cookbook.
I'm sure there are other
On Mon, Feb 14, 2011 at 05:56:44PM -, Clint Byrum wrote:
> The request to create a new bug report, marking it as possibly related,
> is a common practice and it has proven useful in the past to get things
> fixed.
>
> Right now the issue that was reported originally is definitely fixed
> from
We users are NOT experts in the Launchpad rules and regulations.
We just want our problems addressed.
Please do whatever is necessary to open up a bug that addresses the
long standing and still present condition of init scripts not being executed
reliably.
For "Title" and "Description" I propose:
> > On Sat, Feb 12, 2011 at 02:15:20PM -, Brian J. Murrell wrote:
> > Any news on this bug? Is anyone trying to fix it?
> On Sat, 2011-02-12 at 12:11 +, Jens Schødt wrote:
> Yeah, IMHO, upstart was wa rushed into Ubuntu. ...
I agree.
The evidence strongly suggests that Upstart st
> Clint Byrum wrote in comment #4 ...
> Complaining loudly is different than asserting, IMO, so I may have just
> misunderstood your intent.
My intent is to have a trail of crumbs when the expected events fail to happen.
If the boot sequence gets to runlevel 2 that is very different from
runle
peatedly by upstart and
so I am still on Ubuntu 8.04. I understand /etc/init.d/S[0-9][0-9]* .
I don't yet understand /etc/init/*.conf .
Mike Bianchi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/58
On Mon, Jan 31, 2011 at 04:52:18AM -, Josh Kupershmidt wrote:
> :
> Feb. 30th is an invalid date which `date` doesn't want to return, which
> is why it's bumping the result into March.
This explanation does not quite square with the behavior. Witness:
date
Mon Jan 31
On Wed, Jan 12, 2011 at 03:14:41PM -, John Edwards wrote:
> David Haskins, could you run the 'runlevel' command to check if this is
> related to this particular bug, or if it is another problem?
A better approach might be to put logging into /etc/init.d/apache2
and figure out:
If it i
I misspoke in Comment #3.
"text" prevents X from starting.
I believe the removal of "slash" and "quiet" prevent the normal boot graphics.
--
Services not starting on boot in 10.04.1 LTS
https://bugs.launchpad.net/bugs/642555
You received this bug notification because you are a member of Ubuntu
B
> I'd believed this was an upstart issue and related to bug 554172
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172)
> I tried the workarounds until an official fix was release, but neither the
> workarounds nor the official patch solved the issue for me.
Please document here preci
It occurs to me that if you want to force the /dev/console bug, it might be
as simple as adding "console output" to all the /etc/init/*.conf files.
If "successful" it could leave the installation unbootable, so I would
advise doing this in a disposable installation on a separate partition.
--
ole too
early, it fails.
I did a step-by-step analysis in Bug 543506. Start at comment #54.
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/54
--
Mike Bianchi
Foveal Systems
973 822-2085
mbian...@foveal.com
http://www.AutoAuditorium.com
http://www.FovealMounts.com
> . . .Could the lack of a monitor actually plugged into
> the DRAC have anything to do with it (Dell Remote Administration Card)?
I would say "yes". While working out that /dev/console was part of the
problem I did many boots with "verbose" turned on and could see that
order of the start-up
On Tue, Aug 03, 2010 at 02:38:04AM -, Lindsay Barclay wrote:
> ... and for some reason it worked. It has been two days and I have done 10
> cold restarts and cups has loaded each time. I can't explain it, ...
This bug, which at its base is unreliable boots where scripts in
/etc/init/*.conf and
On Mon, Aug 02, 2010 at 03:58:54PM -, Robbie Williamson wrote:
> I'm sorry if you disagree with the policy, but I feel it's a
> good one to have and don't want to waste bug comment space defending it.
I made my argument and have been heard. My argument did not convince.
That's the way it is s
On Mon, Aug 02, 2010 at 12:16:08PM -, Phil Went wrote:
> Workarounds are hocus pocus and should not be distributed. They do not work
> in all cases, so are at best an indicator of where to look for a developer.
> Shouting even when frustrated does not solve problems faster. I will wait
> patie
On Mon, Aug 02, 2010 at 03:24:28AM -, Robbie Williamson wrote:
> :
> 2) It has *something* to do with when lo0 is activated, i.e. a race condition
I disagree, it has something to do with not being able to write /dev/console.
See my analysis in bugs 581291 and 543506.
> 3) There are appa
On Thu, Jul 22, 2010 at 03:18:10PM -, phireph0x wrote:
> RE: Mike Bianchi Yes, I tried ALL of the instructions suggested:
> ... I still have services that don't start on reboot,
Thanks for all your efforts.
Do you get runlevel "unknown" or "N 2"
On Tue, Jul 20, 2010 at 09:49:13AM -, Kai Krakow wrote:
> I don't think that any workarounds could really fix this - the
> workarounds just modify timing or reduce impact.
You are absolutely right.
These are workarounds.
But they are the best we can do because I, for one, do not have the time
On Mon, Jul 19, 2010 at 08:04:03PM -, phireph0x wrote:
> The workaround described in
> http://ubuntuforums.org/showpost.php?p=9480172&postcount=20 doesn't work
> for me. I still have services that don't start on system reboot.
See
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/5435
Damien, Sepero, and all ...
If you look at
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/83 you
will see
that I also recommend
Add "init='/sbin/init --verbose'" to the linux boot line in grub.
I believe this helps by forcing "/sbin/init" to serialize starting up
On Thu, Jul 01, 2010 at 08:06:52PM -, John Edwards wrote:
> For Mike Bianchi - what kernel was your 64-bit machine running? To find
> out run 'uname -a' and post the output.
I don't have access to that machine now, but this from a syslog kept while
debugging. You can s
On Thu, Jul 01, 2010 at 07:26:47PM -, John Edwards wrote:
> So has anyone seen it on a machine which is not a 32-bit install running
> a "generic" (not "generic-pae") kernel?
In my case, I was running a quad-core AMD with a 64-bit Linux. For a while I
thought it was a problem that showed up o
On Thu, Jul 01, 2010 at 04:42:53AM -, Andy wrote:
> This is a serious problem. At this point 10.04 is not production worthy. ...
I agree.
But the evidence is that Canonical is just not paying any attention to this
line of bugs OR somehow does not think they _are_ serious.
I have a service
*** 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"
On Sat, Jun 26, 2010 at 04:27:35PM -, Tim Scheurenbrand wrote:
> Re #131: I tried the solution stated at the other bug-report but it doesn't
> work for me. First reboot after change already started in unknown runlevel
> without starting services like CUPS.
runlevel returning "unknown" appear
On Fri, Jun 25, 2010 at 10:33:02PM -, vindex wrote:
> I have this problem, too, but not only with cups, rc.local and some
> custom startup-scripts are not starting, either.
Look at
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506/comments/83
That has worked for many of us.
--
C
Joel, Till
Re comment #122. I believe you have it backwards.
I believe if you apply the get-around spelled out in comment #83 of
http://bugs.launchpad.net/ubuntu/+source/upstart/+bug/543506
you will find that your CUPS starts will be reliable.
I've seen native 10.4 upstart boot go to "unknown"
/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.
--
M
On Wed, Jun 09, 2010 at 01:06:20PM -, Olivier Debon wrote:
> What I could diff from syslog between a successful startup and a no runlevel
> situation is that only the 2 following messages are missing in the failure
> case:
For many of us, the solution is already in this Bug report. Namely:
On Fri, Jun 04, 2010 at 02:29:49AM -, Francisco.X wrote:
> :
> In the old init.d system, it was easy for me to add something like an
> echo or syslog message to any script to know when it was being executed.
> How can I do the same so I can know if /etc/init/rc-sysinit.conf is even
> run
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
> diff
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.con
etd 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
F
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.co
ere 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,
> I have not found any core file.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/null/+bug/586076/+subscribe
--
Mike Bianchi
Foveal Systems
973 822-2085
mbian...@foveal.com
http://www.AutoAuditorium.com
http://www.FovealMounts.com
--
plymouthd
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 n
I attaching a mofified /etc/init/rc.conf file and marking it as a
solution to this bug.
** Attachment added: "modified rc.conf is a solution to bug 585915"
http://launchpadlibrarian.net/49146163/rc.conf
--
rc.conf fails due to "console output"
https://bugs.launchpad.net/bugs/585915
You receiv
/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 eve
** Attachment added: "syslog_rc_fail"
http://launchpadlibrarian.net/49140893/syslog_rc_fail
--
rc.conf fails due to "console output"
https://bugs.launchpad.net/bugs/585915
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Public bug reported:
Binary package hint: upstart
As shown in the attachment snipped from /var/log/syslog, the /etc/init/rc.conf
file can sometimes fail if the
"console output" stanza fails.
Commenting that stanza out seems to fix the problem and allow rc.conf to
run properly.
** Affects: upst
Public bug reported:
Binary package hint: upstart
Finding where events are asserted and which *.conf files are sensitive
to an asserted event is difficult.
As a documentation habit, it would be good to have comments in both the
*.conf files and the scripts that make assertiongs and the man pages
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
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 notif
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 becaus
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.
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 happe
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 "
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
> > 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 /
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.n
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
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 servi
*** This bug is a duplicate of bug 543506 ***
https://bugs.launchpad.net/bugs/543506
> Suggestion: use start on runlevel [2345] in /etc/init/tty[1-6].conf
Am I expected to make that sort of change to /etc/init/*.conf files?
Maybe there could be two categories:
/etc/init
/etc/init_local
*** This bug is a duplicate of bug 543506 ***
https://bugs.launchpad.net/bugs/543506
> If you read those conf files, they depend on the non-Upstart services
being started (runlevel/rc etc.)
Does that make sense?
It would seem to me that the only requirement for gettys on /dev/tty[1-6]
is
*** This bug is a duplicate of bug 543506 ***
https://bugs.launchpad.net/bugs/543506
> Thanks, this matches the symptoms of bug #543506 - investigation is
> still ongoing; in most cases it actually looks like a failure of the
> non-Upstart services not the Upstart ones.
I don't see how you c
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 noti
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 notifi
*** This bug is a duplicate of bug 543506 ***
https://bugs.launchpad.net/bugs/543506
I'm moving my participation in this discussion to bug #543506.
--
upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d files
https://bugs.launchpad.net/bugs/581291
You received this bug notifica
** Attachment added: "boot.log.successful"
http://launchpadlibrarian.net/48602977/boot.log.successful
--
upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d files
https://bugs.launchpad.net/bugs/581291
You received this bug notification because you are a member of Ubuntu
Bugs, w
Scott -- sorry -- I missed the request for /var/log/boot .log
** Attachment added: "boot.log.failed"
http://launchpadlibrarian.net/48602952/boot.log.failed
--
upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d files
https://bugs.launchpad.net/bugs/581291
You received this bug
Also, with init='/sbin/init --verbose' boots are not 100% reliable. Some
times they still fail.
I have set the number of active CPUs to 3 (was 4) in the BIOS, in desperate
hope that this will make things more reliable.
--
upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d fil
After a successful boot, with init='/sbin/init --verbose' : N 2
After a failed boot, without init= : unknown
--
upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d files
https://bugs.launchpad.net/bugs/581291
You received this bug notification because you are a member of Ubuntu
Having now learned that /var/log/apt/history noted the move from mountall
2.14 to 2.15 today and that
apt-get install mountall=2.14 sets the package back to what it was, I seem
to have returned to the more reliable booting behavior.
--
upstart (/sbin/init) fails to start many /etc/init
I spoke too soon.
The init='/sbin/init --verbose' trick worked, until I accepted an update that
was a new version of the mountall package.
Now I have the old behavior even with --verbose . Sigh.
I don't _know_ that mountall caused the problem. I was working on other stuff
and only discove
** Attachment added: "syslog.old"
http://launchpadlibrarian.net/48552928/syslog.old
--
upstart (/sbin/init) fails to start many /etc/init and /etc/rc2.d files
https://bugs.launchpad.net/bugs/581291
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I am unable to provide the failure evidence, beyond the observations of
things like "ps axf does not show any getty processes", because upstart
was not putting any messages to the console nor into log files. I don't
see any logging mechanism in /etc/init, probably because it expects
things that f
** Attachment added: "xorg_fixup.log"
http://launchpadlibrarian.net/47940353/xorg_fixup.log
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: "term.log"
http://launchpadlibrarian.net/47940320/term.log
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Attachment added: "system_state.tar.gz"
http://launchpadlibrarian.net/47940306/system_state.tar.gz
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/47940245/lspci.txt
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
** Attachment added: "main.log"
http://launchpadlibrarian.net/47940255/main.log
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
apt-term.log
** Attachment added: "apt.log"
http://launchpadlibrarian.net/47940215/apt.log
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: "apt.log"
http://launchpadlibrarian.net/47939835/apt.log
--
error updating fglrx
https://bugs.launchpad.net/bugs/576318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Public bug reported:
Binary package hint: update-manager
from /var/log/dist-upgrade/term.log
Selecting previously deselected package fglrx.^M
Unpacking fglrx (from .../fglrx_2%3a8.723.1-0ubuntu3_amd64.deb) ...^M
^M
[Warning] Uninstall : inst_path_default or inst_path_override^M
does not exist
I acquired
linux-image-2.6.24-21-generic
linux-headers-2.6.24-21
linux-headers-2.6.24-21-generic
linux-ubuntu-modules-2.6.24-21-generic
linux-restricted-modules-2.6.24-21-generic
from
deb http://us.archive.ubuntu.com/ubuntu/ hardy-proposed restricted main
multiverse universe
The kernel halt
2
quiet
savedefault
And when I start the kernel, I see Grub flash Starting Up
and then nothing; no image, no disk rattle.
Does anyone see what I'm missing?
--
Mike Bianchi
--
Kernel Panic, in gdth (RAID) driver on reboot
https://bugs.launchpad.net/bugs/199934
Y
at am I missing? I saw something of having to set up my own PPA, but I
don't understand how that helps.
--
Mike Bianchi
Foveal Systems
973 822-2085 call to arrange Fax
[EMAIL PROTECTED]
http://www.AutoAuditorium.com
http://www.FovealMounts.com
--
Kernel Panic, in gdth (RAI
80 matches
Mail list logo
