I understand this may not be a Bedrock issue, as no one has likely seen this particular error message. I thought I would post anyway, just in case anyone has some insight.
When I deploy my project – whether I’ve a) included dist etc in my repo and deployed using a service like deployhq.com, or b) just used Capistrano, I get a white screen with the words “wrong file”. That’s it. It’s a laughably unhelpful error message. This happened on my current active project (see the error here: theagsc.com.au), so I thought I’d try a nice clean install of Bedrock as a test to determine if I’d done something wrong in my files.
Turns out the bare bones install throws the same error for me (bedrocktest.theagsc.com.au).
I scrutinized the error log as best I could, but found nothing helpful.
/etc/apache2/error.log – My last attempt was today, March 8th. I’ve included the other dates in case they reveal anything helpful.
[Sat Mar 07 00:50:03.134973 2015] [mpm_event:notice] [pid 12754:tid 140551952095104] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
[Sat Mar 07 00:50:03.135220 2015] [core:notice] [pid 12754:tid 140551952095104] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 07 00:55:00.489361 2015] [mpm_event:notice] [pid 12754:tid 140551952095104] AH00491: caught SIGTERM, shutting down
[Sat Mar 07 00:55:01.614084 2015] [mpm_prefork:notice] [pid 20139] AH00163: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
[Sat Mar 07 00:55:01.614284 2015] [core:notice] [pid 20139] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 07 00:55:02.055230 2015] [mpm_prefork:notice] [pid 20139] AH00169: caught SIGTERM, shutting down
[Sat Mar 07 00:55:02.232231 2015] [mpm_prefork:notice] [pid 20221] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.6 configured -- resuming normal operations
[Sat Mar 07 00:55:02.232350 2015] [core:notice] [pid 20221] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 07 00:56:38.583990 2015] [mpm_prefork:notice] [pid 20221] AH00169: caught SIGTERM, shutting down
[Sat Mar 07 00:56:39.650503 2015] [mpm_prefork:notice] [pid 20292] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.6 configured -- resuming normal operations
[Sat Mar 07 00:56:39.650616 2015] [core:notice] [pid 20292] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 07 00:57:07.614435 2015] [:error] [pid 20297] [client 75.130.145.240:62298] script '/var/www/html/info.php' not found or unable to stat
[Sat Mar 07 07:50:16.163793 2015] [mpm_prefork:notice] [pid 20292] AH00169: caught SIGTERM, shutting down
[Sat Mar 07 07:50:28.376589 2015] [mpm_prefork:notice] [pid 1011] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.6 configured -- resuming normal operations
[Sat Mar 07 07:50:28.388723 2015] [core:notice] [pid 1011] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 07 08:26:29.454250 2015] [mpm_prefork:notice] [pid 1011] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Sat Mar 07 08:26:29.615688 2015] [mpm_prefork:notice] [pid 1011] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.6 configured -- resuming normal operations
[Sat Mar 07 08:26:29.615728 2015] [core:notice] [pid 1011] AH00094: Command line: '/usr/sbin/apache2'
[Sat Mar 07 08:38:46.636104 2015] [mpm_prefork:notice] [pid 1011] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Sat Mar 07 08:38:46.756129 2015] [mpm_prefork:notice] [pid 1011] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.6 configured -- resuming normal operations
[Sat Mar 07 08:38:46.756162 2015] [core:notice] [pid 1011] AH00094: Command line: '/usr/sbin/apache2'
[Sun Mar 08 06:41:13.387093 2015] [mpm_prefork:notice] [pid 1011] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
I’m not sure if there are any other helpful file or logs to share? Any help would be amazing, this may the last bug I have to squash before the finish line!
Thanks guys.