Hi Sean,

I was just wondering whether you managed to make any progress on this.  Is there
any more info I can provide you with?

Cheers,
Stella

On Sat, Jun 03, 2006 at 07:56:33AM -0400, sean finney wrote:
> hi stella,
> 
> On Thu, Jun 01, 2006 at 11:15:28AM +0100, Stella Power wrote:
> > The file is too large to send to you by email, Postfix bounced it back.  So 
> > I've
> > put it up for you to download over the web:
> >     http://www.stellapower.net/ltrace.out.tgz
> 
> okay, thanks.  out of curiosity, did mysqld crash with the same signal
> and message, or did you have to hit ctrl-c for it to exit?
> 
> looking at the ltrace file doesn't really reveal anything to me, and i'm
> unable to reproduce the problem, which is a bit frustrating.
> 
> okay, so next steps:
> 
> - send the contents of your /etc/mysql/my.cnf (make sure to mask
>   anything sensitive in the file first)
> 
> - try removing all but the mysql database, and if the server doesn't
>   crash add them back in one at a time until the server does crash.
> 
> the second step is kind of tricky, and you should make sure you know
> what you're doing at each step.
> 
> the process would be something like this:
> 
> (finding the list of databases)
> cd /var/lib/
> find mysql -mindepth 1 -maxdepth 2 -type d ! -name mysql
> 
> (removing all but mysql database)
> /etc/init.d/mysql stop
> tar cvfz /tmp/mysql.save.tgz mysql
> find mysql -mindepth 1 -maxdepth 2 -type d ! -name mysql | xargs rm -rf 
> /etc/init.d/mysql start
> 
> (adding in databases one at a time)
> /etc/init.d/mysql stop
> tar xvfz /tmp/mysql.save.tgz database1
> /etc/init.d/mysql start
> (and so on)
> 
> so if you're feeling particularly adventurous (and/or impatient), try
> the second step while you're waiting to hear back from me after sending
> th emy.cnf file.  if you're feeling particularly cautious, you might
> want to wait on the seconod step until i have a chance to look
> at the file.
> 
> 
>       sean




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to