hello... on my web server after maybe a day, the URL wont resolve.... but the IP address works great.
if i run
ps aux | grep apache2 | wc -l
it showed 150 + instances of apache running... the only thing i knew to do was restart apache, which fixed the problem and started apache back at around 14 instances.
if i refresh the homepage and then run
ps aux | grep apache2 | wc -l
the number creeps up by one.
I am totally clueless on what to do to fix this...
Version Information:
Forum version: SMF 2.0.8 (more detailed)
Current SMF version: SMF 2.0.8
GD version: 2.0
MySQL version: 5.5.37-0ubuntu0.12.04.1
Memcached: ???
PHP: 5.3.10-1ubuntu3
Server version: Apache/2.2.22 (Ubuntu)
Are they active processes, sleeping processes or zombie processes?
How is Apache configured? It sounds like you're using prefork, in which case it's doing *precisely* what it's supposed to be doing: spawning child processes to handle requests when made up to its limit (default 255)
sorry im obviously a novice at this.
any guides to get you the info your looking for?
Not really... I'm just fairly sure that it's doing exactly what it's supposed to be doing...
Just for information, S&L...
http://httpd.apache.org/docs/2.2/mod/prefork.html
Quote
hello... on my web server after maybe a day, the URL wont resolve.... but the IP address works great.
What does that have to do with Apache?
Apache doesn't resolve DNS, you should look at your nameserver software (like bind) if your URL won't resolve.
That the site is still accessible by IP means that at least Apache is doing its job just fine.