After Update of ISPConfig data base error

[DaRKNeSS666NL]

Please help me!
I have run the update of ispconfig but now I cant login any more and my joomla sites giving error
Code:

Database Error: Unable to connect to the database:Could not connect to MySQL

any Ideas are welcome.

Some more info:
Code:

mysql: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted

__________________
Updating my server to Debian Squeeze, so here I go again...

[DaRKNeSS666NL]

Also can not log in with phpmyadmin

#2002 - The server is not responding (or the local MySQL server's socket is not correctly configured)

[DaRKNeSS666NL]

And this is the output when I try to start msql again:

server1:~# /etc/init.d/mysql start
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
Starting MySQL database server: mysqld/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 ./usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
 failed!

[DaRKNeSS666NL]

I have found in an other forum to remove my my.cnf file. So I renamed the file and now I am able to receive mails and see my sites again.

But I am still thinking there are some isus with the server can sombody give me some clues please....

TIA

Appie

[dclardy]

You probably had an issue with your my.cnf file. I am guessing that you updated something on the software side that does not involve ISPConfig.

[DaRKNeSS666NL]

Originally Posted by dclardy

You probably had an issue with your my.cnf file. I am guessing that you updated something on the software side that does not involve ISPConfig.

Thanks for the quick answer,

Now its running without the my.cnf file but thats not the way it should be I am guessing.. or doesn't it matter I renamed the file.

[till]

Does the directory /etc/mysql/conf.d/ exist? If not, create it.

[DaRKNeSS666NL]

Originally Posted by till

Does the directory /etc/mysql/conf.d/ exist? If not, create it.

It doesn't exist, I have seen it in my backup but there was noting in it so I guessed it was left there by some proces.
I will create it and test it again with the my.cnf file.
Till any ideas what happened here with the update?

TIA Appie

[DaRKNeSS666NL]

Originally Posted by DaRKNeSS666NL

I will create it and test it again with the my.cnf file.
Till any ideas what happened here with the update?

That did the trick indeed, thanks all

Appie

[till]

It doesn't exist, I have seen it in my backup but there was noting in it so I guessed it was left there by some proces.

The directory is normally empty. It exists as an option to extend my.cnf.

Till any ideas what happened here with the update?

The update was aborted as mysql was not running. Just restart the update process after you fixed mysql.