4
  • Arch Linux 2011.08.19 (Linux 3.4.2 i686)
  • Apache 2.2.22 with SuExec
  • PHP 5.4.4 (cli) via FastCGI

My sites were all working fine earlier… I’m not sure when it happened because I noticed it over a week later (I’m guessing perhaps after a system upgrade), but all my VirtualHosts went offline with the dreaded “Premature end of script headers: php-fcgid-wrapper” 500 error.

SuExec logs gave me this for each site:

[2012-07-16 00:45:02]: uid: (1001/site) gid: (1001/site) cmd: php-fcgid-wrapper
[2012-07-16 00:45:02]: command not in docroot (/var/www/site/fcgi-bin/php-fcgid-wrapper)

This isn’t (or at least shouldn’t be) true… I automatically compile Apache with --with-suexec-docroot=/srv/www set. Still, I tried a sanity check, to see what docroot SuExec actually thought it had:

$ suexec -V
suexec policy violation: see suexec log for more details

For which the logs claimed:

[2012-07-16 01:07:52]: too few arguments

Tried it with sudo as well; same thing. So, even this makes no sense, and prevents me from being able to diagnose the problem properly.

Another thing I tried was moving everything from /srv/www to /var/www, the default docroot, to see if maybe it had reverted to the raw repository version during the upgrade. Updated my VirtealHosts, restarted Apache, but still got the same 500 errors.

What else could be causing this?

Community
  • 1
Hugh Guiney
  • 245
  • 1
  • 8
  • 20
  • Go back to a known good configuration. Create a testing environment from it and then work your way forward testing as you go. – user9517 Jul 16 '12 at 07:04
  • This *was* my last known good configuration. I honestly don’t know what changed… – Hugh Guiney Jul 16 '12 at 18:16
  • Erm you say ... perhaps after a system upgrade ... surely you know if you did that or not ? – user9517 Jul 16 '12 at 18:20
  • I did do that, but I don’t know that that is actually the cause of the problem; it’s just the only thing I can remember changing. Apache itself did not upgrade, and I didn’t edit any of my config files. I also don’t do full system backups currently, and Arch is rolling release anyway, so it’s non-trivial for me to attempt to recreate a previous server state here—I’d have to downgrade all of my packages manually. I’m willing to try it, but I think that’s a last resort. – Hugh Guiney Jul 16 '12 at 18:35

4 Answers4

2

You don't need to recompile it. You can use this package to set a custom path on debian or ubuntu:

apt-get install apache2-suexec-custom

After installing the package, there is a special directory, where you can set the suexec path for every user. There should be an example file für www-data user:

/etc/apache/suexec/<some-user-name>

If you don't have Debian or Ubuntu, you have to look for such a package or recompile suexec with the right docroot (see suexec doc). The param is:

--with-suexec-docroot=DIR

You have to check, how to do it for your distro.

Fa11enAngel
  • 303
  • 3
  • 8
1

Find the fcgid configurations with this command:

/usr/lib/apache2/suexec -V

-D AP_DOC_ROOT="/var/www"
-D AP_GID_MIN=100
-D AP_HTTPD_USER="www-data"
-D AP_LOG_EXEC="/var/log/apache2/suexec.log"
-D AP_SAFE_PATH="/usr/local/bin:/usr/bin:/bin"
-D AP_UID_MIN=100
-D AP_USERDIR_SUFFIX="public_html"

The wrapper must be written in the directory tree of: AP_DOC_ROOT to be accessed and run.

ppostma1
  • 111
  • 3
1

There's a www-data file (/etc/apache2/suexec/www-data) with 2 lines:

/var/www
/public/cgi-bin/

you can change that lines to what you prefer

Pol Hallen
  • 1,055
  • 2
  • 13
  • 22
0

You need to recompile suexec.c --with-suexec-docroot=/srv/www

Andrew Smith
  • 1,123
  • 13
  • 23