• Resolved BeauSanders

    (@beausanders)


    Mariadb has started crashing about every three days and shutting down. This is not only disabling my blog site, but also all of my production apps on that server. I am pasting the mariadb log entries from the latest incident this morning; please advise me on how to correct this matter:

    190823 06:29:57 mysqld_safe Number of processes running now: 0
    190823 06:29:58 mysqld_safe mysqld restarted
    190823 6:29:58 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 10297 …
    190823 6:29:58 InnoDB: The InnoDB memory heap is disabled
    190823 6:29:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    190823 6:29:58 InnoDB: Compressed tables use zlib 1.2.7
    190823 6:29:58 InnoDB: Using Linux native AIO
    190823 6:29:58 InnoDB: Initializing buffer pool, size = 128.0M
    190823 6:29:58 InnoDB: Completed initialization of buffer pool
    190823 6:29:58 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
    190823 6:29:59 InnoDB: Waiting for the background threads to start
    190823 6:30:00 Percona XtraDB (https://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 173395812
    190823 6:30:00 [Note] Plugin ‘FEEDBACK’ is disabled.
    190823 6:30:00 [Note] Server socket created on IP: ‘0.0.0.0’.
    190823 6:30:00 [Note] Event Scheduler: Loaded 0 events
    190823 6:30:00 [Note] /usr/libexec/mysqld: ready for connections.
    Version: ‘5.5.60-MariaDB’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MariaDB Server
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_options’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_options’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_options’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_options’ is marked as crashed and should be repaired
    190823 6:30:00 [Warning] Checking table: ‘./bso@002dblog@002dwp4@002db15/wp_options’
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_data’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_data’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_data’ is marked as crashed and should be repaired
    190823 6:30:00 [Warning] Checking table: ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_data’
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_logs’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_logs’ is marked as crashed and should be repaired
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_logs’ is marked as crashed and should be repaired
    190823 6:30:00 [Warning] Checking table: ‘./bso@002dblog@002dwp4@002db15/wp_spbc_firewall_logs’
    190823 6:30:00 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_post_views’ is marked as crashed and should be repaired
    190823 6:30:00 [Warning] Checking table: ‘./bso@002dblog@002dwp4@002db15/wp_post_views’
    190823 6:30:03 [ERROR] mysqld: Table ‘./bso@002dblog@002dwp4@002db15/wp_cleantalk_sfw’ is marked as crashed and should be repaired
    190823 6:30:03 [Warning] Checking table: ‘./bso@002dblog@002dwp4@002db15/wp_cleantalk_sfw’
    190823 06:30:14 mysqld_safe Number of processes running now:
    190823 09:39:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    190823 9:39:17 [Note] /usr/libexec/mysqld (mysqld 5.5.60-MariaDB) starting as process 12279 …
    190823 9:39:17 InnoDB: The InnoDB memory heap is disabled
    190823 9:39:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    190823 9:39:17 InnoDB: Compressed tables use zlib 1.2.7
    190823 9:39:17 InnoDB: Using Linux native AIO
    190823 9:39:17 InnoDB: Initializing buffer pool, size = 128.0M
    190823 9:39:17 InnoDB: Completed initialization of buffer pool
    190823 9:39:17 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
    190823 9:39:17 InnoDB: Waiting for the background threads to start
    190823 9:39:18 Percona XtraDB (https://www.percona.com) 5.5.59-MariaDB-38.11 started; log sequence number 173395812
    190823 9:39:18 [Note] Plugin ‘FEEDBACK’ is disabled.
    190823 9:39:18 [Note] Server socket created on IP: ‘0.0.0.0’.
    190823 9:39:18 [Note] Event Scheduler: Loaded 0 events
    190823 9:39:18 [Note] /usr/libexec/mysqld: ready for connections.
    Version: ‘5.5.60-MariaDB’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MariaDB Server

    • This topic was modified 5 years, 7 months ago by BeauSanders.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cleantalk may be crashing mariadb’ is closed to new replies.