** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/620441
Title:
MySQL upstart stop job does not cleanly shutdown mysql
To manage notifications about thi
Had some issues getting changes in mysql's upstart script from taking
effect. This demonstrates the issue, using the respawn command as the
example, and a solution.
$ grep respawn /etc/init/mysql.conf
respawn
$ sudo mysqladmin status ; sudo mysqladmin shutdown ; sudo mysqladmin status ;
sleep
We got bitten by this bug and are now checking tables on our DBs.
What's interesting is that we made changes to the mysql upstart script
but they do not seem to be taking effect. In particular:
1) changes to the kill timeout. Changing the value to 300 had no
effect. Even after issuing an "initc
This bug was fixed in the package mysql-dfsg-5.1 - 5.1.41-3ubuntu12.8
---
mysql-dfsg-5.1 (5.1.41-3ubuntu12.8) lucid-proposed; urgency=low
* raising kill timeout to 300 to help avoid table corruption (LP: #620441)
-- Clint ByrumSat, 20 Nov 2010 12:06:00 -0800
** Changed in: mys
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/620441
Title:
MySQL upstart stop job does not cleanly shu
I tried it with a simplified test case with just DELETEing a lot of data
from the table with 1.5mil rows.
The DELETE command took like a minute and a half to return. After it returned,
I immediately did 'stop mysql' and saw the KILL message in the daemon.log after
~5 seconds.
After I started mys
** Branch linked: lp:ubuntu/lucid-proposed/mysql-dfsg-5.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/620441
Title:
MySQL upstart stop job does not cleanly shutdown mysql
Accepted mysql-dfsg-5.1 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!
** Tags added: verification-neede
Sponsored upload of SRU patch to lucid-proposed
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Status: Triaged => Fix Committed
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
--
MySQL upstart stop job does not cleanly shutdown mysql
h
SRU ack, please upload.
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-
paukaija, thanks for the reminder, I just subscribed ubuntu-sru
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Should ubuntu-sru be subscribed to this bug report?
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-serv
** Description changed:
Release: Ubuntu 10.04 LTS
Package Version: 5.1.41-3ubuntu12.6
Stopping a MySQL server can take some time, especially on a busy
database. If mysqld gets killed while having open connections, then
after the next start you will likely have a lot of tables corrupt
** Branch linked: lp:~clint-fewbar/ubuntu/lucid/mysql-dfsg-5.1/increase-
killtimeout
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfs
** Branch linked: lp:ubuntu/mysql-5.1
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailin
This bug should probably be backported to lucid as well. Accepting lucid
nomination.
To move the SRU forward, the next step is to prepare a SRU report as
outlined in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Status: In Progress
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Status: Confirmed => In Progress
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You r
This is awaiting sponsorship, please see the merge proposal.
** Tags added: patch
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-
+1
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubu
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Status: Triaged => Confirmed
** Changed in: mysql-dfsg-5.1 (Ubuntu Maverick)
Assignee: Clint Byrum (clint-fewbar) => (unassigned)
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You recei
Ultimately, I believe what Johan stated previously is correct. If your
mysql daemon is not stopping when you tell it to shutdown, then you
should be concerned.
I've pushed a branch up now that raises kill timeout to 300 seconds.
5 minutes should be long enough for most databases to finish flushin
** Branch linked: lp:~clint-fewbar/ubuntu/maverick/mysql-5.1/increase-
killtimeout
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-
In doing research for this fix, I'm having trouble finding a set of best
practices for upstart jobs in Ubuntu. If anyone has a link or list of
them, please do post here, as I am a bit confused about how to interact
with the user. console output seems a hacky way (user may not have
console if ssh'in
** Changed in: upstart
Status: New => Invalid
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-ser
** Tags added: server-mrs
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubunt
** Tags added: lucid
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-ser
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Assignee: (unassigned) => Clint Byrum (clint-fewbar)
** Also affects: mysql-dfsg-5.1 (Ubuntu Maverick)
Importance: High
Assignee: Clint Byrum (clint-fewbar)
Status: Triaged
--
MySQL upstart stop job does not cleanly shutdown mysql
https:
On Aug 24, 2010, at 1:22 PM, Johan Kiviniemi wrote:
>> Would there be an indication anywhere for users that they're waiting
> on mysql to die?
>
> The ‘stop’ command having not returned yet, and ‘status jobname’ saying
> ‘stopping’.
>
> If a bug in a service causes a stop request not to stop it
> Would there be an indication anywhere for users that they're waiting
on mysql to die?
The ‘stop’ command having not returned yet, and ‘status jobname’ saying
‘stopping’.
If a bug in a service causes a stop request not to stop it, the service
should be fixed.
As for the pseudocode, I don’t thin
On Aug 24, 2010, at 9:50 AM, Scott James Remnant wrote:
> On Tue, 2010-08-24 at 16:23 +, Clint Byrum wrote:
>
>> Can we abort the stop from pre-stop somehow? Otherwise I'm afraid users
>> will either be left waiting forever, or still sending SIGKILL.
>>
> You can call "start" from the pre-s
On Tue, 2010-08-24 at 16:23 +, Clint Byrum wrote:
> Can we abort the stop from pre-stop somehow? Otherwise I'm afraid users
> will either be left waiting forever, or still sending SIGKILL.
>
You can call "start" from the pre-stop script, which will return the job
to a running state.
That bei
Scott, thanks for the suggestion, I hadn't thought of anything like
that.
Can we abort the stop from pre-stop somehow? Otherwise I'm afraid users
will either be left waiting forever, or still sending SIGKILL.
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bu
You can use a "pre-stop" script/exec to send the proper command to stop
mysql and to wait for it to shut down.
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which
upstart definitely needs a way to disable the SIGKILL functionality.
setting
kill timeout 0
Just means instantly kill it, don't even wait for the SIGTERM.
Definitely not the desired behavior.
So this is really a feature request for upstart more than anything.
To be clear, upstart should allow d
** Also affects: upstart
Importance: Undecided
Status: New
--
MySQL upstart stop job does not cleanly shutdown mysql
https://bugs.launchpad.net/bugs/620441
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
Actually the SIGKILL is really always a no go unless a sysadmin decides
to do this manually. An upstart script should never do this
automatically (not even as a feature ;-) ) I can guarantee that in more
than 90% of the cases after a SIGKILL you will have corrupted tables.
With the default config o
Scott, I've experienced problems with SIGKILL's corrupting mysql
databases before, so the workaround given might be a little misleading.
MySQL can actually be stuck waiting on a single query to finish before
it can shut down, and some queries might take *hours*.
That said, its a known tradeoff if
Thank you for your complete bug report.
It would seem this can be fixed in the upstart job with a line like 'kill
timeout 300'. From man 5 init:
| kill timeout INTERVAL
| Specifies the interval between sending the job's main process
|the SIGTERM and SIGKILL signals when st
38 matches
Mail list logo
