Why does apache crash

The apache server will crash in the last 2 seconds of the installation. I have tested in 6 machines already and i am really fed up with it. Same procedure same clean windows 10 64 bit installation and same results. And not i do not have a second instance of the application running nor a second installation of xampp nor apache nor anything else that i have searched and found about in the forums.

I have to add that i tested all of the versions of xampp just to avoid the message that comes with the 7 version of php which refers to some kind of instability issues with the bitnami modules and xampp. There is a problem with the manager detecting the status of Apache just after a module installation. Your Apache is correctly configured, up and running, but the manager shows it as not running. Your Certificate doesn't match the servername you configured.

That's not a php or a mysql question, it's an Apache one. You should have to look at your httpd. It's so stupid how the new versions are more buggy than the old versions and that the people developing the thing can't even debug using their own debug messages.

I think I tried that old version before and it didn't work so it must have been something to do with the VC files. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Apache in Xampp keeps crashing on start Ask Question. Asked 4 years ago. Active 8 months ago. And when server down, Apache is off.

I have to ssh and restart Apache again. The Ubuntu version is still From the symptoms you are describing, my guess is that this may be due to either your Linode running out of memory, or an Apache configuration issue. Monitor your memory usage. If your server is running out of memory, it may shut down processes unexpectedly.

Something like free -m is a good place to start, though the linked guide above has a few more helpful commands. AtariAge Member. Mar 14, 9 2 I've setup a new server recently and moved a fairly busy forum to it 4. I'm running Invision 4. Database MySQL 5. No other sites are running on the web server, and the database server only supports this one site. Upon initially doing this, Apache would go down pretty quickly, apparently due to exhausting MaxRequestWorkers.

This seemed to resolve the problem, but after about 12 hours Apache stopped responding to requests again, and I didn't see any active PHP-FPM processes. Restarting apache didn't seem to help, and it wasn't until I switched back to PHP-CGI that the server started responding to requests again. I could try increasing MaxClients and MaxRequestWorkers further, but I don't know if that would help--seems like I might just be putting a temporary band-aid on a deeper issue.

I looked through the logs the last time Apache went down or at least hung and saw tons of messages like this: Code:. I not been aware aware of any issues myself, but I have small sites. Most of the tutorials online are unfortunately based on using it with Nginx, probably for a good reason, if only to save one's sanity.

PHP 7. Redbot is handy for checking http caching headers. Check you have the Redis PHP extension installed. Their Argo mode is also an effective option.