Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Single page permanently cached and unable to access anything else #74

Open
tanc opened this issue Oct 22, 2014 · 9 comments
Open

Single page permanently cached and unable to access anything else #74

tanc opened this issue Oct 22, 2014 · 9 comments

Comments

@tanc
Copy link

tanc commented Oct 22, 2014

Hard to write a decent 1 line title for this issue so feel free to change it. The problem:

After rebuilding the box from latest master I can't load any new pages after the server has presented its first page.

For example, if I visit the Drupal 8 installer at http://l.testdomain.dev/core/install.php I get the installer page as expected, but when I click on the 'Save and continue' button, even though the url changes I get served the exact same page.

I can then try to load a completely different page unrelated to Drupal, for example a phpinfo() test file and the server will continue to present the Drupal 8 installer page. Now when I issue an apachectl restart (with vagrant ssh -c "sudo apachectl restart") and reload the page I see the output of phpinfo() as expected. Then I try loading the D8 installer again but I see the output of phpinfo()!

Any idea what is causing this odd behaviour?

@darthsteven
Copy link
Member

Oh, random!

Do you have Varnish enabled in the stack?

@tanc
Copy link
Author

tanc commented Oct 22, 2014

My config.yml:

sites: "sites"
databases: "databases"
memory: 2048
with_gui: false
ip: "192.168.50.4"
php_version: "5.5"
mysql_version: "5.6"
webroot_subdir: "/web"
box_name: "parrot_55"
varnish_enabled: false

@darthsteven
Copy link
Member

:(

@tanc
Copy link
Author

tanc commented Oct 22, 2014

There are two varnish processes running. I've just done a vagrant destroy and vagrant up and the same behaviour is still showing. Very odd.

@darthsteven
Copy link
Member

Does using the d1f1c7b commit of parrot fix the issue?

@tanc
Copy link
Author

tanc commented Oct 22, 2014

Ran: service varnish stop
Still same problem but now no varnish running.

I don't think that commit helps as I've built this box off master which includes that commit.

@tanc
Copy link
Author

tanc commented Oct 22, 2014

Interesting, I've just rebuild with PHP54 and MySQL55 and all good!

sites: "sites"
databases: "databases"
memory: 2048
with_gui: false
ip: "192.168.50.4"
php_version: "5.4"
mysql_version: "5.5"
webroot_subdir: "/web"
box_name: "parrot_54"
varnish_enabled: false

Hope that helps a bit with debugging if you're able to replicate? For now I'm happy with this combination so I'll get on with what I was doing!

@darthsteven
Copy link
Member

Lovely stuff, thanks!

@tripox
Copy link
Contributor

tripox commented Mar 19, 2015

Any solution on this yet?

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

No branches or pull requests

3 participants