1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MariaDB/MySQL backup not working (Site works fine)

Discussion in 'Server Configuration and Hosting' started by faeronsayn, Nov 2, 2014.

  1. faeronsayn

    faeronsayn Well-Known Member

    Trying to back up my database for one of my xenForo forums, and no matter what I do I get these errors.
    I've tried doing innodb force restores with 1, 2, 3 with similar errors (I might have been doing them wrong).
    In any case, I feel like this seems to be the more appropriate forum to post it in.

    Here is one instance of the errors that I get:

    Code:
    InnoDB: Error: tried to read 16384 bytes at offset 0 819200.
    InnoDB: Was only able to read 0.
    141102 14:35:53 InnoDB: Operating system error number 5 in a file operation.
    InnoDB: Error number 5 means 'Input/output error'.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
    InnoDB: File operation call: 'read'.
    InnoDB: Cannot continue operation.
    141102 14:35:53 mysqld_safe Number of processes running now: 0
    141102 14:35:53 mysqld_safe mysqld restarted
    141102 14:35:53 InnoDB: The InnoDB memory heap is disabled
    141102 14:35:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    141102 14:35:53 InnoDB: Compressed tables use zlib 1.2.3
    141102 14:35:53 InnoDB: Using Linux native AIO
    141102 14:35:53 InnoDB: Initializing buffer pool, size = 2.0G
    141102 14:35:53 InnoDB: Completed initialization of buffer pool
    141102 14:35:53 InnoDB: highest supported file format is Barracuda.
    InnoDB: Log scan progressed past the checkpoint lsn 11183392847
    141102 14:35:53 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 11183394185
    141102 14:35:53 InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percents: 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
    InnoDB: Apply batch completed
    141102 14:35:54 InnoDB: Waiting for the background threads to start
    141102 14:35:55 Percona XtraDB (http://www.percona.com) 5.5.38-MariaDB-35.2 started; log sequence number 11183394185
    141102 14:35:55 [Note] Plugin 'FEEDBACK' is disabled.
    141102 14:35:55 [Note] Server socket created on IP: '0.0.0.0'.
    141102 14:35:55 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
    141102 14:35:55 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
    141102 14:35:55 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
    141102 14:35:55 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
    141102 14:35:55 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.39-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
    141102 14:35:59 [ERROR] mysqld: Table './shadygam_forum/xf_session' is marked as crashed and should be repaired
    141102 14:35:59 [Warning] Checking table: './shadygam_forum/xf_session'
    
     
  2. Slavik

    Slavik XenForo Moderator Staff Member

    run mysql_upgrade and then run mysqlcheck --all-databases
     
    HWS likes this.
  3. faeronsayn

    faeronsayn Well-Known Member

    mysql_upgrade and mysqlcheck fails when it gets to that specific database
     
  4. Slavik

    Slavik XenForo Moderator Staff Member

    Whats the error reporting for it?
     
  5. faeronsayn

    faeronsayn Well-Known Member

    This is the error I see

    Code:
    InnoDB: Error: tried to read 16384 bytes at offset 0 819200.
    InnoDB: Was only able to read 0.
    141103 13:45:11  InnoDB: Operating system error number 5 in a file operation.
    InnoDB: Error number 5 means 'Input/output error'.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
    InnoDB: File operation call: 'read'.
    InnoDB: Cannot continue operation.
    141103 13:45:11 mysqld_safe Number of processes running now: 0
    141103 13:45:11 mysqld_safe mysqld restarted
    141103 13:45:11 InnoDB: The InnoDB memory heap is disabled
    141103 13:45:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    141103 13:45:11 InnoDB: Compressed tables use zlib 1.2.3
    141103 13:45:11 InnoDB: Using Linux native AIO
    141103 13:45:11 InnoDB: Initializing buffer pool, size = 2.0G
    141103 13:45:11 InnoDB: Completed initialization of buffer pool
    141103 13:45:11 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!
    141103 13:45:11  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...
    141103 13:45:12  InnoDB: Waiting for the background threads to start
    141103 13:45:13 Percona XtraDB (http://www.percona.com) 5.5.38-MariaDB-35.2 started; log sequence number 11203053478
    141103 13:45:13 [Note] Plugin 'FEEDBACK' is disabled.
    141103 13:45:13 [Note] Server socket created on IP: '0.0.0.0'.
    141103 13:45:13 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
    141103 13:45:13 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
    141103 13:45:13 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
    141103 13:45:13 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
    141103 13:45:13 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.39-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
    
    
     
  6. Solidus

    Solidus Well-Known Member

    Is innodb_force_recovery in your my.cnf?
     
  7. faeronsayn

    faeronsayn Well-Known Member

    I've had that and it didn't work (I might have been doing it wrong).
     
  8. Slavik

    Slavik XenForo Moderator Staff Member

    Keep increment the number until it works is all I can imagine, maybe its something @eva2000 or @MattW has run into before.
     
  9. SneakyDave

    SneakyDave Well-Known Member

    Have you run out of space?
     
  10. faeronsayn

    faeronsayn Well-Known Member

    I've got lots of space, that's definitely not an issue. Considering, that all my other databases have no trouble being exported.
     
  11. alegeek

    alegeek Member

    Possible your tmp directory is filling up?
     

Share This Page