After repointing a domain to the server that holds a new Drupal installation I got this warning in Drupal:

warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/tmp/mysql.sock) is not within the allowed path(s): (/home/smithand:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/smithand/public_html/includes/file.inc on line 643.

I got this from the hosting company:

“Looking into this their script is trying to access a file, /tmp/mysql.sock, which is actually a symbolic link to a file that is outside of the location the user can access. I'm not familiar with the script but there shouldn't be any need to access the mysql.sock directly. Unfortunately this appears to be a scripting issue and our ability to provide support in that area is limited.”

I've found similar posts on the topic but not the solution that has worked for me. Any ideas?

Thanks
Dickster

Comments

mm167’s picture

could u tell us which hosting company u are using?

Drupal Centric’s picture

I ended up trying to use a different tmp folder which then had write issues so returned to the orignal folder and I'm no longer getting the error. Although now I'm getting:

warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/usr/bin/convert) is not within the allowed path(s): (/home/smithand:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/smithand/public_html/sites/all/modules/imageapi/imageapi_imagemagick.module on line 161.

Drupal Centric’s picture

Panic over, I uninstalled ImageAPI ImageMagick and installed ImageAPI GD2 and upped the memory limit to 96m which got around the issue.

strikehawkecomm’s picture

Referrer: update.php?op=results
is_dir() [<a href='function.is-dir'>function.is-dir</a>]: open_basedir restriction in effect. File(/tmp/mysql.sock) is not within the allowed path(s): (/home/xxxxxxx/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/xxxxxx/public_html/includes/file.inc on line 891.