Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7448

mtr may leave stale mysqld

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 5.5.41, 10.0.15, 10.1.3
    • 5.5.42, 10.0.16, 10.1.3
    • Tests
    • 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

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-7659 buildbot may leave stale mysqld

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Stalled

          Activity

            Ascending order - Click to sort in descending order
            svoj Sergey Vojtovich added a comment -

            serg, please review fix for this bug.

            svoj Sergey Vojtovich added a comment - serg , please review fix for this bug.
            svoj Sergey Vojtovich added a comment - 

            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.

            svoj Sergey Vojtovich added a comment - 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.

            People

              svoj Sergey Vojtovich
              svoj Sergey Vojtovich
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.