I stated this only because it stopped once I retained only one instance running. I previously had two and was experiencing this issue.
Is this function supposed to be able to run in more than one instance? I ask because I am not super talented in writing perl matching syntax and cannot always wrap all desired events, triggers, etc. into one elegant line of code. Also, would other pt- functions run concurrently and nicely together?
________________________________
From: Baron Schwartz <email address hidden>
To: <email address hidden>
Sent: Thursday, March 8, 2012 2:07 PM
Subject: [Bug 941469] Re: pt-kill: error getting processlist; mysql server gone away
Steve, do you have reason to believe that one instance was killing the
other?
I think the bug report could also be summarized as "pt-kill doesn't
reconnect if its connection is lost." OK?
Title:
pt-kill: error getting processlist; mysql server gone away
Status in Percona Toolkit:
New
Bug description:
Percona Toolkit v.2.0.3
Mysql: mysqld Ver 5.0.92-community-log for unknown-linux-gnu on x86_64 (MySQL Community Edition (GPL))
When pt-kill is daemonized and then viewing its log, find this error
message:
Error getting SHOW PROCESSLIST: DBD::mysql::st execute failed: MySQL
server has gone away [for Statement "SHOW FULL PROCESSLIST"] at
/usr/bin/pt-kill line 3633.
Baron, I agree with your updated bug description.
I stated this only because it stopped once I retained only one instance running. I previously had two and was experiencing this issue.
Is this function supposed to be able to run in more than one instance? I ask because I am not super talented in writing perl matching syntax and cannot always wrap all desired events, triggers, etc. into one elegant line of code. Also, would other pt- functions run concurrently and nicely together?
_______ _______ _______ _______ ____
From: Baron Schwartz <email address hidden>
To: <email address hidden>
Sent: Thursday, March 8, 2012 2:07 PM
Subject: [Bug 941469] Re: pt-kill: error getting processlist; mysql server gone away
Steve, do you have reason to believe that one instance was killing the
other?
I think the bug report could also be summarized as "pt-kill doesn't
reconnect if its connection is lost." OK?
-- /bugs.launchpad .net/bugs/ 941469
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
pt-kill: error getting processlist; mysql server gone away
Status in Percona Toolkit:
New
Bug description: community- log for unknown-linux-gnu on x86_64 (MySQL Community Edition (GPL))
Percona Toolkit v.2.0.3
Mysql: mysqld Ver 5.0.92-
When pt-kill is daemonized and then viewing its log, find this error
message:
Error getting SHOW PROCESSLIST: DBD::mysql::st execute failed: MySQL
server has gone away [for Statement "SHOW FULL PROCESSLIST"] at
/usr/bin/pt-kill line 3633.
Thank you
To manage notifications about this bug go to: /bugs.launchpad .net/percona- toolkit/ +bug/941469/ +subscriptions
https:/