Xen users - May 2005 - 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?



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hello Paul,

sorry for the new thread, but I''m not subscripted to the list.

I use SuSE 9.3 and the XEN packages they provide. In my dom0 system I had a 
similar problem: at boot mysql is started by it never shows up as running if 
tested with ''rcmysql status''. After some try and error I
deinstalled the
mysql-Max RPM (a MySQL - Server with Berkeley DB) and mysql is working. It 
seems that the Berkeley DB doesn''t work with XEN (or with tls moved to 
tls.disabled). I have not tested this further but I found a similar problem 
with amavis (also using Berkeley DB).

Best regards

Matthias
-- 
Linux is for people who want to know why it works.
Mac is for people who don''t want to know why it works.
DOS is for people who want to know why it does not work.
Windows is for people who don''t want to know why it does not work.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I''m running mysqld in domU, with all tables InnoDB (except for the
system
database). Could this be the same problem? I dunno.

Matthias Pfafferodt wrote, On 24/05/05 21:36:
> Hello Paul,
> 
> sorry for the new thread, but I''m not subscripted to the list.
> 
> I use SuSE 9.3 and the XEN packages they provide. In my dom0 system I had a
> similar problem: at boot mysql is started by it never shows up as running
if
> tested with ''rcmysql status''. After some try and error I
deinstalled the
> mysql-Max RPM (a MySQL - Server with Berkeley DB) and mysql is working. It 
> seems that the Berkeley DB doesn''t work with XEN (or with tls
moved to
> tls.disabled). I have not tested this further but I found a similar problem
> with amavis (also using Berkeley DB).
> 
> Best regards
> 
> Matthias
- --
Paul Laws
Analyst / Programmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFClEuJYmQ8biuDK88RAqCuAJwMXejc61DtNhwzedfDM1XQ8WJpYgCfUomG
hY29cXbW7cPYtthhhkCKSW4=+teC
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hallo Paul,

I don''t know if it is the same problem. You could check if you use the
Berkeley DB and try without it. The SuSE RPM mysql-Max adds the Berkeley
DB and InnoDB to the mysql server. Without this RPM mysql is working fine.
 Amavis also has problems using the Berkeley DB so I think this is the
problem.

Matthias
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I''m running mysqld in domU, with all tables InnoDB (except for the
system
> database). Could this be the same problem? I dunno.
>
> Matthias Pfafferodt wrote, On 24/05/05 21:36:
>> Hello Paul,
>>
>> sorry for the new thread, but I''m not subscripted to the list.
>>
>> I use SuSE 9.3 and the XEN packages they provide. In my dom0 system I
>> had a
>> similar problem: at boot mysql is started by it never shows up as
>> running if
>> tested with ''rcmysql status''. After some try and
error I deinstalled the
>> mysql-Max RPM (a MySQL - Server with Berkeley DB) and mysql is working.
>> It
>> seems that the Berkeley DB doesn''t work with XEN (or with tls
moved to
>> tls.disabled). I have not tested this further but I found a similar
>> problem
>> with amavis (also using Berkeley DB).
>>
>> Best regards
>>
>> Matthias
>
> - --
> Paul Laws
> Analyst / Programmer
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFClEuJYmQ8biuDK88RAqCuAJwMXejc61DtNhwzedfDM1XQ8WJpYgCfUomG
> hY29cXbW7cPYtthhhkCKSW4> =+teC
> -----END PGP SIGNATURE-----
>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Matthias Pfafferodt wrote:
> Hallo Paul,
> 
> I don''t know if it is the same problem. You could check if you use
the
> Berkeley DB and try without it. The SuSE RPM mysql-Max adds the Berkeley
> DB and InnoDB to the mysql server. Without this RPM mysql is working fine.
>  Amavis also has problems using the Berkeley DB so I think this is the
> problem.
> 
> Matthias
Getting a problem here with OpenLDAP, also using Berkeley DB....

Xen testing / 2.6.11 kernel

-- 

-Barry Flanagan

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Barry Flanagan wrote, On 25/05/05 14:25:
> Matthias Pfafferodt wrote:
> 
>>Hallo Paul,
>>
>>I don''t know if it is the same problem. You could check if you
use the
>>Berkeley DB and try without it. The SuSE RPM mysql-Max adds the Berkeley
>>DB and InnoDB to the mysql server. Without this RPM mysql is working
fine.
>> Amavis also has problems using the Berkeley DB so I think this is the
>>problem.
>>
>>Matthias
> 
> 
> Getting a problem here with OpenLDAP, also using Berkeley DB....
> 
> Xen testing / 2.6.11 kernel
> 
I''m pretty sure I''m not using the Berkeley DB. I''ve
tried with the default
MySQL download (not the max); I don''t believe that it even has the
Berkeley DB
code in it.

I *am* using InnoDB, though.

- --
Paul Laws
Analyst / Programmer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFClIJzYmQ8biuDK88RAo3jAJ9XgN2sxu1T3MxoVD+mii63aZPOqwCghhhq
fet4FlWEJGIz6TvGwUqJ5js=ITxt
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Getting a problem here with OpenLDAP, also using Berkeley DB....
> 
> Xen testing / 2.6.11 kernel
What distro are you on? Maybe your Berkeley DB is tickling the same issue 
for some reason.

Cheers,
Mark

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

M.A. Williamson wrote:
>> Getting a problem here with OpenLDAP, also using Berkeley DB....
>>
>> Xen testing / 2.6.11 kernel
> 
> 
> What distro are you on? Maybe your Berkeley DB is tickling the same
> issue for some reason.
> 
Debian Sarge.


-- 

-Barry Flanagan

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Debian Sarge.
Hrrmmm strange.  I asked because we occasionally get problems with Gentoo 
systems USE flags, since for some packages gcc wants to emit certain TLS 
manipulations that won''t work.

How does it die on your system?  Does "xm dmesg" tell you anything
useful?
What about with a debug/verbose build of Xen?

Cheers,
Mark
(who has now fixed his system clock!)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users