IdentifiantMot de passe
Loading...
Mot de passe oublié ?Je m'inscris ! (gratuit)
Navigation

Inscrivez-vous gratuitement
pour pouvoir participer, suivre les réponses en temps réel, voter pour les messages, poser vos propres questions et recevoir la newsletter

Administration MySQL Discussion :

[Centreon] MySQL Daemon failed to start


Sujet :

Administration MySQL

  1. #1
    Membre à l'essai
    Homme Profil pro
    Administrateur systèmes et réseaux
    Inscrit en
    Mai 2014
    Messages
    30
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Localisation : France, Rhône (Rhône Alpes)

    Informations professionnelles :
    Activité : Administrateur systèmes et réseaux
    Secteur : High Tech - Opérateur de télécommunications

    Informations forums :
    Inscription : Mai 2014
    Messages : 30
    Points : 10
    Points
    10
    Par défaut [Centreon] MySQL Daemon failed to start
    Bonjour à tous,

    J'ai un énorme souci depuis un arrêt critique de Centreon. Mysql ne veut plus se lancer. Voici le diag:


    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
     
        /etc/init.d/mysqld start
        [root@srv-centreon ~]# /etc/init.d/mysqld start
        MySQL Daemon failed to start.
        Démarrage de mysqld :                       [ÉCHOUÉ]

    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
        nano /etc/my.cnf
        [mysqld]
        ##### OPTIMIZE FOR CENTREON #####
        innodb_file_per_table
     
        open-files-limit = 32000
     
        key_buffer_size = 256M
        sort_buffer_size = 32M
        join_buffer_size = 4M
        thread_cache_size = 64
        read_buffer_size = 512K
        read_rnd_buffer_size = 256K
        max_allowed_packet = 8M
     
        # For 4 Go Ram
        #innodb_additional_mem_pool_size=512M
        #innodb_buffer_pool_size=512M
     
        # For 8 Go Ram
        #innodb_additional_mem_pool_size=1G
        #innodb_buffer_pool_size=1G
        #################################
        # Settings user and group are ignored when systemd is used (fedora >= 15).
        # If you need to run mysqld under different user or group,
        # customize your systemd unit file for mysqld according to the
        # instructions in http://fedoraproject.org/wiki/Systemd
        user=mysql
     
        datadir=/var/lib/mysql
        socket=/var/lib/mysql/mysql.sock
     
        # Disabling symbolic-links is recommended to prevent assorted security risks
        symbolic-links=0
     
        # Semisynchronous Replication
        # http://dev.mysql.com/doc/refman/5.5/en/replication-semisync.html
        # uncomment next line on MASTER
        ;plugin-load=rpl_semi_sync_master=semisync_master.so
        # uncomment next line on SLAVE
        ;plugin-load=rpl_semi_sync_slave=semisync_slave.so
     
        # Others options for Semisynchronous Replication
        ;rpl_semi_sync_master_enabled=1
        ;rpl_semi_sync_master_timeout=10
        ;rpl_semi_sync_slave_enabled=1
     
        # http://dev.mysql.com/doc/refman/5.5/en/performance-schema.html
        ;performance_schema
     
     
        [mysqld_safe]
        log-error=/var/log/mysqld.log
        pid-file=/var/run/mysqld/mysqld.pid
     
        [client]
        socket=/var/lib/mysql/mysql.sock


    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
        mysql
        Code: [Sélectionner]
        [root@srv-centreon ~]# mysql
        ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)


    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
        restorecon -r /var/lib/mysql
        Code: [Sélectionner]
        restorecon -r /var/lib/mysql
        ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)


    Code : Sélectionner tout - Visualiser dans une fenêtre à part
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    100
    101
    102
    103
        tail /var/log/mysqld.log
        Version: '5.5.34'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi
        141218 07:25:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
        141218  7:25:12 [Note] Plugin 'FEDERATED' is disabled.
        141218  7:25:12 InnoDB: The InnoDB memory heap is disabled
        141218  7:25:12 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
        141218  7:25:12 InnoDB: Compressed tables use zlib 1.2.3
        141218  7:25:12 InnoDB: Using Linux native AIO
        141218  7:25:12 InnoDB: Initializing buffer pool, size = 128.0M
        141218  7:25:12 InnoDB: Completed initialization of buffer pool
        141218  7:25:12 InnoDB: highest supported file format is Barracuda.
        InnoDB: Log scan progressed past the checkpoint lsn 347749954740
        141218  7:25:12  InnoDB: Database was not shut down normally!
        InnoDB: Starting crash recovery.
        InnoDB: Reading tablespace information from the .ibd files...
        InnoDB: Restoring possible half-written data pages from the doublewrite
        InnoDB: buffer...
        InnoDB: Doing recovery: scanned up to log sequence number 347749956708
        InnoDB: 1 transaction(s) which must be rolled back or cleaned up
        InnoDB: in total 92 row operations to undo
        InnoDB: Trx id counter is FD19B00
        141218  7:25:48  InnoDB: Starting an apply batch of log records to the database...
        InnoDB: Progress in percents: 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
        InnoDB: Apply batch completed
        InnoDB: Starting in background the rollback of uncommitted transactions
        141218  7:25:49  InnoDB: Rolling back trx with id FD1997C, 92 rows to undo
        141218  7:25:49  InnoDB: Waiting for the background threads to start
     
        InnoDB: Rolling back of trx id FD1997C completed
        141218  7:25:49  InnoDB: Rollback of non-prepared transactions completed
        141218  7:25:50 InnoDB: 5.5.34 started; log sequence number 347749956708
        141218  7:25:50 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
        141218  7:25:50 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
        141218  7:25:50 [Note] Server socket created on IP: '0.0.0.0'.
        141218  7:25:50 [Note] Event Scheduler: Loaded 0 events
        141218  7:25:50 [Note] /usr/libexec/mysqld: ready for connections.
        Version: '5.5.34'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi
        141218  7:27:23  InnoDB: Assertion failure in thread 2563689360 in file fut0lst.ic line 83
        InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
        InnoDB: We intentionally generate a memory trap.
        InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
        InnoDB: If you get repeated assertion failures or crashes, even
        InnoDB: immediately after the mysqld startup, there may be
        InnoDB: corruption in the InnoDB tablespace. Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
        InnoDB: about forcing recovery.
        06:27:23 UTC - mysqld got signal 6 ;
        This could be because you hit a bug. It is also possible that this binary
        or one of the libraries it was linked against is corrupt, improperly built,
        or misconfigured. This error can also be caused by malfunctioning hardware.
        We will try our best to scrape up some info that will hopefully help
        diagnose the problem, but since we have already crashed, 
        something is definitely wrong and this may fail.
     
        key_buffer_size=268435456
        read_buffer_size=524288
        max_used_connections=5
        max_threads=151
        thread_count=4
        connection_count=4
        It is possible that mysqld could use up to 
        key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1094235 K  bytes of memory
        Hope that's ok; if not, decrease some variables in the equation.
     
        Thread pointer: 0xad25358
        Attempting backtrace. You can use the following information to find out
        where mysqld died. If you see no messages after this, something went
        terribly wrong...
        stack_bottom = ffffffff98cec378 thread_stack 0x30000
        /usr/libexec/mysqld(my_print_stacktrace+0x33)[0x8425c03]
        /usr/libexec/mysqld(handle_fatal_signal+0x42b)[0x82d679b]
        [0x5b2420]
        [0x5b2402]
        /lib/libc.so.6(gsignal+0x50)[0x8e1e30]
        /lib/libc.so.6(abort+0x101)[0x8e3741]
        /usr/libexec/mysqld[0x8563b14]
        /usr/libexec/mysqld[0x8563ceb]
        /usr/libexec/mysqld[0x84d3a84]
        /usr/libexec/mysqld[0x84e96c2]
        /usr/libexec/mysqld[0x84e7cbb]
        /usr/libexec/mysqld[0x84e8798]
        /usr/libexec/mysqld[0x848bc0a]
        /usr/libexec/mysqld[0x84940be]
        /usr/libexec/mysqld(_Z19ha_commit_one_phaseP3THDb+0x85)[0x82daf95]
        /usr/libexec/mysqld(_Z15ha_commit_transP3THDb+0x226)[0x82db296]
        /usr/libexec/mysqld(_Z17trans_commit_stmtP3THD+0x37)[0x8267a87]
        /usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x622)[0x81a6ee2]
        /usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x116)[0x81afd96]
        /usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2719)[0x81b2e79]
        /usr/libexec/mysqld(_Z10do_commandP3THD+0xd8)[0x81b3688]
        /usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0x109)[0x8259529]
        /usr/libexec/mysqld(handle_one_connection+0x4f)[0x825960f]
        /lib/libpthread.so.0[0xa24912]
        /lib/libc.so.6(clone+0x5e)[0x98e7ce]
     
        Trying to get some variables.
        Some pointers may be invalid and cause the dump to abort.
        Query (ffffffff955229f0): is an invalid pointer
        Connection ID (thread ID): 24
        Status: NOT_KILLED
     
        The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
        information that should help you find out what is causing the crash.
    Pouvez-vous m'aider svp ?

    Cordialement,
    Laurent

  2. #2
    Membre à l'essai
    Homme Profil pro
    Administrateur systèmes et réseaux
    Inscrit en
    Mai 2014
    Messages
    30
    Détails du profil
    Informations personnelles :
    Sexe : Homme
    Localisation : France, Rhône (Rhône Alpes)

    Informations professionnelles :
    Activité : Administrateur systèmes et réseaux
    Secteur : High Tech - Opérateur de télécommunications

    Informations forums :
    Inscription : Mai 2014
    Messages : 30
    Points : 10
    Points
    10
    Par défaut
    Impossible pour moi de faire repartir MySQL. J'ai donc finalement refait une nouvelle VM avec un import de la conf via CLAPI.

    Cdt,
    Laurent

Discussions similaires

  1. Timeout error occurred trying to start MySQL Daemon.
    Par omkam dans le forum Administration
    Réponses: 1
    Dernier message: 25/01/2012, 11h24
  2. workflow failed on start
    Par ahmedmido dans le forum SharePoint
    Réponses: 5
    Dernier message: 04/02/2009, 22h31
  3. Réponses: 8
    Dernier message: 23/04/2008, 14h04
  4. Réponses: 1
    Dernier message: 30/01/2008, 23h10
  5. Réponses: 0
    Dernier message: 22/07/2007, 18h42

Partager

Partager
  • Envoyer la discussion sur Viadeo
  • Envoyer la discussion sur Twitter
  • Envoyer la discussion sur Google
  • Envoyer la discussion sur Facebook
  • Envoyer la discussion sur Digg
  • Envoyer la discussion sur Delicious
  • Envoyer la discussion sur MySpace
  • Envoyer la discussion sur Yahoo