Well, if you examine nf, and php.ini, and compare it to the standalone installs, you see they mean exactly what they're saying. When you visit their, all over, you see xampp was not designed for production. I repeated the process with php-5.5.15-Win32-VC11-x86, and again things were stable. I did the same thing with PHP, please understand, I was desperate for a fix. Then copied the entire "conf" directory back into the Apache folder.Īpache started right up and remained stable. I backed up the entire Apache "conf" directory, and overwrote the files with httpd-2.4.10-win32-VC11. I heard about httpd-2.4.10-win32-VC11 and php-5.5.15-Win32-VC11-x86 resolving some of the memory leaks so I did some testing on the localhost. mod_fastcgi was slow, to many executables sucking up memory and cpu. For low traffic sites, mod_fastcgi or mod_fcgid is an option, this post is for site with 400+ online users. I don't believe there is one fix, but I did manage to get the server stable with many fixes, and I'll share those. I've been battling this for 3 three years now. My problem has always been an unstable opcode cache (Parent: child process exited with status 255 - Restarting), and the other one (Parent: child process exited with status 3221225477 - Restarting). Test extensively on your localhost before going live. Try these suggestions at your own risk, and don't hold me or the xampp staff responsible if something goes wrong. I would like to share something with the Windows users who chose to use xampp in a production environment. This is my 2nd post on the site although I've been been an xampp user for 3 years now.
0 kommentar(er)
