This bug was fixed in the package mysql-5.5 - 5.5.20-0ubuntu1
---
mysql-5.5 (5.5.20-0ubuntu1) precise; urgency=low
* New upstream release.
* d/mysql-server-5.5.mysql.upstart: Fix stop on to make sure mysql is
fully stopped before shutdown commences. (LP: #688541) Also
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu4.1
---
sysvinit (2.88dsf-13.10ubuntu4.1) oneiric-proposed; urgency=low
* d/src/initscripts/etc/init.d/sendsigs: wait up to 300 extra
seconds for upstart jobs that have been killed. They will be sent
SIGKILL by
Tested the Python test case from the bug description using the
initscripts in Oneiric proposed. Prior to patch, did see Killing all
remaining processes... fail as described. After patch, saw All
processes ended within 16 seconds. According to the test case, this
is a successful fix.
--
You
Alan you are my stable release update hero this week. :) The update
should land in about 5 days (minimum 7 in -proposed just in case we
missed a major regression.)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
Hello Michael, or anyone else affected,
Accepted sysvinit into oneiric-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
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu8
---
sysvinit (2.88dsf-13.10ubuntu8) precise; urgency=low
* d/src/initscripts/etc/init.d/sendsigs: wait up to 300 extra
seconds for upstart jobs that have been killed. They will be sent
SIGKILL by upstart when
** Also affects: mysql-5.1 (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: mysql-5.5 (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Changed in: mysql-5.1 (Ubuntu
Fix is waiting in the oneiric-proposed queue.
** Description changed:
+ == SRU JUSTIFICATION ==
+
+ IMPACT: potential data loss or extension of downtime. MySQL, for
+ example, if sent a SIGKILL before it is done flushing its buffers into
+ MyISAM tables, will lose that data. If using InnoDB,
** Changed in: mysql-5.5 (Ubuntu Precise)
Status: In Progress = Invalid
** Changed in: mysql-5.1 (Ubuntu Precise)
Status: Triaged = Invalid
** Changed in: sysvinit (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: sysvinit (Ubuntu Precise)
Assignee:
** Branch linked: lp:~clint-fewbar/ubuntu/precise/sysvinit/wait-for-
long-shutdown-jobs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown
** Changed in: sysvinit (Ubuntu)
Importance: Undecided = High
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
So, I believe the right way to handle this is to wait a long time for
any upstart job that has status of 'stop/killed'.
We can't be finding all of the services that are slow to shutdown one
by one. Authors of upstart jobs will know how long to wait before
sending kill -9. Once kill -9 has been
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mysql-5.5 (Ubuntu)
Status: New = In Progress
** Changed in: mysql-5.5 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: mysql-5.5 (Ubuntu)
Assignee: (unassigned) = Clint Byrum (clint-fewbar)
** Changed in: mysql-5.1 (Ubuntu)
Status: In Progress = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
I agree that this should be fixed in sysvinit. Is it really appropriate
to change mysql-5.5 at all? It should be a straightforward change to
sysvinit, and the mysql change should be reverted afterwards.
** Tags added: rls-p-tracking
** Also affects: mysql-5.1 (Ubuntu Precise)
Importance:
I think ultimately no, mysql-5.5 shouldn't be changed for this, and
agreed the change should be straight forward. I was not certain if we
were willing to tackle the sysvinit change in precise.. but on second
thought, of course we should be. So I'll hold back on the change to
mysql-5.5 and take a
I do unsubscribe from this bug for the time beeing. It does not make
sense to deal with the symtoms until the root of the evil Bug #672177 is
fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
I first tried to grep within a x-term, but there I get faulty output regarding
gvfs. I suppose it's not needed.
So I booted into a maintainence root-shell (without network) and did:
lsof -n | grep deleted - nothing reported
apt-get install --reinstall libc6
and afterwards
lsof -n | grep
And here the output of
initctl list
after reinstall of libc6. It is amaizeing, that even though I selected
root shell without network in the maintainence system, a lot of
services including network is up and running (I used scp to copy the
output to my PC).
** Attachment added: initctl list
@Clint:
I did test your proposal in Maverick.
Before editing the stop scripts:
fgrep stop on runlevel /etc/init/*.conf
/etc/init/acpid.conf:stop on runlevel [!2345]
/etc/init/anacron.conf:stop on runlevel [!2345]
/etc/init/apport.conf:stop on runlevel [!2345]
/etc/init/atd.conf:stop on runlevel
I took you literally and canged all [!2345], not the others:
The remaining now are:
fgrep stop on runlevel /etc/init/*.conf
/etc/init/rc.conf:stop on runlevel [!$RUNLEVEL]
/etc/init/rcS.conf:stop on runlevel [!S]
/etc/init/rc-sysinit.conf:stop on runlevel
/etc/init/tty2.conf:stop on runlevel
On Thu, 2010-12-23 at 22:07 +, ingo wrote:
I took you literally and canged all [!2345], not the others:
The remaining now are:
fgrep stop on runlevel /etc/init/*.conf
/etc/init/rc.conf:stop on runlevel [!$RUNLEVEL]
/etc/init/rcS.conf:stop on runlevel [!S]
This doesn't affect Debian as the upstart package in Debian still uses
plain sysv compat and there are no native upstart jobs yet.
A wise decision, good to know.
Thanks,
Ingo
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1
I was working with someone on another issue recently, and he pointed out
a situation where someone had used this:
start on starting rc RUNLEVEL=[06]
to run a specific task before the system shut down.
It got me thinking, should we instead just transition services that need
to start before
On Tue, 2010-12-21 at 12:41 +, Scott James Remnant wrote:
On 20/12/10 18:22, Clint Byrum wrote:
In a message to ubuntu-devel I suggested that we have an abstract job,
'network-services', which most normal (non boot-critical) services
should follow.
@Michael: yes, this should be stop on unmount-filesystem or single-
user (we can create a new event for single-user to make the logic
clearer).
@Clint: I agree that full migration sounds like the best approach. I
have had a few discussions previously with Scott on the idea of abstract
jobs. There
On Tue, 2010-12-21 at 12:41 +, Scott James Remnant wrote:
General note: ubuntu-devel is *NOT* the correct list to discuss Upstart
changes unless they're unique to Ubuntu.
Wouldn't it be fair to inform Debian about those problems before they release
Squeeze?
(tough I never observed it on
After discussion with Scott, the best short-term solution would seem to
be:
1) Modify /etc/init.d/umountfs to call the following in do_stop before
calling umount/swapoff:
initctl emit unmount-filesystem
2) Modify /etc/init.d/umountroot to call the following in do_stop before
calling
2010/12/20 James Hunt 688...@bugs.launchpad.net:
3) Modify all upstart configs for services which are slow to stop such that
they stop on unmount-filesystem,
rather than stop on runlevel [016].
- What about single user mode? I guess when switching to runlevel 1 we
want to stop services
On Mon, 2010-12-20 at 12:50 +, James Hunt wrote:
After discussion with Scott, the best short-term solution would seem to
be:
1) Modify /etc/init.d/umountfs to call the following in do_stop before
calling umount/swapoff:
initctl emit unmount-filesystem
2) Modify
So I've done some more thinking about this, and I had a bit of an aha!
moment.
While we *should* in fact stop using 'stop on runlevel [016]' or 'stop
on runlevel [!2345]', I think we can solve this without touching all of
those jobs.
/etc/init.d/sendsigs has this code:
# Upstart jobs
** Patch added: lp688541.diff
https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/688541/+attachment/1767453/+files/lp688541.diff
** Changed in: sysvinit (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Also attaching the bash script that I used to test this, which simulates
a process taking a long time on SIGTERM without forking.. it *should*
work with sleep too, given the sendsigs change I posted, but when that
change is not there.. sendsigs kills the sleeps and ruins all the fun.
Below is the
2010/12/16 Clint Byrum cl...@fewbar.com:
/etc/init.d/sendsigs has this code:
# Upstart jobs have their own stop on clauses that sends
# SIGTERM/SIGKILL just like this, so if they're still running,
# they're supposed to be
for pid in $(initctl list | sed -n -e
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
Ubuntu-server-bugs mailing list
On Thu, 2010-12-16 at 15:45 +, Michael Biebl wrote:
2010/12/16 Clint Byrum cl...@fewbar.com:
I'm attaching a debdiff that solves the race as far as I can tell,
though I think it needs a good long look, since it could mean shutdowns
hang for a long time waiting (I'm especially
Hmm, I am wondering now if this bug is the same thing.
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/616287
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
Note that there is one incorrect assumption, which is that sendsigs will
never kill any upstart jobs.
In fact, it does make one attempt to kill -9 any still running upstart
jobs:
if [ -z $alldead ] ; then
log_action_begin_msg Killing all remaining processes
And, whoops, I just re-read that, its using killall5's -o to still omit
those processes.
Please disregard that last message then.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
2010/12/14 Clint Byrum cl...@fewbar.com:
I do think the appropriate fix is to have umountfs emit an 'unmounting-
filesystems' event and anything that does a 'start on local-filesystems'
or 'start on filesystem' should also 'stop on unmounting-filesystems',
What do you do about services which
Great point, thanks for pointing that out!
rc-sysinit does not start until filesystem and net-device-up IFACE=lo,
and so, runlevel 2, which is reached by callint rc-sysinit, implies all
of the services you mention. It is important to point out that we must
include any of those *implied* to be
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
Ubuntu-server-bugs mailing list
What would be the general approach to express shut down on runlevel
0/1/6 before the disks go away in terms of upstart triggers? Once
there's an approach, pleaes hand over to canonical-server. Thanks!
** Changed in: mysql-5.1 (Ubuntu)
Status: New = Triaged
** Changed in: mysql-5.1
Suggestion: make umountfs wait for all upstart jobs to finish.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
2010/12/10 Ante Karamatić iv...@grad.hr:
Suggestion: make umountfs wait for all upstart jobs to finish.
Doesn't that conflict though with what is written in
/etc/init.d/sendsigs:
# Upstart jobs have their own stop on clauses that sends
# SIGTERM/SIGKILL just like this, so if
Ante, good eyes there. That statement is a little misleading, that if
they're still running, they're supposed to be, as this assumes there
was an event somewhere between the running system, and runlevel [016],
which to my knowledge, there isn't.
I'm a little confused as to why umountfs is still
James, could you take a look at this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
Ubuntu-server-bugs
47 matches
Mail list logo
