Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5.41, 10.0.15, 10.1.3
-
None
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
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.