stoppin mysql/gave up waiting

[Mayuran Yogarajah]

We have MySQL running on a Redhat server (RHEL 3.2).  We issued a 
service mysql
restart yesterday and for some reason MySQL didn't shut down properly.  
The init
script said it "gave up waiting" and deleted the PID file anyway.  Since 
we issued a restart,
I suspect a second copy of MySQL got started.  InnoDB complained that it 
was not
shut down normally and started doing recovery.  We let the recovery 
process finish, stopped
the second instance of mysql and killed the first instance (using kill 
-9).  The server seems OK
now (luckily its not in production yet), but I don't know what would 
cause MySQL to not
shut down properly.  Has this happened to anyone else? Please let me 
know if you have any
theories or suggestions.

thanks,
M
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]