Well, the command
sudo /usr/local/mysql/support-files/mysql.server stop
generates the error message:
ERROR! MySQL server PID file could not be found!
On the other hand,
sudo launchctl unload -F
/Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
stops the server and
sudo /usr/local/mysql/support-files/mysql.server start
starts it
On 12/3/16, 4:40 PM, "Peter Brawley" <peter.braw...@earthlink.net> wrote:
On 12/3/2016 13:58, Martin Mueller wrote:
> I was able to install a version of MySQL 5.6 on OS Sierra. It appears
that the “launchdaemon’ method works while the mysql.server start/stop method
does not work. In retrospect I should have seen that, but I also think that
the official documentation could and should be more explicit about what is a
significant change in Apple’s start/stop routines.
If you mean that seriously, it needs to be more specific.
PB
-----
>
> On 12/3/16, 12:43 PM, "Peter Brawley" <peter.braw...@earthlink.net> wrote:
>
> On 12/2/2016 17:58, Martin Mueller wrote:
> > Alas, running the stop and start commands under sudo makes zero
difference.
>
> ?! The cited page recommends more than sudo starts and stops, eg ...
>
> |unset TMPDIR mysql_install_db |
>
> Did you try that? Did you check the pid setting in my.cnf, eg
> pid-file=/var/run/mysqld/mysqld.pid? I believe you need to ensure
that
> the pid file specified in my.cnf exists and that the mysql daemon
owns
> it ...
>
> mkdir /var/run/mysqld
> touch /var/run/mysqld/mysqld.pid
> chown -R mysql:mysql /var/run/mysqld
>
> Also see
>
https://urldefense.proofpoint.com/v2/url?u=http-3A__superuser.com_questions_159486_how-2Dto-2Dkill-2Dprocess-2Din-2Dmac-2Dos-2Dx-2Dand-2Dnot-2Dhave-2Dit-2Drestart-2Don-2Dits-2Down&d=CwIDaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk&m=Rp61bfD4ngoSU50qebNy37Nmv34OSqdiU4Sigj8b9zI&s=RDN0din-b9O7hEkNJOKe1CbYe_5MipeeuN2oeOMsWfI&e=
>
> > This is a very frustrating problem, and I hope somebody in the
MySQl documentation department will take a look at it. It’s cleary a problem
that has been around for years because the Web is full of complaints and tips.
But there doesn’t seem to be any convergence a bout a diagnosis or a likely
cure. And there is nothing in the MySQL documentation that draws attention to
the probem.
> >
> > In my case, I’m double frustrated because some months ago my MySQL
application broke around this problem, and then a couple of weeks ago it cured
itself when I somewhat arbitrarily picked up an earlier version of my
installation from Time Machine.
> That suggests the problem arose from a change in your app, or a
setting
> change that occurred in a MySQL upgrade. To show that this is a
common
> problem that MySQL docs ought to address, you'll need to identify the
> setting that's gone awry.
>
> PB
>
>
>
--
MySQL General Mailing List
For list archives:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.mysql.com_mysql&d=CwIDaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk&m=I5PKsknY5e1wjZZG11zhg1tGbZKrqgs0FExanPNtMkk&s=40lzUebvOmuxTUq-dnXHbwXgaFEyIyYqf93pjPGQibU&e=
To unsubscribe:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.mysql.com_mysql&d=CwIDaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk&m=I5PKsknY5e1wjZZG11zhg1tGbZKrqgs0FExanPNtMkk&s=40lzUebvOmuxTUq-dnXHbwXgaFEyIyYqf93pjPGQibU&e=
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
