MySQL ODBC Connector - MySQL 4.0.18 on Mac OS X 10.2.8 won't start

Author

MySQL 4.0.18 on Mac OS X 10.2.8 won't start

Sachin Petkar

2006-04-02, 9:26 am

------ =_Part_1289_25357107
.1143984017614
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

For some reason, MySQL 4.0.18 has suddenly stopped running and will not
start anymore.

It has been running for several weeks until about 5 days ago. When I tried
to reach it, I discovered that it is no longer running. However,
attempting to start it via the mysqld_safe script simply returns with:

Starting mysqld daemon with databases from /usr/local/mysql/data
060402 18:49:55 mysqld ended

[1] Done ./mysqld_safe --user mysql

To confirm, the /tmp/mysql.sock file does not exist at this point.

Any ideas on how to get this running again?

Sachin

--
Sachin Petkar
Email : sachin.petkar@gmail.com

------ =_Part_1289_25357107
.1143984017614--

mysql@karsites.net

2006-04-02, 8:26 pm

Do you have some sort of visual process manager for Mac OS X
that can tell you at a glance if mysqld_safe and mysql
server are actually running in memory?

Under linux I use a program called qps.

http://www.student.nada.kth.se/~f91-men/qps/

You may already have a similar utility to view running
processes under Mac OS X. Or there may be something similar
you can download for free off the net.

You really need some way of verifying that mysqld is
actually running in memory, before attempting to connect to
it.

This is handy for showing running multiple servers, ie when
upgrading to a newer version. You can see the port and
socket each mysqld is listening to, plus other server
directives such as the data directory and PID.

I start mysqld directly with a bash shell script:

#! /bin/sh
#
# start the MySQL database server

/usr/local/mysql-5.0.18/bin/mysqld \
--defaults-file=/usr/local/mysql-5.0.18/my.cnf \
--port=7000 \
--socket=/var/lib/mysql/mysql.sock \
--pid=/var/lib/mysql/laptop.pid \
--user=mysql \
--datadir=/var/lib/mysql &

and stop it with:

#! /bin/sh
#
# stop the MySQL database server

/usr/local/mysql-5.0.18/bin/mysqladmin shutdown \
-uXXXXXX -pXXXXXX
--socket=/var/lib/mysql/mysql.sock

If I don't use the script to pass parameters to mysqld but
add them to my.cnf, they will not appear in qps process
manager.

I have noticed that sometimes mysqld_safe script would
start, and be in memory, but the mysqld server was not being
loaded into memory for some reason, which obviuosly meant I
could not connect to the mysql server.

For that reason I no longer use mysqld_safe to start mysqld.

HTH

Keith

In theory, theory and practice are the same;
in practice they are not.

On Sun, 2 Apr 2006, Sachin Petkar wrote:

> To: mysql@lists.mysql.com
> From: Sachin Petkar <sachin.petkar@gmail.com>
> Subject: MySQL 4.0.18 on Mac OS X 10.2.8 won't start
>
> For some reason, MySQL 4.0.18 has suddenly stopped running and will not
> start anymore.
>
> It has been running for several weeks until about 5 days
> ago. When I tried to reach it, I discovered that it is no
> longer running. However, attempting to start it via the
> mysqld_safe script simply returns with:
>
> Starting mysqld daemon with databases from /usr/local/mysql/data
> 060402 18:49:55 mysqld ended
>
> [1] Done ./mysqld_safe --user mysql
>
>
> To confirm, the /tmp/mysql.sock file does not exist at this point.
>
> Any ideas on how to get this running again?

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

mysql@karsites.net

2006-04-02, 8:26 pm

Here are some screen snapshots of qps showing mysql server
running on my machine.

I tries to post these to the list, but they went over the
file size limit for the mailing list.

Showing mysql running in memory without using mysqld_safe script:
http://www.karsites.net/KAR/website...ing/mysqld1.jpg

First part of command-line parameters passed to mysqld:
http://www.karsites.net/KAR/website...ing/mysqld2.jpg

Second part of command-line parameters passed to mysqld:
http://www.karsites.net/KAR/website...ing/mysqld3.jpg

Regards

Keith

In theory, theory and practice are the same;
in practice they are not.

On Sun, 2 Apr 2006, Sachin Petkar wrote:

> To: mysql@lists.mysql.com
> From: Sachin Petkar <sachin.petkar@gmail.com>
> Subject: MySQL 4.0.18 on Mac OS X 10.2.8 won't start
>
> For some reason, MySQL 4.0.18 has suddenly stopped running and will not
> start anymore.
>
> It has been running for several weeks until about 5 days
> ago. When I tried to reach it, I discovered that it is no
> longer running. However, attempting to start it via the
> mysqld_safe script simply returns with:
>
> Starting mysqld daemon with databases from /usr/local/mysql/data
> 060402 18:49:55 mysqld ended
>
> [1] Done ./mysqld_safe --user mysql
>
>
> To confirm, the /tmp/mysql.sock file does not exist at this point.
>
> Any ideas on how to get this running again?

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Eric Braswell

2006-04-02, 8:26 pm

Sachin Petkar wrote:
> For some reason, MySQL 4.0.18 has suddenly stopped running and will not
> start anymore.
>
> It has been running for several weeks until about 5 days ago. When I tried
> to reach it, I discovered that it is no longer running. However,
> attempting to start it via the mysqld_safe script simply returns with:
>
> Starting mysqld daemon with databases from /usr/local/mysql/data
> 060402 18:49:55 mysqld ended
>
> [1] Done ./mysqld_safe --user mysql
>
>
> To confirm, the /tmp/mysql.sock file does not exist at this point.

There are several possible reasons for this. One of the most common is
inappropriate permissions on the files in /usr/local/mysql/data (they
need to be readable and writable by the user under which mysql is run,
usually "mysql")

The first thing you should do is check the error log file in
/usr/local/mysql/data, on Mac OS X, usually named <hostname>.err

In a terminal window, typing:

tail /usr/local/mysql/data/example.com.err

will give you the last few lines of this file and likely tell you what
the specific problem is. It's possible you may need to be root or use
sudo <command> to get permissions to read this file.

Another poster suggested verifying that MySQL is not running. In your
case it has clearly stopped, but you can always verify that by using the
ps command:

ps auwx | grep mysql

If it's running, you will see an item with "/usr/local/mysql/bin/mysqld"
in the list.

It was also suggested to us another utility other than safe_mysqld to
start the mysql server. In most cases it is better to use safe_mysqld.
Any special options you need can be specified in /etc/my.cnf. But it
sounds like you are using the default installation, so everything should
just work.

Eric

--
Eric Braswell
Web Manager MySQL AB
Cupertino, USA

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql? unsub...sie.nctu.edu.tw

Sachin Petkar

2006-04-02, 8:26 pm

------ =_Part_4478_15391766
.1144011588880
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thanks to everyone, MySQL is back up and running.
This was definitely enlightening!

Sachin

On 4/3/06, Eric Braswell <ebraswell@mysql.com> wrote:
>
> Sachin Petkar wrote:
> tried
>
> There are several possible reasons for this. One of the most common is
> inappropriate permissions on the files in /usr/local/mysql/data (they
> need to be readable and writable by the user under which mysql is run,
> usually "mysql")
>
> The first thing you should do is check the error log file in
> /usr/local/mysql/data, on Mac OS X, usually named <hostname>.err
>
> In a terminal window, typing:
>
> tail /usr/local/mysql/data/example.com.err
>
> will give you the last few lines of this file and likely tell you what
> the specific problem is. It's possible you may need to be root or use
> sudo <command> to get permissions to read this file.
>
> Another poster suggested verifying that MySQL is not running. In your
> case it has clearly stopped, but you can always verify that by using the
> ps command:
>
> ps auwx | grep mysql
>
> If it's running, you will see an item with "/usr/local/mysql/bin/mysqld"
> in the list.
>
> It was also suggested to us another utility other than safe_mysqld to
> start the mysql server. In most cases it is better to use safe_mysqld.
> Any special options you need can be specified in /etc/my.cnf. But it
> sounds like you are using the default installation, so everything should
> just work.
>
> Eric
>
>
> --
> Eric Braswell
> Web Manager MySQL AB
> Cupertino, USA
>
>

--
Sachin Petkar
Email : sachin.petkar@gmail.com

------ =_Part_4478_15391766
.1144011588880--

Greg 'groggy' Lehey

2006-04-03, 3:27 am

--EcLUEBHJhOmOUQ0C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Monday, 3 April 2006 at 2:29:48 +0530, Sachin Petkar wrote:
> On 4/3/06, Eric Braswell <ebraswell@mysql.com> wrote:
>
> Thanks to everyone, MySQL is back up and running.
> This was definitely enlightening!

Did you establish what the cause of the problem was?

Greg
--
Greg Lehey, Senior Software Engineer
MySQL AB, http://www.mysql.com/
Echunga, South Australia
Phone: +61-8-8388-8286 Mobile: +61-418-838-708
VoIP: sip:4484@sip.mysql.com, sip:0871270137@sip.internode.on.net

Are you MySQL certified? http://www.mysql.com/certification/

--EcLUEBHJhOmOUQ0C
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFEMJcnIubykFB6
QiMRAq+OAJ488/ SYR5vsBqjSu182X7cjwq
9fnACfTbjw
C2H6LW63qlBpdiNphP4g
46c=
=H9fQ
-----END PGP SIGNATURE-----

--EcLUEBHJhOmOUQ0C--

Sachin Petkar

2006-04-03, 3:27 am

------ =_Part_7318_15502926
.1144038073574
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I created the my.cnf file (for some reason, it was nowhere to be found) and
passed it as an argument to mysqld_safe . That's it! Works beautifully
now.

Thanks,
Sachin

On 4/3/06, Greg 'groggy' Lehey <grog@mysql.com> wrote:
>
> On Monday, 3 April 2006 at 2:29:48 +0530, Sachin Petkar wrote:
> not
>
> Did you establish what the cause of the problem was?
>
> Greg
> --
> Greg Lehey, Senior Software Engineer
> MySQL AB, http://www.mysql.com/
> Echunga, South Australia
> Phone: +61-8-8388-8286 Mobile: +61-418-838-708
> VoIP: sip:4484@sip.mysql.com, sip:0871270137@sip.internode.on.net
>
> Are you MySQL certified? http://www.mysql.com/certification/
>
>
>

--
Sachin Petkar
Home : +91 80 4120 8542
Email : sachin.petkar@gmail.com

------ =_Part_7318_15502926
.1144038073574--

Sponsored Links