Shared hosting: Read timeout issue during initial setup

[olibur (Oliver Burkhalter)]

I try to install Neos on a Shared Hosting. But I get following errors in the error_log while calling the /setup page:

...mod_fcgid: read data timeout in 35 seconds...
Premature end of script headers: index.php

The Hosting provider increased then the max_execution_time to 240 seconds, but without any success.

After timeout I receive the following error message in the browser:

Application ErrorThe Flow application could not be launched.

My provider also mentioned that the PHP functions system() and shell_exec() are not available on their Shared hostings.

Could this be the issue for the read timeouts? Are there any workarounds for this?

Thanks for your help!

[christianm (Christian Müller)]

But the exec() function is enabled? That should be the only thing needed actually.

Hard to say what the actual error is without seeing a log. Can you check if Neos wrote logs in Data/Logs?
I know there was a problem with fcgi but that was fixed months ago.

[olibur (Oliver Burkhalter)]

Yes the *exec()" function is enabled.

Unfortunately Neos does not write any logs in Data/Logs, I just can see the mentioned logs in the error_logs file with the read timeout issue.

Are there still any other “debugging hints” for the Shared Hoster?

You can see the issue also here: http://test.islandkids.ch/setup

Or see PHP info here (maybe this helps too for some analysis): http://test.islandkids.ch/pi.php

[olibur (Oliver Burkhalter)]

I’ve found the solution…I’m a bit “blind”

I had the following configuration:

core:
  phpBinaryPathAndFilename: /opt/atomic/atomic-php56/root/usr/bin/php-cgi

But if I changed it to:

core:
  phpBinaryPathAndFilename: /opt/atomic/atomic-php56/root/usr/bin/php

just using the “php” binary, then it worked…

Thanks @christianm for your hints.