Todd and Guys,
Your advice helped me too. I think either Apple screwed up when set up
/tmp directory to be writeable by root only or since MySQL package has bug
or shall be installed ONLY as root user.
- Nicos
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
Nicos,
Actually, MySQL should be installed by an administrator, but it should
be executed by root, which would permit the writing to the tmp dir.
Meaning everytime you kick off MySQL server, you'll need to do so as
root. This is usually how I dow it:
cd /usr/local/mysql
sudo echo
sudo ./bin/my
I figured out what happened, though I don't know when it happened...
I had screwed up the permissions for the /tmp/ directory, so the mysql
user could not create the socket it needed there. A well-placed chmod
and things are back in working order.
Thanks to all for the suggestions,
Todd
--
MySQ
Check your permissions in /usr/local/mysql, I think the package leaves
some incorrectly set.
The exact problem is usually logged in
/usr/local/mysql/data/.err this file is invaluable
Cheers!
--s
On Wednesday, July 2, 2003, at 09:24 AM, Todd O'Bryan wrote:
OK. I've verified that no mysqld is
OK. I've verified that no mysqld is running using Egor's command from
below, and
by using netstat (which someone else suggested) there is nothing
listening on port 3306.
Any new ideas?
Thanks,
Todd
On Wednesday, July 2, 2003, at 09:51 AM, Egor Egorov wrote:
"Todd O'Bryan" <[EMAIL PROTECTED]>
"Todd O'Bryan" <[EMAIL PROTECTED]> wrote:
> Something bad has happened. MySQL was up and running on my machine, but
> now it's not and I have a chicken and egg problem that I can't seem to
> solve...
>
> I uninstalled any old versions of MySQL and I'm using the package
> installer of version 4.
If you did not shutdown the server prior to the upgrade, you could have
left mysqld running, even after its socket was removed.
Use ps to see if mysqld is still running, and kill it if necessary.
Todd O'Bryan wrote:
Something bad has happened. MySQL was up and running on my machine,
but now it'
Something bad has happened. MySQL was up and running on my machine, but
now it's not and I have a chicken and egg problem that I can't seem to
solve...
I uninstalled any old versions of MySQL and I'm using the package
installer of version 4.0.13 on Mac OS 10.2.6.
When I "cd /usr/local/" and "s
