| LinHES Forums http://forum.linhes.org/ |
|
| moved /var and /tmp, now mysql is hosed http://forum.linhes.org/viewtopic.php?f=5&t=9787 |
Page 1 of 1 |
| Author: | jeffwight [ Mon Apr 24, 2006 8:10 pm ] |
| Post subject: | moved /var and /tmp, now mysql is hosed |
My root directory was filling up, so I moved /var and /tmp to their own partitions to free up some space. Now mysql is hosed. I'm not conversant in mysql, so I don't know how to fix it. I suspect that I goofed up file ownership or permissions in either /var or /tmp, but I don't know where I went astray. Can some kind soul point me in the right direction? I'm running knoppmyth R5A16. Thanks, -Jeff (more details below) When I run 'mythbackend', I get the following: root@mythtv:/var/run# mysql ERROR 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) root@mythtv:/var/run# mythbackend 2006-04-24 19:07:51.541 New DB connection, total: 1 2006-04-24 19:07:51.544 Unable to connect to database! 2006-04-24 19:07:51.544 Driver error was [1/2002]: QMYSQL3: Unable to connect Database error was: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 2006-04-24 19:07:51.549 Failed to init MythContext, exiting. |
|
| Author: | lordsnooty [ Tue Apr 25, 2006 4:40 am ] |
| Post subject: | |
So mysql isn't starting. First, try a manual start as root to see if any messages are revealed: Code: /etc/init.d/mysql start
Also take a look at the mysql log files - /var/log/mysql/* and /var/log/mysql.* - to see if any clues exist. |
|
| Author: | Alibloke [ Tue Apr 25, 2006 6:40 pm ] |
| Post subject: | |
I just moved my /var also...but I used the command cp -a which preserves all permssions (-a stands for archive). All seems to be working. Try that instead perhaps, or have you deleted the old /var by now? |
|
| Author: | alien [ Wed Apr 26, 2006 2:07 am ] |
| Post subject: | |
If your root directory is filling up, it may be because you have a large sql log file (mine hit over 2G before my system crashed). Take a look in /var/log/mysql/ and see if there are any unusally large log files. I deleted mine (mysql.log I think) and linked it to /dev/null. This takes a reboot to take affect and free up disk space. Note: You might want to check the log file to see what is filling it up. In my case, I was doing repeated music scans of ~300 albums as I was re-organizing my collection. Each sql query was logged and never cleaned up. You can also do a search for "logrotate". There is a post somewhere on how to set it up. I took the easier route and got rid of the log file all together as it didn't seem to contain anything useful. Allen |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|