Install fails for the 2.1.0-rc4 standard

I’ve stated about this on the other thread, but I want to mention that the 2.1.0-rc4 advanced installation worked well.

This is the apache error logs from the standard installation:

[Tue May 03 23:51:00 2011] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Tue May 03 23:51:04 2011] [notice] Apache/2.0.63 (Win32) PHP/5.2.14 configured -- resuming normal operations
[Tue May 03 23:51:04 2011] [notice] Server built: Jan 17 2008 22:58:29
[Tue May 03 23:51:04 2011] [notice] Parent: Created child process 3756
[Tue May 03 23:51:05 2011] [notice] Child 3756: Child process is running
[Tue May 03 23:51:05 2011] [notice] Child 3756: Acquired the start mutex.
[Tue May 03 23:51:05 2011] [notice] Child 3756: Starting 250 worker threads.
[Tue May 03 23:51:11 2011] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Tue May 03 23:51:11 2011] [notice] Apache/2.0.63 (Win32) PHP/5.2.14 configured -- resuming normal operations
[Tue May 03 23:51:11 2011] [notice] Server built: Jan 17 2008 22:58:29
[Tue May 03 23:51:11 2011] [notice] Parent: Created child process 5348
[Tue May 03 23:51:12 2011] [notice] Child 5348: Child process is running
[Tue May 03 23:51:12 2011] [notice] Child 5348: Acquired the start mutex.
[Tue May 03 23:51:12 2011] [notice] Child 5348: Starting 250 worker threads.

My systems are like on my signature.

I’ve experienced this over the last couple of days as well goldsky, at least it looks like it’s the same issue.
Turns out that this bug
http://bugs.modx.com/issues/4572
is triggering this bug
http://bugs.modx.com/issues/4567
in the installer, on Windows platforms.
Fixes will be in git shortly.

kool.
thx, mike.

Tried like a dozen couple of fixes that I found and that I could come up with and yet no cigar.

ReSpawN, as far as I understand the problem, these are the commits that should make it go away.

https://github.com/modxcms/revolution/commit/38bb1fb81de08b30418cadfdc612b2aace8d764a
https://github.com/modxcms/revolution/commit/a4e8ba35374fb9cbedabf2a223707a8e93821dd1

If those don’t do it, then I’m not understanding the problem you’re having. Is it exactly as Oleg describes here?
http://modxcms.com/forums/index.php/topic,63983.msg361980.html#msg361980

One commit fixes the names of install error log files, so they actually get created on Windows, and the other commit gets rid of a recursion that was happening if a log file couldn’t be written.

If there’s another similar problem that we haven’t uncovered yet, I’d love to nail it asap. Thx.

Yes, it’s exactly as Oleg describes it. I also replied in that topic. I’m gonna get a cup of coffee and then I’ll try to fix it! I’ll let you know ASAP. Thanks in advance, even if it doesn’t work. ;-)

Give this man a big applause! netProphET to the rescue!

By replacing the following line in /setup/includes/modinstall.class.php (line 253) I fixed the problem:
This fix can be found on netProphET’s Github: https://github.com/modxcms/revolution/commit/38bb1fb81de08b30418cadfdc612b2aace8d764a

Thanks a bunch bro.

Awesome.. glad I don’t have another bizarre bug like that to hunt down

Heh indeed! I always find it quite strange that such a small little bug can break an entire CMF/CMS/Installer.