Don't like ads? PRO users don't see any ads ;-)
Public Pastes
Guest

Untitled

By: a guest on Jun 25th, 2012  |  syntax: None  |  size: 7.42 KB  |  hits: 27  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. Jun 25 09:26:26 backup3 mysqld_safe: Number of processes running now: 0
  2. Jun 25 09:26:26 backup3 mysqld_safe: mysqld restarted
  3. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: The InnoDB memory heap is disabled
  4. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
  5. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: Compressed tables use zlib 1.2.3.4
  6. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: Using Linux native AIO
  7. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: Initializing buffer pool, size = 256.0M
  8. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: Completed initialization of buffer pool
  9. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27 InnoDB: highest supported file format is Barracuda.
  10. Jun 25 09:26:27 backup3 mysqld: InnoDB: The log sequence number in ibdata files does not match
  11. Jun 25 09:26:27 backup3 mysqld: InnoDB: the log sequence number in the ib_logfiles!
  12. Jun 25 09:26:27 backup3 mysqld: 120625  9:26:27  InnoDB: Database was not shut down normally!
  13. Jun 25 09:26:27 backup3 mysqld: InnoDB: Starting crash recovery.
  14. Jun 25 09:26:27 backup3 mysqld: InnoDB: Reading tablespace information from the .ibd files...
  15. Jun 25 09:26:27 backup3 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
  16. Jun 25 09:26:27 backup3 mysqld: InnoDB: buffer...
  17. Jun 25 09:26:28 backup3 mysqld: InnoDB: In a MySQL replication slave the last master binlog file
  18. Jun 25 09:26:28 backup3 mysqld: InnoDB: position 0 56542, file name mysql-bin.010962
  19. Jun 25 09:26:28 backup3 mysqld: InnoDB: and relay log file
  20. Jun 25 09:26:28 backup3 mysqld: InnoDB: position 0 56826, file name ./mysqld-relay-bin.000002
  21. Jun 25 09:26:28 backup3 mysqld: InnoDB: Last MySQL binlog file position 0 36224079, file name /home/mysql/log/mariadb-bin.000475
  22. Jun 25 09:26:28 backup3 mysqld: 120625  9:26:28  InnoDB: Waiting for the background threads to start
  23. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 Percona XtraDB (http://www.percona.com) 1.1.8-26.0 started; log sequence number 72230112426
  24. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Plugin 'FEEDBACK' is disabled.
  25. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Recovering after a crash using /home/mysql/log/mariadb-bin
  26. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Starting crash recovery...
  27. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Crash recovery finished.
  28. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=mysqld-relay-bin' to avoid this problem.
  29. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.010962' at position 56542, relay log './mysqld-relay-bin.000002' position: 56826
  30. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Event Scheduler: Loaded 0 events
  31. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] /usr/sbin/mysqld: ready for connections.
  32. Jun 25 09:26:29 backup3 mysqld: Version: '5.5.25-MariaDB-mariadb1~precise-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
  33. Jun 25 09:26:29 backup3 mysqld: 120625  9:26:29 [Note] Slave I/O thread: connected to master 'repl@db1.fm01.net:3306',replication started in log 'mysql-bin.011085' at position 57880486
  34. Jun 25 09:26:30 backup3 mysqld: 120625  9:26:30 [ERROR] mysqld got signal 11 ;
  35. Jun 25 09:26:30 backup3 mysqld: This could be because you hit a bug. It is also possible that this binary
  36. Jun 25 09:26:30 backup3 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
  37. Jun 25 09:26:30 backup3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
  38. Jun 25 09:26:30 backup3 mysqld:
  39. Jun 25 09:26:30 backup3 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
  40. Jun 25 09:26:30 backup3 mysqld:
  41. Jun 25 09:26:30 backup3 mysqld: We will try our best to scrape up some info that will hopefully help
  42. Jun 25 09:26:30 backup3 mysqld: diagnose the problem, but since we have already crashed,
  43. Jun 25 09:26:30 backup3 mysqld: something is definitely wrong and this may fail.
  44. Jun 25 09:26:30 backup3 mysqld:
  45. Jun 25 09:26:30 backup3 mysqld: Server version: 5.5.25-MariaDB-mariadb1~precise-log
  46. Jun 25 09:26:30 backup3 mysqld: key_buffer_size=134217728
  47. Jun 25 09:26:30 backup3 mysqld: read_buffer_size=2097152
  48. Jun 25 09:26:30 backup3 mysqld: max_used_connections=0
  49. Jun 25 09:26:30 backup3 mysqld: max_threads=102
  50. Jun 25 09:26:30 backup3 mysqld: thread_count=0
  51. Jun 25 09:26:30 backup3 mysqld: It is possible that mysqld could use up to
  52. Jun 25 09:26:30 backup3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759167 K  bytes of memory
  53. Jun 25 09:26:30 backup3 mysqld: Hope that's ok; if not, decrease some variables in the equation.
  54. Jun 25 09:26:30 backup3 mysqld:
  55. Jun 25 09:26:30 backup3 mysqld: Thread pointer: 0x0x7f54f00009a0
  56. Jun 25 09:26:30 backup3 mysqld: Attempting backtrace. You can use the following information to find out
  57. Jun 25 09:26:30 backup3 mysqld: where mysqld died. If you see no messages after this, something went
  58. Jun 25 09:26:30 backup3 mysqld: terribly wrong...
  59. Jun 25 09:26:30 backup3 mysqld: stack_bottom = 0x7f553101e800 thread_stack 0x48000
  60. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f553194042b]
  61. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f5531577e61]
  62. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f5530871cb0]
  63. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f55313f1d94]
  64. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f55313ff66e]
  65. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f5531400184]
  66. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f55314261b8]
  67. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f553143ee82]
  68. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f5531442487]
  69. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f5531641428]
  70. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f55313d3e8d]
  71. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f55313d4ec8]
  72. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f5530869e9a]
  73. Jun 25 09:26:30 backup3 mysqld: ??:0(??)[0x7f552f53c4bd]
  74. Jun 25 09:26:30 backup3 mysqld:
  75. Jun 25 09:26:30 backup3 mysqld: Trying to get some variables.
  76. Jun 25 09:26:30 backup3 mysqld: Some pointers may be invalid and cause the dump to abort.
  77. Jun 25 09:26:30 backup3 mysqld: Query (0x7f54f000e717): is an invalid pointer
  78. Jun 25 09:26:30 backup3 mysqld: Connection ID (thread ID): 1
  79. Jun 25 09:26:30 backup3 mysqld: Status: NOT_KILLED
  80. Jun 25 09:26:30 backup3 mysqld:
  81. Jun 25 09:26:30 backup3 mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off
  82. Jun 25 09:26:30 backup3 mysqld:
  83. Jun 25 09:26:30 backup3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  84. Jun 25 09:26:30 backup3 mysqld: information that should help you find out what is causing the crash.
create a new version of this paste RAW Paste Data