Re: MySQL 5 crashing on 6.0
Adam Bayless <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.database |
|---|---|
| Message-ID | <[email protected]> |
Miroslav Lachman thought no one was listening and belted out: > > > Have you any useful information in mysql errorlog? (usualy > /var/db/mysql/your.host.name.err) > > Miroslav Lachman > > I should have included that in my original message. Here's the latest crash. Not much in the way of error messages: 060207 06:01:41 mysqld restarted 060207 6:01:42 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... 060207 6:01:42 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 16 3794872210. InnoDB: Doing recovery: scanned up to log sequence number 16 3800114688 . . . InnoDB: Doing recovery: scanned up to log sequence number 16 3957401088 060207 6:02:18 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 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 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 16 3962643968 . . . InnoDB: Doing recovery: scanned up to log sequence number 16 4119930368 060207 6:04:04 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 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 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 16 4125173248 . . . InnoDB: Doing recovery: scanned up to log sequence number 16 4282459648 060207 6:05:47 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 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 InnoDB: Apply batch completed InnoDB: Doing recovery: scanned up to log sequence number 16 4287702528 . . . InnoDB: Doing recovery: scanned up to log sequence number 17 97371946 060207 6:07:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 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 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 0, file name 060207 6:08:27 InnoDB: Started; log sequence number 17 97371946 060207 6:08:27 [Note] /usr/local/libexec/mysqld: ready for connections. Version: '5.0.18-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-5.0.18 Thanks, Adam _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-database To unsubscribe, send any mail to "[email protected]"