Re: a curse on OS sierra and MySQL?

[Martin Mueller]

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"  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"  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=CwIDaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk=Rp61bfD4ngoSU50qebNy37Nmv34OSqdiU4Sigj8b9zI=RDN0din-b9O7hEkNJOKe1CbYe_5MipeeuN2oeOMsWfI=
>  
>  > 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=CwIDaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk=I5PKsknY5e1wjZZG11zhg1tGbZKrqgs0FExanPNtMkk=40lzUebvOmuxTUq-dnXHbwXgaFEyIyYqf93pjPGQibU=
 
To unsubscribe:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.mysql.com_mysql=CwIDaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk=I5PKsknY5e1wjZZG11zhg1tGbZKrqgs0FExanPNtMkk=40lzUebvOmuxTUq-dnXHbwXgaFEyIyYqf93pjPGQibU=
 




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: a curse on OS sierra and MySQL?

[Peter Brawley]

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"  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=CwIDaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk=Rp61bfD4ngoSU50qebNy37Nmv34OSqdiU4Sigj8b9zI=RDN0din-b9O7hEkNJOKe1CbYe_5MipeeuN2oeOMsWfI=
 
 > 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: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: a curse on OS sierra and MySQL?

[Peter Brawley]

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 
http://superuser.com/questions/159486/how-to-kill-process-in-mac-os-x-and-not-have-it-restart-on-its-own



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

Re: a curse on OS sierra and MySQL?

[Hal.sz S.ndor]

2016/12/02 18:58 ... Martin Mueller:

Alas, running the stop and start commands under sudo makes zero difference. 
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. But after a couple of weeks it suddenly failed in the same way 
although I had done nothing on the system administration end.

I’m not a programmer, but I’ve worked with lots of programs, and MySQL, which 
is wonderful when it works, is absolutely the worst in the obscure and poorly 
documented steps that take you from the code to an installation that works. At 
least that is the case with OS 10.


Just now I looked at the Peter-recommended page, and toward the end saw 
references (mcsharry) to sudden change of owner & permission--it sounds 
somewhat like your problem. Looked into that? (maybe a MySQL bug is 
involved.)


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: a curse on OS sierra and MySQL?

[Martin Mueller]

Alas, running the stop and start commands under sudo makes zero difference. 
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. But after a couple of weeks it suddenly failed in the same way 
although I had done nothing on the system administration end. 

I’m not a programmer, but I’ve worked with lots of programs, and MySQL, which 
is wonderful when it works, is absolutely the worst in the obscure and poorly 
documented steps that take you from the code to an installation that works. At 
least that is the case with OS 10.

On 12/2/16, 5:42 PM, "Peter Brawley"  wrote:

On 12/2/2016 16:59, Martin Mueller wrote:
> I have been trying repeatedly and in vain to install the community 
edition of MySQL 5.7.16 on an iMac running OS sierra.  I religiously followed 
the instructions for uninstalling previous versions found at 
https://urldefense.proofpoint.com/v2/url?u=http-3A__community.jaspersoft.com_wiki_uninstall-2Dmysql-2Dmac-2Dos-2Dx=CwIDaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk=LP2YLfUL67Gr-H-dkv9ZuW5LDsLMTL-M7m7g50wBPu4=sqlfF8DCjesZOKwqOhB8bmyF0bkpvNWHU8cXz-amxg4=
 , and installation progresses smoothly and terminates successfully.  Bu the 
attempt to start the server produces the error message  :
> ERROR! MySQL server PID file could not be found!

Is 

https://urldefense.proofpoint.com/v2/url?u=http-3A__stackoverflow.com_questions_861_pid-2Derror-2Don-2Dmysql-2Dserver-2Dstart=CwIDaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=rG8zxOdssqSzDRz4x1GLlmLOW60xyVXydxwnJZpkxbk=LP2YLfUL67Gr-H-dkv9ZuW5LDsLMTL-M7m7g50wBPu4=M2Yd8vqNwYiRfeLsjhV2Ut_dG-pxlDiy5d-eEx1rubQ=
  
helpful?

PB

- 

Re: a curse on OS sierra and MySQL?

[Peter Brawley]

On 12/2/2016 16:59, Martin Mueller wrote:

I have been trying repeatedly and in vain to install the community edition of 
MySQL 5.7.16 on an iMac running OS sierra.  I religiously followed the 
instructions for uninstalling previous versions found at 
http://community.jaspersoft.com/wiki/uninstall-mysql-mac-os-x, and installation 
progresses smoothly and terminates successfully.  Bu the attempt to start the 
server produces the error message  :
ERROR! MySQL server PID file could not be found!


Is 
http://stackoverflow.com/questions/861/pid-error-on-mysql-server-start 
helpful?


PB

-



I have tried this and that, looking at advice on the Web, which is plentiful 
but not always. Nothing works.

I have installed Postgresql, about which I know very little. But the 
installation proceeded smoothly, and turning the server on and off works like a 
charm.

Is it a reasonable conclusion that MySQl and OS 10 just don’t like each other 
very much and that a prudent man is better off with some other database? The 
MySQL documentation is not very helpful in the sense that following it doesn’t 
produce good results.




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql