Mike Franon Stopping mysql does not always stop it?
Jun 06, 2013; 09:28
Mike Franon
Stopping mysql does not always stop it?
I am running mysql 5.0 for now, and I have a script that I wrote at 12 am, that stops mysql server, unmounts the disk that has mysql, and takes a different snapshot from amazon as the new disk.
Long story short, 50% of the time the command /etc/init.d/mysqld stop will fail
Stopping MySQL: [FAILED]
Unmounting /opt on dbserver1
I then log on the server and mysql is still running.
When that happens what is the best way to stop mysql? I am trying to write something in my script that will do that, and thinking of using the kill command, but is that the best way?
Or should I be using mysqladmin stop? Is there a better way to bring down mysql server and make sure it is down? Should I be doing something else to ensure it comes down?
Thanks
Jun 06
Manuel Arostegui Re: Stopping mysql does not always stop it?
Jun 06, 2013; 15:39
Manuel Arostegui
Re: Stopping mysql does not always stop it?
Jun 06
Reindl Harald Re: Stopping mysql does not always stop it?
Jun 06, 2013; 15:55
Reindl Harald
Re: Stopping mysql does not always stop it?
Jun 06
Manuel Arostegui Re: Stopping mysql does not always stop it?
Jun 06, 2013; 16:10
Manuel Arostegui
Re: Stopping mysql does not always stop it?
Jun 06
hsv Re: Stopping mysql does not always stop it?
Jun 06, 2013; 10:01
hsv
Re: Stopping mysql does not always stop it?
Jun 06
Reindl Harald Re: Stopping mysql does not always stop it?
Jun 06, 2013; 19:36
Reindl Harald
Re: Stopping mysql does not always stop it?
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!