lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
eol reached https://wiki.ubuntu.com/Releases
** Changed in: mysql-5.1 (Ubuntu Oneiric)
Status: Triaged = Invalid
** Changed in: mysql-5.1 (Ubuntu Natty)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Importance: Undecided = Medium
** Changed in: upstart (Ubuntu)
Status: New = Triaged
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
**
** Changed in: upstart (Ubuntu Natty)
Status: New = Won't Fix
** Changed in: upstart (Ubuntu Oneiric)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
** Changed in: upstart (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: upstart (Ubuntu Precise)
Status: New = 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've rejected the lucid upload here; 5.1.62 has been uploaded by the
security team to -proposed, so this will need to be rebased on that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
** Description changed:
+ == SRU Justification ==
+
+ = IMPACT =
+
+ Users who have inadvertently broken their mysql configuration will be
+ met with a hung package upgrade process on any updates, and no easy way
+ to see that fact.
+
+ = TEST CASE: =
+
+ 1. sudo apt-get install mysql-server
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.5 (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.5 (Ubuntu Natty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.5 (Ubuntu Oneiric)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
** Changed in: mysql-5.5 (Ubuntu Lucid)
Status: Confirmed = Invalid
** Changed in: mysql-5.5 (Ubuntu Natty)
Status: Confirmed = Invalid
** Changed in: mysql-5.5 (Ubuntu Oneiric)
Status: Confirmed = Invalid
** Description changed:
== SRU Justification ==
= IMPACT =
This bug was fixed in the package mysql-5.5 - 5.5.22-0ubuntu1
---
mysql-5.5 (5.5.22-0ubuntu1) precise; urgency=low
* New upstream release (LP: #965523)
* d/mysql-server-5.5.mysql.upstart: Add respawn limit and code
to exit ping loop if mysqld needs to be respawned. (LP:
** Tags added: precise rls-mgr-p-tracking
--
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/711635
Title:
init: post-start can cause respawn to hang
To manage notifications about
** Also affects: mysql-5.1 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: mysql-5.5 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: mysql-dfsg-5.1 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: mysql-5.1
** Also affects: mysql-5.1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mysql-5.1 (Ubuntu)
Status: New = Triaged
** Changed in: mysql-5.5 (Ubuntu)
Status: New = Triaged
**
I spent some time on this today, and I think that upstart's handling of
respawn + post-start is probably making jobs harder than they need to
be.
In the mysql case, we need to exit the mysqladmin ping loop if the
process goes into 'respawn', so that the process can in fact be
respawned...
One final thought, I'm raising the importance to High. Failing to detect
and report a serious problem in this sort of daemon seems like an
important problem!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
** Branch linked: lp:ubuntu/mysql-5.5
--
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/711635
Title:
init: post-start can cause respawn to hang
To manage notifications about this
** Summary changed:
- mysql update fails waiting for upstart job to respawn
+ init: post-start can cause respawn to hang
** Changed in: upstart
Status: New = Triaged
** Changed in: upstart
Importance: Undecided = Medium
--
You received this bug notification because you are a member
19 matches
Mail list logo
