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

pidfile has been removed after call mysqld -V

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.5.33a
    • Fix Version/s: N/A
    • Component/s: None
    • Labels:
      None
    • Environment:
      version is 5.5.27

      Description

      we got maria install in many servers so we try to reproduce in test environment and it works :

      uname -a
      Linux siucidmdbsb2 2.6.32-279.14.1.el6.x86_64 #1 SMP Mon Oct 15 13:44:51 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
      [mysql@siucidmdbsb2 INT db]$ ls -la
      total 170080
      drwxr-x--- 6 mysql mysql      4096 Nov 13 14:44 .
      drwxr-xr-x 4 root  root       4096 Dec 18  2012 ..
      -rw-rw---- 1 mysql mysql     16384 Nov  7 10:48 aria_log.00000001
      -rw-rw---- 1 mysql mysql        52 Nov  7 10:48 aria_log_control
      -rw-rw---- 1 mysql mysql 163577856 Nov 13 14:41 ibdata1
      -rw-rw---- 1 mysql mysql   5242880 Nov 13 14:41 ib_logfile0
      -rw-rw---- 1 mysql mysql   5242880 Nov 12 13:48 ib_logfile1
      -rw-rw---- 1 mysql mysql     16384 Aug 12 16:15 ib_lru_dump
      drwx------ 2 mysql mysql     12288 Oct  2 17:03 jbilling
      -rw-rw---- 1 mysql mysql       109 Nov 13 14:41 master.info
      drwx------ 2 mysql mysql      4096 Mar 13  2013 mysql
      drwx------ 2 mysql mysql     20480 Nov 12 10:39 nevisidm
      drwx------ 2 mysql mysql      4096 Mar 13  2013 performance_schema
      -rw-rw-r-- 1 mysql mysql         5 Nov 13 14:44 siucidmdbsb2.pid
      [mysql@siucidmdbsb2 INT db]$ mysqld -V
      mysqld  Ver 5.5.27-MariaDB-log for Linux on x86_64 (MariaDB Server)
      [mysql@siucidmdbsb2 INT db]$ ls -la
      total 170076
      drwxr-x--- 6 mysql mysql      4096 Nov 13 14:44 .
      drwxr-xr-x 4 root  root       4096 Dec 18  2012 ..
      -rw-rw---- 1 mysql mysql     16384 Nov  7 10:48 aria_log.00000001
      -rw-rw---- 1 mysql mysql        52 Nov  7 10:48 aria_log_control
      -rw-rw---- 1 mysql mysql 163577856 Nov 13 14:41 ibdata1
      -rw-rw---- 1 mysql mysql   5242880 Nov 13 14:41 ib_logfile0
      -rw-rw---- 1 mysql mysql   5242880 Nov 12 13:48 ib_logfile1
      -rw-rw---- 1 mysql mysql     16384 Aug 12 16:15 ib_lru_dump
      drwx------ 2 mysql mysql     12288 Oct  2 17:03 jbilling
      -rw-rw---- 1 mysql mysql       109 Nov 13 14:41 master.info
      drwx------ 2 mysql mysql      4096 Mar 13  2013 mysql
      drwx------ 2 mysql mysql     20480 Nov 12 10:39 nevisidm
      drwx------ 2 mysql mysql      4096 Mar 13  2013 performance_schema
      

      So as u can see pidfile has been removed also with mysqld --help same results.
      we use DTRACE and we see this:

      unlink("/data/mariadb/db/siucidmdbsb2.pid") = 0
      write(1, "mysqld  Ver 5.5.27-MariaDB-log f"..., 68) = 68
      

      installation is by RPM by puppet

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            Hi,
            Does it mean you haven't had the problem for a while and just got it now again?

            Show
            elenst Elena Stepanova added a comment - Hi, Does it mean you haven't had the problem for a while and just got it now again?
            Hide
            maxdix massimo disaro added a comment -

            no, actually means we resolve the problem to upgrade the version and on 5534 we did not see this bug.

            For a new project has been set a new 'cluster' , and because of puppet config we end up to install 5527. Where the problem is happening permanent and we reproduce.

            Show
            maxdix massimo disaro added a comment - no, actually means we resolve the problem to upgrade the version and on 5534 we did not see this bug. For a new project has been set a new 'cluster' , and because of puppet config we end up to install 5527. Where the problem is happening permanent and we reproduce.
            Hide
            elenst Elena Stepanova added a comment -

            Please let us know whether upgrade to 5.5.34 resolved the problem on the new cluster as well.

            Show
            elenst Elena Stepanova added a comment - Please let us know whether upgrade to 5.5.34 resolved the problem on the new cluster as well.
            Hide
            maxdix massimo disaro added a comment -

            yes the problem with 55.34 is not there anymore.

            Show
            maxdix massimo disaro added a comment - yes the problem with 55.34 is not there anymore.
            Hide
            elenst Elena Stepanova added a comment -

            While we don't know what exactly fixed the problem in 5.5.34, since we could never reproduce it locally, I'm closing it as fixed for now. If somebody ever encounters it again, the bug can be re-opened.

            Show
            elenst Elena Stepanova added a comment - While we don't know what exactly fixed the problem in 5.5.34, since we could never reproduce it locally, I'm closing it as fixed for now. If somebody ever encounters it again, the bug can be re-opened.

              People

              • Assignee:
                elenst Elena Stepanova
                Reporter:
                maxdix massimo disaro
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: