This is a discussion on replacing missing mysql.sock (FreeBSD OS) within the MySQL Database forums, part of the Database Forums category; Don't you hate it when you have a missing sock? I'm hoping there's someone (anyone!) who knows ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Don't you hate it when you have a missing sock?
I'm hoping there's someone (anyone!) who knows FreeBSD who can advise me how to recreate the MySql socket file in its default location (in my case, in /tmp/mysql.sock). Seems my /var partition got over-full last night and evidently brought down the server. I guess that was the cause; I can't see any other. Since last night, I haven't been able to restart MySql. This effects of my sites, since most of my content now runs on Drupal, which requires MySql. One of the things that I did today was move MySql data files to my /usr partition, where there's more room, with a sym link to its default location at /var/db/mysql; careful to chown the directory and files to the user mysql. I also tried deinstalling and then reinstalling MySql from ports, hoping that would resurrect the socket, but no go. I've googled and scoured the mysql.com, to no avail. If there is an answer out there (and there undoubtedly is, I haven't been able to find it.) Any suggestions would be sincerely appreciated. I know there are a lot of a number of subscribers here who are more expert than me with MySql. I'd really like to get this thing back ASAP, if possible, not just for my own site, but also for the benefit of the people and organizations who relying on me as a host. Many thanks. Tom P.S. For the record, I'm running a mixture of Drupal sites; some v4.7.x and others v5.x. OS is FreeBSD 6.1 on Apache 1.3.24, PHP 5.1.2 mod_perl/1.29, MySql 5.0.18, with Gallery 2.1, TNG 6.1, and PmWiki 2.0.13. |
|
|||
|
tomrue wrote:
> /tmp/mysql.sock touch /tmp/mysql.sock Will suffice. Make sure mysql has permission to enter /tmp and read/write to mysql.sock -- Brian Wakem Email: http://homepage.ntlworld.com/b.wakem/myemail.png |
|
|||
|
Brian
Thanks for the reply. I tried your suggestion, even chmod 777 mysql.sock. Still no go. I'm starting to think it has something to do with some log files that may have been damaged by the disk overflow last night. I'll keep poking. Any other suggestions most welcome. Thanks again. -- http://tomrue.net On Apr 21, 5:29 pm, Brian Wakem <n...@email.com> wrote: > tomrue wrote: > > /tmp/mysql.sock > > touch /tmp/mysql.sock > > Will suffice. > > Make sure mysql has permission to enter /tmp and read/write to mysql.sock > > -- > Brian Wakem > Email:http://homepage.ntlworld.com/b.wakem/myemail.png |
|
|||
|
>Don't you hate it when you have a missing sock?
> >I'm hoping there's someone (anyone!) who knows FreeBSD who can advise >me how to recreate the MySql socket file in its default location (in >my case, in /tmp/mysql.sock). Seems my /var partition got over-full >last night and evidently brought down the server. I guess that was the >cause; I can't see any other. My observation is that when you shut down the server process, the socket goes away, and when you start it up again, it comes back. I'm running FreeBSD 6 now, but I've been running FreeBSD and MySQL for a long time and this hasn't changed recently. Now, if the server fails to start for some reason, like passing it bogus command-line options which I've done a few times, it will quit and not create the socket. Check permissions on /tmp and /var/db/mysql to make sure the server won't have problems trying to create the socket or log files. Also make sure there's a decent amount of disk space. >Since last night, I haven't been able to restart MySql. This effects >of my sites, since most of my content now runs on Drupal, which >requires MySql. One of the things that I did today was move MySql data >files to my /usr partition, where there's more room, with a sym link >to its default location at /var/db/mysql; careful to chown the You need to be really careful about permissions and ownership here, as you've noted. >directory and files to the user mysql. I also tried deinstalling and >then reinstalling MySql from ports, hoping that would resurrect the >socket, but no go. I've googled and scoured the mysql.com, to no >avail. If there is an answer out there (and there undoubtedly is, I >haven't been able to find it.) |
![]() |
| Thread Tools | |
| Display Modes | |
|
|