Why apache doesn't serve pages when it's running

grob115 · 02-24-2007, 11:35 PM

Hello,

Just wondering why my Apache wasn't serving pages when the system says "httpd (pid 7302) is running...". The following is a snippet of what I entered into the system:

[root@vps ~]# service httpd status
httpd (pid 7302) is running...
[root@vps ~]# service httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
[root@vps 2007.02]# service httpd status
httpd (pid 13328 13327 13325 12254 12253 12252 12251 12250 12249 12248 12247 12243) is running...

macemoneta · 02-25-2007, 12:03 AM

Did you remember to open the firewall port(s)?

grob115 · 02-25-2007, 07:37 AM

Please explain... how does it have to do with firewall ports...

macemoneta · 02-25-2007, 10:48 AM

A web server transfers data over network ports (by default, ports 80 and 443). In order for you to connect, the firewall must allow data to pass on those ports.

grob115 · 02-25-2007, 06:09 PM

I see. It should be opened and set properly. What I actually was saying is that Apache wasn't serving pages before I restarted it even though it says "httpd (pid 7302) is running..."

It's serving pages only when it says "httpd (pid 13328 13327 13325 12254 12253 12252 12251 12250 12249 12248 12247 12243) is running..." Why are there so many processes?

macemoneta · 02-25-2007, 06:26 PM

The number of servers is defined in your httpd.conf file. This allows Apache to service multiple concurrent requests, and to distribute workload over multiple CPUs (if available).

grob115 · 02-25-2007, 08:19 PM

Ah I see. So what does it mean when there's only one process ID running and it is not serving pages. What type of problems can cause this?

macemoneta · 02-25-2007, 08:32 PM

Check '/var/log/http/error.log' for messages.