[ubuntu-us-mi] How to shut down MySQL on Ubuntu Lucid 10.04?

David Barnett dhbarnett at gmail.com
Thu Dec 16 19:01:35 GMT 2010


Is there anything in the mysql logs? It almost sounds likethe database is
ignoring the stop command. Maybe a permissions issue?

--dave
On Dec 16, 2010 1:48 PM, "Robert Citek" <robert.citek at gmail.com> wrote:
> On Thu, Dec 16, 2010 at 1:03 PM, mike <mcruz32 at wowway.com> wrote:
>> Maybe this can help.
>> http://upstart.ubuntu.com/faq.html#reload
>
> Thanks, except that is also fraught with issues.
>
> "If a job is running, the changes to the definition will not occur
> until the job has been stopped;"
>
> And I can't stop the job (mysql in this case) because upstart will
> cause the tables to get corrupted by killing mysqld too soon.
>
> "To force a reload you may send init the HUP signal, or use the
> following command: initctl reload "
>
> Unfortunately, that reload doesn't work for me:
>
> $ sudo initctl reload
> initctl: missing job name
> Try `initctl --help' for more information.
>
> If I specify mysql as the job, that seems to be equivalent to
> /etc/init.d/mysql reload. The man page for initctl seems to confirm
> this:
>
> reload JOB [KEY=VALUE]...
>
> Sends the SIGHUP signal to running process of the named
> JOB instance.
>
> So a reload sends SIGHUP to the JOB and not to init.
>
> The one thing I have not tried is 'kill -SIGHUP 1". I'm going to
> setup a VM before I try that one on our servers.
>
> Regards,
> - Robert
>
> --
> ubuntu-us-mi mailing list
> ubuntu-us-mi at lists.ubuntu.com
> Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-mi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-mi/attachments/20101216/4744dae9/attachment-0001.htm 


More information about the ubuntu-us-mi mailing list