Checking for new configurations / going to migrate page results in WSOD (though server code is 200) [#1518090]

Hiya,

I'm going to provide a bit of history on what I did:

On local server, create configuration.
Pull down db from live to local.
Install configuration and load datastore to active store. Successful.
Push codebase to staging server and attempt to repeat.
- Go to 'check for new configurations'. Get wsod.
- Try to track items. Starts tracking.
- Go to 'check for new configurations'. Get wsod.
- Go to 'admin/config/system/configuration/migrate'. Get wsod.

I was checking through the error logs trying to see what could be the issue but no such luck. In fact, when I look at the access logs, the pages are actually returning a code 200 (which seems to imply something else is going on but I am unsure). I had some luck when I changed the include $file lines to get the stream-uri version of the file. But I also see config:// is registered correctly so it should be working just fine (and it passes the is_file() check). The two environments are set up differently (locally, I am running php 5.3.6 while the server runs 5.3.10. I was running apache locally while running nginx on the server but I later switched it to apache and ended up with the same errors) but I am at a loss on what could be going on. Any help on this would be greatly appreciated.

Comment	File	Size	Author
#8	configuration-wsod-1518090-8.patch	6.89 KB	lucascaro
#5	wsod-1518090-5.patch	6.92 KB	misc
#1	config-stream.patch	6.45 KB	btmash

Comments

Comment #1

btmash commented 6 April 2012 at 19:57

Status:

Active

» Needs review

Status	File	Size
new	config-stream.patch	6.45 KB

I can't believe this actually worked - there is definitely something going on with the include_once and config:// between 5.3.6 and 5.3.10. As a workaround, I am wrapping the files for include in drupal_realpath. Attaching a patch which is, unfortunately, in svn format. But should still be able to apply it.

Comment #2

btmash commented 8 April 2012 at 09:58

As a note, I've also filed an issue at https://bugs.php.net/bug.php?id=61665 as I think that may ultimately be the culprit.

Comment #3

jerrac commented 12 April 2012 at 23:46

Um, I can't get that patch to apply.

On the command line, in the configuration module directory, I run:

patch < config-stream.patch

And get nothing. On my dev server.

Do the same on my prod server (yes, I know bad idea) I get this:

sites/all/modules/contrib/configuration$ patch < config-stream.patch 
can't find file to patch at input line 5
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|Index: includes/configuration.image.inc
|===================================================================
|--- includes/configuration.image.inc	(revision 1871)
|+++ includes/configuration.image.inc	(working copy)
--------------------------
File to patch:

What am I missing?

Comment #4

btmash commented 13 April 2012 at 20:54

Hmm, I'm not sure why it won't see the diff. Lets see if I create a git diff instead. I've updated more stuff since there were a few other weird issues that came up.