cacti+mysql 报错

liang3391

cacti+mysql


mysql间隔几分钟就会自动down掉（端口号和进程仍然存在），必须要手动杀掉所有的mysql进程才，然后重启mysql服务才可以正常使用。


FATAL: Cannot connect to MySQL server on 'localhost'. Please make sure you have specified a valid MySQL database name in 'include/config.php'

[ 本帖最后由 liang3391 于 2009-5-3 16:21 编辑 ]

devilkin0312

所有的，意思是很多？一致杀线程不怕崩掉么回复 1# liang3391


   

alang85

回复 6# liang3391


    你先清理之前的日志，然后在连接，看报什么错误，然后再打印出来。先解决数据库能正常启动。

alang85

回复 1# liang3391


    根据MYSQL错误日志处理问题。网上有些说找不到mysql.sock。

shihao138096

楼主首先确定一下<cacti_dir>/include/下面的config.php以及global.php文件中mysql的数据库相关选项是否设置正确

Coolriver

如只是安装一个新的mysql 那么，你把/usr/local/mysql/var 下面一个id 开头的文件给删掉，在启动。让mysql重新创建试一下。

liang3391

mysql 不以root运行的话  就不能启动。mysql没有做任何处理。这服务器上mysql安装了几次。也没有做数据直接cpoy。

Coolriver

root@testtt [/usr/local/mysql/var]# /usr/local/mysql/bin/mysqld_safe --defaults-file=/etc/my.cnf --user=root

mysql 不能以root运行。
现在日值显示，表空间错误，需要恢复。你的数据是不是直接cpoy过来的。而且里有innodb的表。

去查一下innodb怎么迁移的。就可以必免了。

liang3391

090503 16:25:53  InnoDB: Page checksum 1612628608, prior-to-4.0.14-form checksum                                               2673809632
InnoDB: stored checksum 808464432, prior-to-4.0.14-form stored checksum 80846443                                              2
InnoDB: Page lsn 808464432 808464432, low 4 bytes of lsn at page end 808464432
InnoDB: Page number (if stored to page already) 808464432,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 808464432
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1.
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: See also InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery                                              .html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
090503 16:25:53  mysqld ended
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of page 2.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Error: page n stored in the page read in is 808464432, should be 1!
090503 16:25:53  InnoDB: Error: page 808464432 log sequence number 808464432 808464432
InnoDB: is in the future! Current system log sequence number 0 193521.
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.0/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1.
InnoDB: You may have to recover from a backup.
090503 16:25:53  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 30303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030
InnoDB: stored checksum 858796848, prior-to-4.0.14-form stored checksum 858796848
InnoDB: Page lsn 858796848 858796848, low 4 bytes of lsn at page end 858796848
InnoDB: Page number (if stored to page already) 858796848,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 858796848
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 1.
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: See also InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
090503 16:40:52  mysqld ended




root@testtt [~]# cat /usr/local/mysql/log/
error.log      mysql.log      slowquery.log
root@testtt [~]# cat /usr/local/mysql/log/slowquery.log
/usr/local/mysql/libexec/mysqld, Version: 5.0.40-log (Source distribution). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/local/mysql/libexec/mysqld, Version: 5.0.40-log (Source distribution). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/local/mysql/libexec/mysqld, Version: 5.0.40-log (Source distribution). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/local/mysql/libexec/mysqld, Version: 5.0.40-log (Source distribution). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/local/mysql/libexec/mysqld, Version: 5.0.40-log (Source distribution). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/sbin/mysqld, Version: 5.0.67-community-log (MySQL Community Edition (GPL)). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/sbin/mysqld, Version: 5.0.67-community-log (MySQL Community Edition (GPL)). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument
/usr/sbin/mysqld, Version: 5.0.67-community-log (MySQL Community Edition (GPL)). started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument

[ 本帖最后由 liang3391 于 2009-5-3 16:44 编辑 ]