[MDEV-7448] mtr may leave stale mysqld Created: 2015-01-13  Updated: 2015-03-04  Resolved: 2015-01-15

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 5.5.41, 10.0.15, 10.1.3
Fix Version/s: 5.5.42, 10.0.16, 10.1.3

Type: Bug Priority: Major
Reporter: Sergey Vojtovich Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7659 buildbot may leave stale mysqld Closed
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

Happens time to time on bb causing tests of further builds to fail. Sometimes it happens immediately after bb exception.

At least one way to leave stale mysqld is easily reproducible:
1. ssh to a remote host
2. run mtr and wait till tests are started
3. close session: ~.
4. get back to the host and observe stale mysqld

 Comments   
Comment by Sergey Vojtovich [ 2015-01-14 ]

serg, please review fix for this bug.

Comment by Sergey Vojtovich [ 2015-01-15 ] 

revno: 4406
 
revision-id: svoj@mariadb.org-20150114135038-v50g2cul4vce63h8
 
parent: nirbhay@mariadb.com-20150114232423-ohkxk5njulzqlw20
 
committer: Sergey Vojtovich <svoj@mariadb.org>
 
branch nick: 5.5
 
timestamp: Wed 2015-01-14 17:50:38 +0400
 
message:
 
  MDEV-7448 - mtr may leave stale mysqld
 
 
 
  Let mtr handle SIGHUP the same way as SIGINT. This solves stale mysqld processes
 
  left after broken/closed ssh connection.

Generated at Thu Feb 08 07:19:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.