I've got a pretty stable Mercury instance running (I forget which version). I've not got any production sites on it though I do plan to leverage a Mercury box for that soon.
On this box I have a strange quirk that I can't seem to figure out. If I've not loaded a page for several hours it sends me output of the home page in a /node format instead of the node I've set for the home page. Hit refresh and it does what it's supposed to do.
I've disabled all caching, disconnected Varnish so just Apache is serving the page and I still get this display. I even put the site into maintenance mode and it still flashes all the nodes instead of loading the correct theme. Could this be a pressflow issue? It's really hard for me to diagnose since I can't figure out how to duplicate it except to walk away for a few hours. But it's bad when the client comes to check on development of the site and it looks like the theme is broken...
Anyone else have any thoughts?
Comments
thats strange ... I am going
thats strange ... I am going to start testing a multisite this afternoon. However my idea was to not use the pressflow install in the ami and rather setup an aegir build with pressflow platforms. So my case may be a bit different however it should still be a test of the multisite inside the mercury ami. I will report back on my tests, id be interested to hear what else you find on this too. What a strange bug!
I'm wondering if it's
I'm wondering if it's something in the Apache config with the Vhosts? It's still doing it although I'm starting to think that it's cookie based now????
Doug
@nullvariable | www.nullvariable.com
This is unlikely to be a
This is unlikely to be a Pressflow-specific issue, but you can try switching temporarily back to Drupal core to verify this.
I have not noticed this bug
I have not noticed this bug in my tests.. although my main Aegir platfrom is not pressflow all the other platforms I made are. The multi-site seems to be fine though im only using the normal cache right now and havnt tested aggressive,seems og doesnt work with aggressive so ill have to see what those side effects are and decide how to handle that, hopefully its not so bad I have to choose between the two.
It only happens the first
It only happens the first time I access the site. And only one specific site, I've not spotted the same issue on other sites. My client has accessed the site and seen the same problem. It seems to load the default site for parts of it. I get the EC2 instance DNS as the name of the site until I refresh. Refreshing seems to do the trick. I haven't had the time to test this out more throughly although I do agree it's unlikely that it's a pressflow specific issue.
Doug
@nullvariable | www.nullvariable.com