Geeklog Forums

I\'m getting the failed opening error that is usual when paths are wrong. However this occured overnight. I\'m suspecting changes made by my host as oscommerce is hosed as well.

What changes could they have made to hose it?

PHP info at:

http://www.circadian.com/catalog/info.php

Can\'t see anything out of the ordinary - open basedir is off, as is safemode. Btw, kerin.us works for me - or where you talking about another site? bye, Dirk

Yep, it's a company intranet I run - I didn't want to give the URL as I'm trying to keep it hidden from search engines etc.

Full message is:

Fatal error: Failed opening required '/home/virtual/site273/fst/var/www/html/xxxxxxxxx/config.php' (include_path='.:/php/includes:/usr/share/php' in /var/www/html/xxxxxx/lib-common.php on line 65

With directory names changed to xxxx.

On OScommerce the message is:

Warning: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /var/www/html/catalog/includes/functions/database.php on line 19

Warning: MySQL Connection Failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) in /var/www/html/catalog/includes/functions/database.php on line 19
Unable to connect to database server!

I can get into the SQL server remotely with no problem.


Thanks, Alex.

Assuming that the path is correct: Check permissions and ownership of the file and all directories involved. As for the SQL error: That sounds like either MySQL is not running at all or your settings are not correct (trying to connect to the wrong server maybe?). bye, Dirk

Sooo,

As suspected my host had made some \"security\" upgrades to the ensim hosting software. This resulted in a number of things:

Using \'localhost\' as for the database location is now no good - must use 127.0.0.1

The path names, which were previously full path names (to the root of the server with all of the sites - /site273/fst/var/www/html/ etc. now just have to be:

/var/www/html/ etc.

This affected php and my cgi scipts which need the server root.

FYI: I\'m hosting with webintellects.com
I solved the problem 24 hours after they started looking at it....

Thanks Dirk for your advice - it sent me down the right road.

Alex Kerin.