MySQL Server startup issues

[Lazy Hill Wineries]

For some reason I cannot get my MySQL server to start. It has been
running fine until Friday, when we has a strange issue with the
Solaris server which it is running on. The server had a few files get
their chmod setting messed up and now after fixing that, MySQL won't
start.

Exerpt from neuro18.err:

040830 15:55:19 mysqld started
040830 15:55:19 Can't start server : UNIX Socket : Permission denied
040830 15:55:19 Aborting

040830 15:55:19 /usr/local/mysql-standard-4.0.20-sun-solaris2.8-sparc/bin/mysqld:
Shutdown Complete

040830 15:55:19 mysqld ended

ps -ef|grep mysql yeilds no other mysqk processes running.

ls -l in /usr/local/mysql yeilds:

-rw-r--r-- 1 root mysql 19106 May 13 20:14 COPYING
-rw-r--r-- 1 root mysql 8403 May 13 20:14 INSTALL-BINARY
-rw-r--r-- 1 root mysql 1937 May 13 19:53 README
drwxr-xr-x 2 root mysql 1536 May 13 21:59 bin
-rwxr-xr-x 1 root mysql 773 May 13 21:59 configure
drwxrwxr-x 9 mysql mysql 512 Aug 30 15:55 data
drwxr-xr-x 2 root mysql 512 May 13 21:59 docs
drwxr-xr-x 2 root mysql 1536 May 13 21:59 include
drwxr-xr-x 2 root mysql 512 May 13 21:59 lib
drwxr-xr-x 3 root mysql 512 May 13 21:59 man
drwxr-xr-x 6 root mysql 512 May 13 21:59 mysql-test
drwxr-xr-x 2 root mysql 512 May 13 21:59 scripts
drwxr-xr-x 3 root mysql 512 May 13 21:59 share
drwxr-xr-x 5 root mysql 1024 May 13 21:59 sql-bench
drwxr-xr-x 2 root mysql 512 May 13 21:59 support-files
drwxr-xr-x 2 root mysql 512 May 13 21:59 tests

Any help is appreciated. Thanks

Chad

[Lazy Hill Wineries]

As a follow up to my previous post, I have figured out that MySQL will
start as root but not as the mysql user. Any ideas?

Thanks

Chad

[GQ]

la******@chadandtrish.com (Lazy Hill Wineries) wrote in message news:<e9**************************@posting.google. com>...

As a follow up to my previous post, I have figured out that MySQL will
start as root but not as the mysql user. Any ideas?

Thanks

Chad

Hi,

Check the my.cnf file that is used to make sure you have permision on
the socket file (...sock in /tmp ?) and the pid file (in data-dir ?).
Also check in the data directory for the error file.

GQ