Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > General

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Thread Tools Display Modes
Prev Previous Post   Next Post Next
Old 28th January 2011, 01:09
MrCompTech MrCompTech is offline
Join Date: Jul 2010
Posts: 92
Thanks: 1
Thanked 20 Times in 9 Posts
Default open_basedir restriction in effect. File() is not within the allowed path(s)

open_basedir restriction in effect. File() is not within the allowed path(s)

Using ISPConfig3, Fedora 13, Wordpress 3.0.4

Have severl Wordpress sites, all have this problem.
Have several Joomla sites with no problems.

Isn't there supposed to be a file listed in the error message in the parenthesis - 'Files()'?

This error causes the log files to grow 20KB to 50KB every time a page on the site is displayed including the website admin pages!

The settings for the website are:

CGI - unchecked
SSI - unchecked
SuEXEC - checked
Own Error-Documents - unchecked
Auto-Subdomain - none
SSL - unchecked
PHP - Fast-CGI
Active - Checked

Linux User - web34
Linus Group - client1
Allow Override - All
PHP open_base_dir -

Apache directives - FcgidMaxRequestLen 5000000

While troublesghooting this issue I found the error.log file for this website to be 22741993435 bytes long! - Ouch!

To establish a baseline I:
disconnected the LAN from the Internet,
logged out of the wp admin
had no open browser windows to this web site

I then open one window to the site http://25freempsdownloads.com

And checked the log file. It grew by 54304 bytes! This is definitly an uh-oh!

In the logs the same basic error messages kept repeating over and over and over!
With only slightly differences that being the file name and the line number -

[Thu Jan 27 14:01:55 2011] [warn] [client]
mod_fcgid: stderr: PHP Warning: require():
open_basedir restriction in effect. File() is not within the allowed path(s):
) in
/var/www/clients/client1/web34/web/wp-settings.php on line 19

On error lines a 'referrer' is listed as

I changed the theme to the default Wordpress theme and the same error messages appeared in the log file and it increase by 98KB.

In this last error message it seems like it is saying that file being called on line 19 by the script wp-settings.php is not in the path.
Am I interpreting this error message correctly? It doesn't seem that this could be correct.

In this error message line 19 is -
require( ABSPATH . WPINC . '/load.php' );

Other lines that were referred to in the error messages are -
line 20 require( ABSPATH . WPINC . '/default-constants.php' );
line 21 require( ABSPATH . WPINC . '/version.php' );
line 66 require( ABSPATH . WPINC . '/compat.php' );
line 67 require( ABSPATH . WPINC . '/functions.php' );
line 68 require( ABSPATH . WPINC . '/classes.php' );

The pages come up and they don't seem to be missing anything.

I 'reset' the error.log file by 'echo > error.log'.
Is there any way to put a limit on how large the error log will grow?

To be sure the ownship was correct I ran:
chown -R web34:client1 /var/www/clients/client1/web34/web

Anybody have an idea has to what might be causing this?

Last edited by MrCompTech; 28th January 2011 at 03:39.
Reply With Quote
Sponsored Links


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Postfix delivery problem erebus Installation/Configuration 8 29th July 2014 21:17
All my mail is going to /var/mail/vmail _sluimers_ Installation/Configuration 21 10th January 2011 14:21
High on Lenny - Lvm Mount Problem Serverman Technical 1 23rd June 2009 17:26
debian etch courier pop3 issue docean Installation/Configuration 6 20th March 2008 16:38
Chroot SSH + ISPConfig Norman Installation/Configuration 27 26th March 2007 04:40

All times are GMT +2. The time now is 12:12.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.