we have seen two deadlocks of mysqld in the past two days, one with
rt3.0.3rc4 and one with rt3.0.3 release.
conf is apache 1.3, mysql 3, modperl1, DBD::mysql 2.1027, Searchbuilder 0.86
symptom: rt hangs and email to rt bounces
a try to trace the mysqld restarts it and after that rt3 runs fine again
(for some time).
In rt.log we have entries like:
[Wed Jun 25 16:30:37 2003] [warning]: DBIx::SearchBuilder error:Can’t
connect to local MySQL server through socket ‘/var/run/mysqld/
mysqld.sock’ (111)
Jesse, I will send you personally a part of the mysql.log file just before
mysqld stops working. A series of Queries like
SELECT ACL.id from ACL, Groups, Principals, CachedGroupMembers WHERE
(ACL.RightName = ‘SuperUser’ OR ACL.RightName = ‘SeeQueue’) AND
Principals.Disabled = 0 AND CachedGroupMembers.Disabled = 0 AND
Principals.id = Groups.id AND Principals.id = CachedGroupMembers.GroupId
AND CachedGroupMembers.MemberId = ‘166’ AND ( ACL.ObjectType = ‘RT::System’
OR (ACL.ObjectType = ‘RT::Queue’ AND ACL.ObjectId = ‘3’)) AND ( (
ACL.PrincipalId = Principals.id AND ACL.PrincipalType = ‘Group’ AND (Groups
.Domain = ‘SystemInternal’ OR Groups.Domain = ‘UserDefined’ OR
Groups.Domain = ‘ACLEquivalence’ OR Groups.Domain = ‘Personal’)) OR (
((Groups.Domain = ‘RT::Queue-Role’ AND Groups.Instance = ‘3’) ) AND
Groups.Type = ACL.PrincipalType AND Groups.Id = Principals.id AND
Principals.PrincipalType = ‘Group’) ) LIMIT 1
–Am Mittwoch, 25. Juni 2003 22:47 Uhr -0700 schrieb Robert Spier rspier@pobox.com:
mysql4 is highly recommended.
yes I know but we have mysqld running for other dbs as well and did not
upgrade yet.
What platform are you running on?
Debian Linux woody with manual installed perl 5.8.0
Is there anything in the mysql error log?
there is only the process id of the killed processes and the time stamp for
restart. I for myself did not restart apache and my admin said he tried to
trace the processes and did not restart it manually
Is the mysql process still there? What state is it in?
there is only the process id of the killed processes and the time stamp for
restart. I for myself did not restart apache and my admin said he tried to
trace the processes and did not restart it manually
What do you mean “only the process id” ?? Is there a mysql crash
message?
At Thu, 26 Jun 2003 16:55:29 +0100,
Daniel Foster wrote:
mysql4 is highly recommended.
Is this for resons of performace, stability or both?
Performance, stability AND functionality
Fair enough - MySQL 4 it is then!
Next question is FastCGI or mod_perl?
mod_perl has the advantage of tighter integration into Apache so that
it can terminate disconnected connections, aborting a database query,
etc… but FastCGI is often easier to setup.
I’d probably use mod_perl in production, but FastCGI in development.
But really this is a “what works best for you in your environment.”
