Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: enchesss on November 11, 2009, 06:20:19 AM
-
After updating the sme server. I was trying to log into the administrator section of a second installation of joomla. The error said unable to access database.
have tried to restart mysql but it will not restart when stopping it says [ok]
but when restarting it says [failed]
1hr later:
Have tried rebooting server and still mysql will not work
Something was happening with mysql and it would not restart even after rebooting!!
I thought that I would have to reinstall mysql or even the sme7.4 but
I used another post that suggested editing /etc/my.conf
I commented out this line:
socket=/var/lib/mysql/mysql.sock
and replaced it with this one:
socket=/tmp/mysqlsock
and the restarted mysql - and everything worked
I then changed things back to normal - e.g
#socket=/tmp/mysqlsock
socket=/var/lib/mysql/mysql.sock
and found that even though my joomla database is completely unable to be accessed I can still phpmyadmin into the server database.
Have reinstalled backup database but that still did not fix everything - I had to reinstall joomla too
everything working now though - still some tidying up though.
Anyone know what may have happened cause I have no idea (but that is not unusual)
-
That is not the proper solution, you should look through the logfiles and find the proper reason why MySQL is not starting. This is a work around that will fail on updates as your configuration file is overwritten in such cases.
Start by looking through /var/log/messages for clues. if you have problems interpreting your logs perhaps we can help.
-
@enchesss
I would also add:
- please don't edit and edit again your posts..
- please report such things in bugzilla.. you will be steered in the right direction to solve your problems
thank you
-
Thanks - Will follow your instructions IF this happens again. But everything has been fine with the server (as usual).
-
Thanks - Will follow your instructions IF this happens again. But everything has been fine with the server (as usual).
I seriously advice you to investigate now, as now you will have the relevant log files available, which you might not have in the future when the proplem re-appears. With your current solution the problem will definitely re-occur, doing like you do now is short-sighted.
-
Thanks,
Hve looked at log file and can not see anything.
Should I post the mysqld log for you?
-
Thanks,
Hve looked at log file and can not see anything.
Should I post the mysqld log for you?
If there is nothing in it we have no use for it either...