Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Reviewing logfiles to figure out why my site was down a few days ago, I found hundreds of lines like these (partially redacted with "x"):

[Fri Nov 27 23:14:36 2009] [error] [client] PHP Warning: require_once(): open_basedir restriction in effect. File(/var/www/xxx/xxx.php) is not within the allowed path(s): (\xa0\x99\xc4) in /var/www/xxx/index.php on line 17

Note that the open_basedir value is binary, so it won't match anything.

No (admin) change was made on the server to cause this, and none was made to stop it.. it apparently resolved itself on its own (apache or other services weren't restarted/reloaded). The open_basedir directive in the apache conf file looks like this:

php_admin_value open_basedir /var/www:/usr/share/php

What would cause the open_basedir value to reload with a binary value, or where can I even start to troubleshoot this? This is the second time in the last two weeks this problem has arisen.

Apache version: 2.2.8, PHP: 5.3.0, Linux 2.6.24-23

share|improve this question
up vote 0 down vote accepted

The problem is apparently due to this bug.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.