Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I tried installing the mySQL Binary on Slackware 10.2 (w/ fluxbox if that matters).. I just downloaded it, tar -xzf'ed it, then ./configure;make;make installed it... I thought that would be all I needed, but whenever I try to start up the daemon, I get this error:
Code:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
Help plox? I don't know where the mysql.sock file is normally installed, then I can just start mysql up with a -S /normal/path/to/mysql.sock...
i just searched LQ for that exact error message, and got 70 exact identical questions... you might like to try that next time. the answer to all those threads... start the mysql service. all you'd doing is starting the client, not the daemon.
I think you forget to create the initial database. Have a look in /etc/rc.mysqld, the command is mentioned there (something like mysql_installdb or so).
I did, I ran the commands in the rc.mysqld file a while back. Created a password for the mysql user and everything.. I've done everything it says to do in the files, but I still get that error.
mysql@rawrcore:~$ Starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/run/mysql/mysql.pid
061111 15:40:32 mysqld ended
^^ That's the error I get when I run mysql_install_db. Where can I get that file?
Is that the exact error message? It seems that there is a space in the filename, which probably shouldn't be there.
Just to clarify the PID issue: the Process ID (PID) of many services/daemons are stored in files in /var/run when the service is started. This makes it very easy to:
1. stop the service (just executes a "kill" or "killall" on the stored PID)
2. check if the service is still running (by checking if the PID file exists or not).
So, when you start mysqld, it'll create the PID file in /var/run. In your case, mysqld then stopped immediately and erased the PID file (because the Process ID stored inside it is no longer valid).
Anyways, it seems that mysqld is starting allright, so no execution permission issue. It just immediately stops, probably caused by an error or something.
Maybe you can check out the MySql log files (if you don't know where they're stored, search in /var/log or on the MySql website). It should give you some indication why mysqld fails to start.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.