리눅스 분류
msyql 재시작이안됩니다..ㅠㅠ
작성자 정보
- 메일 작성
- 작성일
컨텐츠 정보
- 2,364 조회
- 0 추천
- 목록
본문
mysql 이 한번죽은후에 살릴려고 프로세스 다죽이고 다시 mysqld_safe & 했는뎅도
걔속 mysql_ended 메세지만 나오거던요 로그 파일 확인하니까..이메세지가 나오는데
확인좀해주세요..
050926 10:03:30 mysqld started
050926 10:03:34 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: Doing recovery: scanned up to log sequence number 0 43922
050926 10:03:34 InnoDB: Flushing modified pages from the buffer pool...
050926 10:03:34 InnoDB: Started
/usr/local/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20' socket: '/tmp/mysql.sock' port: 3306
050926 10:17:11 /usr/local/mysql/libexec/mysqld: Normal shutdown
050926 10:17:12 InnoDB: Starting shutdown...
050926 10:18:33 mysqld started
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
InnoDB: You may have to recover from a backup.
050926 10:18:38 InnoDB: Page dump in ascii and hex (16384 bytes):
050926 15:28:39 InnoDB: Page checksum 3635807122, prior-to-4.0.14-form checksum 271693429
InnoDB: stored checksum 3057247106, prior-to-4.0.14-form stored checksum 271693429
InnoDB: Page lsn 0 43886, low 4 bytes of lsn at page end 43886
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: Look also at section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about
InnoDB: forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
050926 15:28:39 mysqld ended
050926 15:29:00 mysqld started
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
InnoDB: You may have to recover from a backup.
050926 15:29:00 InnoDB: Page dump in ascii and hex (16384 bytes):
걔속 mysql_ended 메세지만 나오거던요 로그 파일 확인하니까..이메세지가 나오는데
확인좀해주세요..
050926 10:03:30 mysqld started
050926 10:03:34 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: Doing recovery: scanned up to log sequence number 0 43922
050926 10:03:34 InnoDB: Flushing modified pages from the buffer pool...
050926 10:03:34 InnoDB: Started
/usr/local/mysql/libexec/mysqld: ready for connections.
Version: '4.0.20' socket: '/tmp/mysql.sock' port: 3306
050926 10:17:11 /usr/local/mysql/libexec/mysqld: Normal shutdown
050926 10:17:12 InnoDB: Starting shutdown...
050926 10:18:33 mysqld started
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
InnoDB: You may have to recover from a backup.
050926 10:18:38 InnoDB: Page dump in ascii and hex (16384 bytes):
050926 15:28:39 InnoDB: Page checksum 3635807122, prior-to-4.0.14-form checksum 271693429
InnoDB: stored checksum 3057247106, prior-to-4.0.14-form stored checksum 271693429
InnoDB: Page lsn 0 43886, low 4 bytes of lsn at page end 43886
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: Look also at section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about
InnoDB: forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
050926 15:28:39 mysqld ended
050926 15:29:00 mysqld started
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 0.
InnoDB: You may have to recover from a backup.
050926 15:29:00 InnoDB: Page dump in ascii and hex (16384 bytes):
관련자료
-
이전
-
다음
댓글 0
등록된 댓글이 없습니다.
