Hi all
my setup:
# uname -a
Linux localhost 2.6.18-8.el5.028stab031.1 #1 SMP Fri Apr 27
20:08:01 MSD 2007 x86_64 Intel(R) Xeon(TM) CPU 3.00GHz GenuineIntel
GNU/Linux
I have a amd64 gentoo template where I installed mysql
gcc-4.1.1, glibc-2.5-r2, 2.6.18-8.el5.028stab031.1 x86_64
[ebuild R ] dev-db/mysql-5.0.38 USE="berkdb perl ssl -big-tables
-cluster -debug -embedded -extraengine -latin1 -max-idx-128 -minimal
(-selinux) -static" 0 kB
and when I start mysqld and stop while innodb is active , at next
start mysqld will crash:
snip from /var/log/mysql/mysqld.err
FIRST START:
070510 12:31:55 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
070510 12:31:56 InnoDB: Log file ./ib_logfile0 did not exist: new to be
created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
070510 12:31:56 InnoDB: Log file ./ib_logfile1 did not exist: new to be
created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
070510 12:31:56 InnoDB: Started; log sequence number 0 0
070510 12:31:56 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.38-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306
Gentoo Linux mysql-5.0.38
070510 12:32:09 [Note] /usr/sbin/mysqld: Normal shutdown
STOP:
070510 12:32:09 InnoDB: Starting shutdown...
070510 12:32:10 InnoDB: Shutdown completed; log sequence number 0 43655
070510 12:32:10 [Note] /usr/sbin/mysqld: Shutdown complete
2ND START:
070510 12:49:46 [Warning] No argument was provided to --log-bin, and
--log-bin-index was not used; so replication may break whe
n this MySQL server acts as a master and has his hostname changed!! Please
use '--log-bin=/var/run/mysqld/mysqld-bin' to avoid
this problem.
070510 12:49:46 - mysqld got signal 4;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctioning
hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.
CRASH!
If I set skip-innodb.. will work fine
no failed beans:
rtg-db-vps / # grep -v ' 0$' /proc/user_beancounters
Version: 2.5
uid resource held maxheld
barrier limit failcnt
no issue with quota:
# vzquota stat 102
resource usage softlimit hardlimit grace
1k-blocks 536692 104857600 104857600
inodes 42462 6000000 6000000
Any hints?
catam
PS: Please CC me on replies I am not subscribed
_______________________________________________
Users mailing list
[email protected]
https://openvz.org/mailman/listinfo/users
