On Fri, Mar 30, 2007 at 11:22:53PM +0200, Christian Hammers wrote: > > > On 2007-03-30 Ambrose Li wrote: > > > Please mail me the output of: > > > > > > grep mysql /var/log/syslog > > > > This is roughly 8 minutes after the postinst script got stuck: > > > > Mar 30 15:42:38 tea mysqld[32369]: 070330 15:42:38 > > [Note] /usr/sbin/mysqld: Normal shutdown Mar 30 15:42:38 tea mysqld[32369]: > > And what does it say before that? I.e. when it starts? Maybe something > interesting there.
Um... nothing. It doesn't start at all. The shutdown you see was a previous mysql version. It worked before I did an apt-get upgrade (but I didn't write down what version I had as I didn't expect any problems). I couldn't get it to work, and I reinstalled from the version in etch. When I reinstalled the unstable version to get the log message, it stopped the mysql from etch, which is what the log I sent you was. Or is the new build depending on a particular kernel feature at compile time? I am asking because I compile my own kernel and it is not the "latest" kernel series; squid also gives me problem since a number of months ago and I was told that squid will never be fixed, so I am setting apt to hold squid to avoid the new builds from getting installed. > The only reason I know why mysql completetly "stoppes" but still not crashes > is when it tries to write but there is not enough space on the disc. > > Do you use innodb so that it maybe tries to extend the table space? On > which partition is it? It's on the /var partition which is 63% full. There is 231M available. > bye, > > -christian- Regards, -- Ambrose Li <[EMAIL PROTECTED]> Chinese Cultural Centre of Greater Toronto +1 416 292 9293 http://www.cccgt.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
