** Changed in: mysql-dfsg-5.0 (Debian)
Status: New = Confirmed
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
** Branch linked: lp:ubuntu/karmic/mysql-dfsg-5.0
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
** Branch linked: lp:ubuntu/jaunty-updates/mysql-dfsg-5.0
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
** Changed in: mythbuntu
Status: Triaged = Fix Released
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
** Changed in: mysql-dfsg-5.0 (Ubuntu Jaunty)
Status: Fix Released = Fix Committed
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Do not change bug statuses without explanation.
** Changed in: mysql-dfsg-5.0 (Ubuntu Jaunty)
Status: Fix Committed = Fix Released
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of
** Changed in: mysql-dfsg-5.0 (Ubuntu Karmic)
Status: Triaged = In Progress
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug was fixed in the package mysql-dfsg-5.0 -
5.1.30really5.0.83-0ubuntu1
---
mysql-dfsg-5.0 (5.1.30really5.0.83-0ubuntu1) karmic; urgency=low
[ Norbert Tretkowski ]
* New upstream release.
[ Mathias Gug ]
* Merge from debian unstable, remaining changes:
+
** Changed in: mysql-dfsg-5.0 (Ubuntu Jaunty)
Status: Incomplete = Fix Released
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thanks to the careful and detailed analysis of Stephane in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527623, it seems that
there are two issues:
==
SIGHUP, SIGQUIT, SIGINT ignored after package installation
After an apt-get install
** Changed in: mysql-dfsg-5.0 (Ubuntu Jaunty)
Importance: Undecided = Medium
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0
that patch is still wrong.
The first time a HUP is received, we run the code in the trap
and call wait which will wait for both the refresh command and
the mysqld one.
But we won't return from that trap until mysqld dies, and in the
trap the HUP signal is blocked, which means any subsequent
HUP
** Tags added: verification-done
** Tags removed: verification-needed
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
This bug was fixed in the package mysql-dfsg-5.0 -
5.1.30really5.0.75-0ubuntu10.2
---
mysql-dfsg-5.0 (5.1.30really5.0.75-0ubuntu10.2) jaunty-proposed; urgency=low
* debian/patches/38_scripts__mysqld_safe.sh__signals.dpatch: wait in the
SIGHUP trap to avoid killing an existing
Short answer: Fixed.
I was running on Mythbuntu 8.10 and didn't have these errors.
Fresh load of Mythbuntu 9.04RC, got the 'hanging' messages in syslog and
database errors ending with
'MySQL server has gone away' in mythbackend.log. These messages are gone now.
Thank you.
--
mysqld_safe
Proposed works for me. No sign of mysql trouble in any of the logs.
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
Accepted mysql-dfsg-5.0 into jaunty-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!
** Changed in: mysql-dfsg-5.0
I'm not sure if I'm late to the party or not here... but on the off
chance that it would be helpful, I threw together a program to print out
the source process ID for a SIGHUP signal. I have attached the source
to this bug. Very simple to use... in this case:
1. mv mysqld_safe mysqld_safe_real
I just tried Marc's signal tracker: Here is the output after boot:
Executing (/usr/bin/mysqld_safe_real )
signo: [1], errno: [0], code: [128], pid: [0], uid: [0]
It looks like a code of 0x80 corresponds to a code of SI_KERNEL.
What does the kernel have against mysqld_safe?
--
mysqld_safe
** Description changed:
--Impact--
I'm running mythtv on jaunty with mysql-server-5.0 version
5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts,
then mysql restarts and mythtv gets confused.
This is caused by some portions of a debian patch that is applied on
** Bug watch added: Debian Bug tracker #527623
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527623
** Also affects: mysql-dfsg-5.0 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527623
Importance: Unknown
Status: Unknown
--
mysqld_safe thinks mysqld has
** Changed in: mysql-dfsg-5.0 (Debian)
Status: Unknown = New
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
Hi Will,
On Mon, May 11, 2009 at 01:35:31AM -, Will Uther wrote:
I also looked in the logs to see what was happening on boot with the
change and I noticed:
May 10 11:02:55 willvo sshd[2981]: Received signal 15; terminating.
May 10 11:02:55 willvo ntpd[3721]: ntpd exiting on signal 15
Agreed. It seems that the latter has been identified and a workaround is
described in this bug. I think the former should also be well understood
before pushing anything to a *stable* release. A known broken behaviour
with a workaround is better then pushing an update that breaks existing
On Mon, May 11, 2009 at 08:33:20PM -, Mario Limonciello wrote:
Regardless of what is sending a SIGHUP to mysqld_safe, it should be a
supported scenario to allow such signals to be sent to system daemons.
It's common for SIGHUP to be used to ask to reload configuration files
when the
Here is another way to fix the issue: add a wait to the trap:
-+trap '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf
refresh' 1 # HUP
++trap '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf refresh
wait' 1 # HUP
This patch doesn't remove an existing
Mathias:
Spectacular idea. I just manually tried it on my test system that i've been
using to investigate this bug. It solves the problems entirely.
On Mon, May 11, 2009 at 22:04, Mathias Gug math...@ubuntu.com wrote:
Here is another way to fix the issue: add a wait to the trap:
-+trap
On 12/05/2009, at 2:16 AM, Mathias Gug wrote:
Thanks for figuring this out. This is probably the root cause of the
issue. I've seen similar behavior with sshd - could you describe your
network configuration? Are you using network-manager or
/etc/network/intrefaces? Are you using a static
I patched mysqld_safe directly based on Mario's diff (and replace the
wait that I had removed). This fixes the problem for me.
I also looked in the logs to see what was happening on boot with the
change and I noticed:
May 10 11:02:55 willvo sshd[2981]: Received signal 15; terminating.
May 10
Installed a new update today, Lots of mysqld messages in the log file, none
appear to be errors, all appear to occur when mysqld starts, none occurred when
mythtv-backend started 3 minutes later.
Seems the bug may be fixed.
--
mysqld_safe thinks mysqld has crashed when it hasn't
Probably no point in me doing this but I spent the evening trying to get
the mysqld process hanging with the patch installed and never could.
I'm using network manager and the WaitForHDHomeRun script and I'm not
seeing any trouble.
I forgot to mention - before the patch I occasionally saw mysqld
I had exactly the same bugs - Mythbuntu 9.04, adding Mario's PPA (no
other modifications) fixed it.
Thank you very much Mario!
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Thanks for taking to prepare a debdiff and conduct some testing. However
I'm not comfortable with releasing an update that changes the signal
handling, especially removing one.
I'd like to understand *why* is mysqld crashing in the first place. It
seems that mythbackend is making mysqld crash.
There are two problems at stake here actually:
1) something is sending HUP to mysqld_safe. That's not been determined
yet. Clearly it's some root process that is doing it. It can't be
mythbackend because it doesn't run as root.
2) mysqld_safe is not properly handling the HUP. When the trap
Mathias has said this package shouldn't go to -updates in its current
state, so I'm marking it verification-failed for now. Mathias, when
you've had time to reevaluate the package and if you conclude it's
suitable, please set it back to verification-needed; or if you upload a
new version of the
Mathias,
i can trigger this problem on my laptop which is *not* running
mythbackend by simply issuing 'sudo killall -HUP mysqld_safe'. So it's
not related to MythTV.
In fact, if you issue 'mysqladmin refresh' as done by mysqld_safe when
it catches a SIGHUP, mysqld will *not* crash. See Mario's
See this thread
http://ubuntuforums.org/showthread.php?p=7233888#post7233888
superm1 suggested I enable the Jaunty Proposed repository to see if it
fixed this problem, it did not. I still get this in the log:
May 7 12:43:01 AComputer mysqld_safe[4938]: Number of processes running now: 1
May 7
Strange. I set everything back to default except I didn't use my
SxxWaitForHDHomeRun script. I manually configured the network and had
Network Manager shut off. I verified I was getting the problem, then
applied the patch. I haven't had a single mysqld process hanging since
the patch.
I
Accepted mysql-dfsg-5.0 into jaunty-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!
** Changed in: mysql-dfsg-5.0
Martin,
Is it a good enough test to install over Mario's PPA or would you prefer
I revert mysql, reproduce the error, then apply the proposed over the
top of it?
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification
Added jaunty-proposed and did a partial update of mysql. No problems
found with mythbuntu. I you want a test on a clean install let me know.
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a
Thanks for making that build available on your ppa Mario. I just
installed it and it seems to have fixed my problems. I can reboot and I
don't get the mysqld errors or the behavior of my recorded schedules not
being loaded into the mythbackend.
One surprise is that it also seems to fix a
** Also affects: mysql-dfsg-5.0 (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: mysql-dfsg-5.0 (Ubuntu Karmic)
Importance: Undecided
Status: Confirmed
** Changed in: mysql-dfsg-5.0 (Ubuntu Jaunty)
Status: New = Confirmed
--
mysqld_safe thinks
** Description changed:
- Binary package hint: mysql-server-5.0
+ --Impact--
+ I'm running mythtv on jaunty with mysql-server-5.0 version
5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts,
then mysql restarts and mythtv gets confused.
- I'm running mythtv on jaunty
Thanks, Mario. Assigned to Canonical server team for review.
** Changed in: mysql-dfsg-5.0 (Ubuntu Karmic)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug
I'm testing the patch. Works Great! Mario really is Super.
I'm a Mythbuntu 9.04 RC install that was fully updated as of yesterday
(before the PPA test fix). I restored everything to the error state
and verified the error still exists. The error state does have the
problem. (mythbackend log
I've got a debdiff that i'd like to propose as a solution to this, but I
would like to get some wider testing and feedback with it before
uploading it to -proposed.
It's attached, and I have a test build on my PPA (version
5.1.30really5.0.75-0ubuntu10.1~ppa1) at
I see that Mythbuntu 9.04 has been released and there is no mention of
this problem in the release notes
(http://www.mythbuntu.org/9.04/Release_notes).
I am still having this problem. After every reboot I have to manually
restart the mythtv backend for my recording schedules to be read in from
This should definitely be added to the release notes or fixed, but it
appears that the problem can be resolved by performing the workaround in
the original description.
Also, just doing something to interact with the database (like schedule
a dummy recording), always worked to fix the problem for
On a fresh install of mythbuntu 9.04 I get this problem. The fix
described above does not work for me. (It doesn't change the behavior
at all as far as I can tell).
My situation is more complex since I use a HDHomeRun tuner (so I need
the network working as well). Here is what I've tried:
1)
50 matches
Mail list logo
