100816 00:04:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql-bkp
100816  0:04:38 [Warning] option 'thread_stack': unsigned value 131072 adjusted to 245760
100816  0:04:38 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 480 error messages,
but it should contain at least 641 error messages.
Check that the above file is the right version for this program!
100816  0:04:38 [Note] Plugin 'FEDERATED' is disabled.
100816  0:04:38 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
100816  0:04:38 [ERROR] mysqld: Can't create/write to file '/var/lib/mysql-bkp/maria_log_control' (Errcode: 13)
100816  0:04:38 [ERROR] mysqld: Got error 'Can't create file' when trying to use maria control file '/var/lib/mysql-bkp/maria_log_control'
100816  0:04:38 [ERROR] Plugin 'MARIA' init function returned error.
100816  0:04:38 [ERROR] Plugin 'MARIA' registration as a STORAGE ENGINE failed.
100816 00:04:38 [Note] PrimeBase XT (PBXT) Engine 1.0.11 Pre-GA loaded...
100816 00:04:38 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
100816 00:04:38 [Error] MainThread int fs_open_file(filesys_xt.cc:595) errno (13): Permission denied: '/var/lib/mysql-bkp/pbxt-lock'
100816 00:04:38 [Error] MainThread int fs_open_file(filesys_xt.cc:595)
100816  0:04:38 [ERROR] Plugin 'PBXT' init function returned error.
100816  0:04:38 [ERROR] Plugin 'PBXT' registration as a STORAGE ENGINE failed.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
100816  0:04:38  InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.
100816 00:04:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
100816 00:05:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql-bkp
100816  0:05:39 [Warning] option 'thread_stack': unsigned value 131072 adjusted to 245760
100816  0:05:39 [ERROR] Error message file '/usr/share/mysql/english/errmsg.sys' had only 480 error messages,
but it should contain at least 641 error messages.
Check that the above file is the right version for this program!
100816  0:05:39 [Note] Plugin 'FEDERATED' is disabled.
100816  0:05:39 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
100816 00:05:39 [Note] PrimeBase XT (PBXT) Engine 1.0.11 Pre-GA loaded...
100816 00:05:39 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
100816  0:05:39  InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1230824223690
100816  0:05:39  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 1230827448335
100816  0:05:40  InnoDB: Error: page 118666 log sequence number 1230828741374
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 2B4B1900
100816  0:05:40  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 100816  0:05:40  InnoDB: Error: page 180225 log sequence number 1230828719278
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:40  InnoDB: Error: page 180276 log sequence number 1230828745868
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
0 100816  0:05:40  InnoDB: Error: page 182713 log sequence number 1230828768066
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
1 100816  0:05:40  InnoDB: Error: page 239491 log sequence number 1230828196061
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:40  InnoDB: Error: page 196609 log sequence number 1230828895564
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:40  InnoDB: Error: page 220673 log sequence number 1230828742197
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
2 3 100816  0:05:40  InnoDB: Error: page 220679 log sequence number 1230828757456
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:40  InnoDB: Error: page 32769 log sequence number 1230828770108
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
4 5 100816  0:05:40  InnoDB: Error: page 192196 log sequence number 1230828760370
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
6 100816  0:05:40  InnoDB: Error: page 196661 log sequence number 1230828753595
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:40  InnoDB: Error: page 606266 log sequence number 1230828841056
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Probable data corruption on page 961814
InnoDB: Original record (compact record)
InnoDB: on that page.
InnoDB: Cannot find the dir slot for record (compact record)
InnoDB: on that page!
100816  0:05:40  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 3d8937ea000ead16000ead0f000ead180000011e925a482445bf000000000000000000000000000b3ded802d3b4a015b3ca500050000002a00000000000000000000000000000002d45fffffffff000000037b57004a0000700000000000010002002e696e66696d756d0006000b000073757072656d756d032c27001c001c14272e000b02060000c470ede0000010018e000002d300002b4b058b000003476f212f001c73696d706c65333280001245ce8a98eb800000064d65726368616e646973658180004d79204368656d6963616c20526f6d616e6365202d2056656e6f6d202d204769726c79202d204f6e6573697a6520800000110000004d79204368656d6963616c20526f6d616e6365202d2056656e6f6d202d204769726c793c62723e475353544d435256454e30312d4f6e6573697a652f732f6d2f736d5f6d63725f76656e6f6d5f6769726c5f342e676966800000012f732f6d2f736d5f6d63725f76656e6f6d5f6769726c5f342e67696680001245ce9916066d792d6368656d6963616c2d726f6d616e63652d76656e6f6d2d6769726c792d6f6e6573697a656d792d6368656d6963616c2d726f6d616e63652d76656e6f6d2d6769726c792d6f6e6573697a652e68746d6c312e30800000110000800000110000800000110000800000110000800000110000800000110000800000110000800000110000800000110000031e19001b001b111d22000b01060000c470ede00000180156000002d400002b4b06e300000340141c5c001c73696d706c653780001245ce8a98ee800000064d65726368616e646973658180005468757273646179202d204c6f676f202d20542d5368697274202d20536d616c6c20800000110000005468757273646179202d204c6f676f202d20542d53686972743c62723e5353545448554c4f4730312d536d616c6c2f732f6d2f736d5f74687572736461795f6c6f676f5f362e676966800000012f732f6d2f736d5f74687572736461795f6c6f676f5f362e67696680001245ce99160974687572736461792d6c6f676f2d73686972742d736d616c6c74687572736461792d6c6f676f2d73686972742d736d616c6c2e68746d6c312e30800000110000800000110000800000110000800000110000800000110000800000110000800000110000800000110000800000110000031f1a001b001b121d23000b01060000c470ede0000020015a000002d500002b4b083800000340221688001c73696d706c653780001245ce8a98f1800000064d65726368616e646973658180005468757273646179202d204c6f676f202d20542d5368697274202d204d656469756d20800000110000005468757273646179202d204c6f676f202d20542d53686972743c62723e5353545448554c4f4730312d4d656469756d2f732f6d2f736d5f74687572736461795f6c6f676f5f372e676966800000012f732f6d2f736d5f74687572736461795f6c6f676f5f372e67696680001245ce99160c74687572736461792d6c6f676f2d73686972742d6d65646975100816  0:05:40  InnoDB: Error: page 192204 log sequence number 1230828761321
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
6d74687572736461792d6c6f676f2d73686972742d6d656469756d2e68746d6c312e30800000110000800000110000800000110000800000110000800000110000800000110000800000110000800000110000800000110000031c1700190019111b20000b02060000c470ede0040028014b000002d600002b4b098f00000eb9100816  0:05:40  InnoDB: Error: page 180224 log sequence number 1230828719278
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
[... confidential ...]
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
[... confidential ...]
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
[... confidential ...]
InnoDB: End of page dump
100816  0:05:41  InnoDB: Page checksum 1032402922 (32bit_calc: 614159610), prior-to-4.0.14-form checksum 1188927962
InnoDB: stored checksum 1032402922, prior-to-4.0.14-form stored checksum 1188927962
InnoDB: Page lsn 286 2455390244, low 4 bytes of lsn at page end 2455390244
InnoDB: Page number (if stored to page already) 961814,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 0 185439
100816  0:05:41  InnoDB: Assertion failure in thread 140629119433040 in file page/page0page.c line 153
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
100816  0:05:41 [ERROR] 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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 350904 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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...
100816  0:05:41  InnoDB: Error: page 182666 log sequence number 1230828767131
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 196631 log sequence number 1230828750657
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 196635 log sequence number 1230828751701
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 153011 log sequence number 1230828505120
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 81947 log sequence number 1230828757439
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 98305 log sequence number 1230828222445
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
10 100816  0:05:41  InnoDB: Error: page 98304 log sequence number 1230828740049
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
11 12 13 14 15 16 17 18 19 20 21 22 100816  0:05:41  InnoDB: Error: page 239227 log sequence number 1230828819623
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
23 24 25 26 27 100816  0:05:41  InnoDB: Error: page 144332 log sequence number 1230828826805
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 144348 log sequence number 1230828745884
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
28 29 30 31 32 33 34 100816  0:05:41  InnoDB: Error: page 266766 log sequence number 1230827796338
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 228168 log sequence number 1230828770140
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 228174 log sequence number 1230829098111
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 228183 log sequence number 1230828967677
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 228185 log sequence number 1230828763304
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100816  0:05:41  InnoDB: Error: page 228187 log sequence number 1230828757456
InnoDB: is in the future! Current system log sequence number 1230827448335.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
35 36 37 100816  0:05:41  InnoDB: Assertion failure in thread 140629111040336 in file rem/rem0rec.c line 561
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
Aborted
100816 00:05:41 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended