Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

claw-playbook - drupal error #801

Closed
Natkeeran opened this issue Feb 14, 2018 · 4 comments · Fixed by Islandora-Devops/islandora-playbook#59
Closed

claw-playbook - drupal error #801

Natkeeran opened this issue Feb 14, 2018 · 4 comments · Fixed by Islandora-Devops/islandora-playbook#59

Comments

@Natkeeran
Copy link
Contributor

claw-playbook gets deployed without error. However, when I go to localhost:8000, the following error message gets thrown:

handle($request); $response->send(); $kernel->terminate($request, $response); 
commit 00fa2321fe8c2840ab3882d7f83e3d05ec3088f1
Author: Natkeeran <[email protected]>
Date:   Mon Feb 12 11:11:58 2018 -0500
@Natkeeran Natkeeran added bug and removed bug labels Feb 14, 2018
@whikloj
Copy link
Member

whikloj commented Feb 14, 2018

@Natkeeran I just tried that and I was ok.

> git log -n 1
commit 00fa2321fe8c2840ab3882d7f83e3d05ec3088f1 (HEAD -> master, origin/master, origin/HEAD)
Author: Natkeeran <[email protected]>
Date:   Mon Feb 12 11:11:58 2018 -0500

    Update README.md (#54)
    
    Update instructions about deploying to port 80

Once it came up.

> curl -I http://localhost:8000
HTTP/1.1 200 OK
Date: Wed, 14 Feb 2018 18:27:01 GMT
Server: Apache/2.4.18 (Ubuntu)
X-Powered-By: PHP/7.0.25-0ubuntu0.16.04.1
Cache-Control: must-revalidate, no-cache, private
X-Drupal-Dynamic-Cache: UNCACHEABLE
X-UA-Compatible: IE=edge
Content-language: en
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Expires: Sun, 19 Nov 1978 05:00:00 GMT
X-Generator: Drupal 8 (https://www.drupal.org)
X-Drupal-Cache: HIT
Content-Type: text/html; charset=UTF-8

@MarcusBarnes
Copy link

I've been able to reproduce the behaviour @Natkeeran reported in #801 (comment). We are investigating a few things to see if we can determine what may be going on.

@Natkeeran
Copy link
Contributor Author

@whikloj @MarcusBarnes

Installing this module libapache2-mod-php7.0 seems to fix the issue. Reference

@mjordan
Copy link
Contributor

mjordan commented Feb 27, 2018

@Natkeeran I hit this too and installing libapache2-mod-php7.0 worked for me too (I chose to keep the locally modified php.ini).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants