On 12/20/2011 09:47 AM, Clint Byrum wrote:
The best way to try and figure out what is causing this is to modify
/etc/init.d/umountroot and right before the umount's, add
/usr/bin/lsof -n /saved.root.lsof
sync
This will save a listing of all opened files and which processes have
them
Excerpts from chtnh's message of Sat Jul 23 04:41:01 UTC 2011:
I'm new in Ubuntu (10.10) and in Lauchpad, and I have this bug. I don't
understand how you fix it, as there is fix released. Can someone explain
me, please?
There are other bugs that sometimes cause an unclean shutdown, this one
On 16.02.2011 00:25, Clint Byrum wrote:
There are also a couple more bugs
covering daemons that need to be shutdown, namely, sshd and portmap.
Clint,
the portmap Bug #711425 you filed has not got any attention yet, it's
still undecided and unassigned - does nobody care?
--
You received this
On Tue, 2011-02-15 at 21:51 +, Paul Crawford wrote:
Well it is not yet fixed for 10.04 with the 'proposed' updates. Tonight
just rebooted after updates to kernal 2.6.32-29 and guess what? Yes, my
syslog contained the following sort of message:
Feb 15 21:45:24 paul-ubuntu kernel: [
Bad news there: I'm afraid that we've already had to entirely freeze
updates for 10.04.2 in order that we can get certification done in time;
unfortunately that's a rather time-consuming process and needs a couple
of weeks of clearance. I expect that 10.04.3 won't be a problem,
though.
--
You
I'm afraid there's no point railing about it here - we're already
committed to the date and it would be a colossal rearrangement of many
people's schedules to change it at this point. As I say, sorry, and we
should be able to get this nailed down for .3.
--
You received this bug notification
At least certified bugs can be documented, with certified workarounds.
On Wed, Feb 2, 2011 at 2:05 PM, ingo 672...@bugs.launchpad.net wrote:
... freeze updates for 10.04.2 in order that we can get certification
done
That means we get certified BUGS - and that 10 months after release!
--
On Sun, 2011-01-23 at 12:39 +, ingo wrote:
Observed just another oddity, probably a separate bug in mountall?
I tried to mount the / filesystem (ext3) in journal mode to see if this
improves the situation by adding the option to /etc/fstab:
data=journal,erros=remount-ro
But that
On Sun, 2011-01-23 at 11:50 +, ingo wrote:
Sorry, but I can't reproduce it now, getting still 4 orphaned inodes.
Can I insert some lines to log which libs are still in use?
Yes, you can put this just after the remounts:
lsof -n | grep DEL
sleep 10
Which will give you 10 seconds to view
On Tue, 2011-02-01 at 16:17 +, ingo wrote:
you can put this just after the remounts:
lsof -n | grep DEL
sleep 10
*Lucid-amd64*
I did so (with new libc6 and upstart from Lucid-proposed installed) and found
something new:
it's the NFS which makes trouble. Portmap and statd are still
On Tue, 2011-02-01 at 20:23 +, ingo wrote:
But there is no way to codify that point in the shutdown into the
upstart job, which I suspect is why it has no stop on. I believe the
proper way to handle this is to have a matching event to
remote-filesystems , unmounted-remote-filesystems,
On Tue, 2011-02-01 at 21:32 +, ingo wrote:
Puh, by and by I understand why Ubutu is blamed for use on servers.
Do you see any chance to get that mess cleaned up in Lucid?
(Squeeze is beeuing released soon)
I don't know if I'd call it a mess at this point. The shutdown will
certainly be
On Tue, 2011-02-01 at 23:06 +, Jimmy Merrild Krag wrote:
Now (after a while) I've gotten through reading this bug.
I have just updated my server, it now runs 10.04.2. Does this mean it
has no issues? It's a non-critical server I access remotely. should I
care at all, or just wait for
ingo: that's the way the Ubuntu release process works, I'm sorry that
this is a surprise to you
On Mon, Jan 24, 2011 at 1:00 PM, ingo 672...@bugs.launchpad.net wrote:
@Zippo,
it is really a sad story with LTS-Lucid. I really don't understand how
such a buggy release could pass QC (if there is
On Sat, 2011-01-22 at 11:50 +, ingo wrote:
Thanks for Lucid-fix. I did immediately test with new 'libc6' and
'upstart' from Lucid-proposed:
1. just new 'libc6' - does not change anything (8 orphaned inodes after
reboot).
2. + new 'upstart' - gives 1 orphaned inode after reboot.
3.
On Wed, 2011-01-05 at 21:31 +, ingo wrote:
Hi Clint,
thanks for fast fix - but unfortunately only in Natty which is still in
development. This bug was reported for *Lucid*, which in terms of
service will even survive Natty. When will that be fixed and who cares?
Hi Ingo. This is the
Yes, I know how to drive bzr and dpkg ;-)
My point is that if you do that diff, the only occurrence of SIGTERM
is in the code for the upstart/udev bridge, that patch doesn't add any
handling to upstart itself.
Scott
On Wed, Dec 29, 2010 at 6:54 AM, Clint Byrum cl...@fewbar.com wrote:
On Wed,
I've no idea why that revision got dropped from the Ubuntu package, I
did a bit of investigation and it seems to vanish about the point we
switched to the auto-importer based packages. My only guess is that
bzr undid the cherry-pick as part of a merge.
Right, eglibc's postinst should definitely
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote:
This makes sense, because telinit u just sends SIGTERM to upstart, which
has no handler, as it was removed by revision 977, and doesn't seem to
have been added back. Since SIG_DFL signals are not delivered to init,
I'm not
On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote:
This makes sense, because telinit u just sends SIGTERM to upstart, which
has no handler, as it was removed by revision 977, and doesn't seem to
have been
Are you sure? I can't find that code at all - it looks like it's been
lost somehow
On Tue, Dec 28, 2010 at 6:19 PM, Clint Byrum cl...@fewbar.com wrote:
On Tue, 2010-12-28 at 14:22 +, Scott James Remnant wrote:
On Tue, Dec 28, 2010 at 6:47 AM, Clint Byrum cl...@fewbar.com wrote:
This
On Wed, 2010-12-29 at 00:06 +, Scott James Remnant wrote:
Are you sure? I can't find that code at all - it looks like it's been
lost somehow
quite certain.. its a bit tricky to find it in bzr, but this will give
it to you for, say, maverick:
$ bzr branch lp:ubuntu/maverick/upstart
22 matches
Mail list logo
