[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] mysql & xen - is anyone using this combination successfully?
Hi, I've tried running the mysql daemon on a few different servers running Xen, and seen two different sorts of problems. In one case, on two identically configured systems, the mysql daemon segv's but restarts immediately. This happened with Xen 2.0.5, I haven't yet seen it with 2.0.6. It seems to be the same problem as this one: http://lists.xensource.com/archives/html/xen-users/2005-05/msg00281.html http://lists.xensource.com/archives/html/xen-users/2005-05/msg00250.html In the other case, the mysql daemon crashes, and on a restart detects a checksum fault. I've seen this three times now, and had to recreate the database from an SQL dump - twice with 2.0.5 and once with 2.0.6. Here's an excerpt from the log: 050524 8:43:15 InnoDB: Started /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.0.24-standard' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Official MySQL-standard binary /etc/host.conf: line 24: bad command `mdns off' InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 796594. InnoDB: You may have to recover from a backup. 050524 8:43:55 InnoDB: Page dump in ascii and hex (16384 bytes): [hex dump removed] 050524 8:43:55 InnoDB: Page checksum 919908210, prior-to-4.0.14-form checksum 1953981686 InnoDB: stored checksum 2965041445, prior-to-4.0.14-form stored checksum 842083124 InnoDB: Page lsn 2 1189539217, low 4 bytes of lsn at page end 876034097 InnoDB: Page may be an index page where index id is 0 151 InnoDB: (index `bytime` of table `archive200501/sms_log`) InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 796594. 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 http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. 050524 8:43:56 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 3 827083739 InnoDB: Doing recovery: scanned up to log sequence number 3 827083739 050524 8:43:56 InnoDB: Flushing modified pages from the buffer pool... 050524 8:43:56 InnoDB: Started /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.0.24-standard' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Official MySQL-standard binary /etc/host.conf: line 24: bad command `mdns off' I'm beginning to wonder whether it's safe to use mysql on xen in a live environment. Is anyone actually doing this successfully? Attachment:
paul.laws.vcf _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |