1.2.0 drivers crash when creating connection to a db

[jacqueswaller]

Using the Windows DLLs provided by PECL to use MongoDB with PHP and Apache. Windows 7 x64. I tried a variety of PHP versions (7.0.11, 7.0.9, 7.0.8 and 7.0.5), and a couple Apache versions (2.4.18 and the latest 2.4.23) all with same result.

The driver appears to be loaded correctly, as I can instantiate and interact with a variety of driver-related classes like MongoDB\BSON\UTCDateTime, but as soon as I try to create a connection like

$manager = new MongoDB\Driver\Manager("mongodb://localhost:27017");

My process crashes and I get ERR_CONNECTION_RESET. The apache error log will show something like:
[mpm_winnt:notice] [pid 11244:tid 524] AH00428: Parent: child process 10756 exited with status 255 -- Restarting.
All drivers up to and including 1.1.8 working fine with all of the above php/apache versions. Additionally, there are no issues with any of the 1.2.0 drivers when using PHP's built-in web server.

[jmikola]

Where is ERR_CONNECTION_RESET coming from? Is that an error in the browser requesting the PHP file?

Which version of the driver are you using (based on this list)? 1.2.0 stable has not been released yet.

According to this Stack Overflow answer, exit code 255 may be synonymous with a fatal error. The advice there suggests enabling error reporting within the PHP configuration and checking for anything that may be suppressing an error or exception. Are you certain that the very same PHP configuration is being used by Apache and the built-in web-server (I presume that would be the CLI configuration).

[jacqueswaller]

Right, yeah ERR_CONNECTION_RESET is what displays in Firefox/Chrome web browser. The message body as returned from Apache is

Failure when receiving data from the peer

I'll search around a bit to see what's up with that, but guessing that's what happens when the PHP process terminates.

I tried out 1.2.0alpha2 and 1.2.0alpha3 (there's no windows dll on pecl for alpha1) both with same result.

I only have the one config with mongo extensions loaded, but yes the same PHP configuration is being used by Apache and the built-in web-server (verified by a simple print(php_ini_loaded_file());). I guess it's also worth mentioning that a simple php myTestFile.php command also works fine (and uses the same .ini), so it's specifically some weird interaction with these new drivers+apache.

I'll see what else I can troubleshoot.

[jacqueswaller]

I tried using an absolutely stock Apache install (zero changes to conf other than to use php) and still occurs, so I don't think it's anything "weird" we're doing with Apache.

Not sure how to get more debug info out of this (everything already set to max, and php isn't generating any errors of any kind). Guess I'll check back when the stable release is ready.

[jmikola]

1.2.0 has been released if you'd like to test that. If the issue persists, I can try to reproduce this on a Windows 7 VM next week. Feel free to link me to specific binaries to download for Apache, PHP, MongoDB, and anything else that might be useful for attempting reproduction. An example PHP script to server via Apache would help as well, unless you'd like me to create something that opens a local connection and issues a basic command like ping or isMaster.

[jacqueswaller]

Same problem, unfortunately.

The Apache binaries we use are at https://www.apachelounge.com/download/ (though I did try a few other providers of binaries like apache haus). Version probably doesn't matter too much (I tried a random selection of them) though what I tested the stable dll with is 2.4.18

Windows binaries for PHP are at http://windows.php.net/download#php-7.0 (Version doesn't seem to matter much; I had tried a bunch of different vers for the alpha, for stable I tried 7.0.11 and 7.0.13).

Windows binaries for mongodb can be found at https://www.mongodb.org/dl/win32/x86_64-2008plus-ssl?_ga=1.89388379.1977526765.1452104591 . I've been testing with Mongodb 3.2.0, and I don't think I've tried any other versions so maybe that matters for something. But I figured it was an issue with apache since with the php built-in web server everything is fine.

As far as test script, it isn't exactly complicated just

<?php  
    try
    {
        $manager = new MongoDB\Driver\Manager("mongodb://localhost:27017");
    }
    catch(MongoDB\Driver\Exception\Exception $e)
    {
        print("Handled exception");
    }
    
    print("success!");
    exit;
?>

Where the fatal line is when creating the Manager.

In the mean time I guess I'll try something other than 3.2.0 and see if anything changes.

[jacqueswaller]

Yeah, ditto for 3.0.7 (what we legit use in production) as well as 3.4.0

[globules-io]

Exact same issue here with Apache 2.4.23 x64 + PHP7.1 x64 TS + driver 1.2.0 + Mongo 3.4.0 = ERR_CONNECTION_RESET

[globules-io]

Same same with driver 1.2.1

[lindelius]

The underlying reason for these crashes is most likely the exact same as for my crashes (described in #476).

[globules-io]

just FYI I tested with php_mongodb-1.1.10-7.1-ts-vc14-x64.zip and it works.

[jmikola]

@jacqueswaller: Please see my comment in #476 (comment). I believe I've narrowed this down to our client persistence, which was introduced in 1.2.0alpha2 and would explain why the issue first appeared in that release.

[jacqueswaller]

After setting up a x86 environment, I can confirm that it no longer crashes when creating a MongoDB\Driver\Manager object