checking httpd connections

unSpawn · 07-11-2003, 09:35 AM

...grepping the "netstat" output you posted above: "grep tmp/netstat -ce "^tcp.*ESTABLISHED.*httpd" I get 16 connections, can't see no problem with that. Similar way would be to use "lsof", as root: "lsof -i | grep -ce ESTABLISHED".

jiena · 07-15-2003, 09:52 PM

I've installed apache on linux 7.3 but when i tried to restart the service an error
occured.

Below is the error:

httpd failed to start. The error was: Starting httpd: Error:
Apache has not been designed to serve pages while running as root. There
are known
race conditions that will allow any local user to read any file on the
system. If you desire to serve pages
as root then add -DBIG_SECURITY_HOLE to the EXTRA_CFLAGS line in your
src/Configuration file and rebuild the
server. It is strongly suggested that you instead modify the User directive
in your httpd.conf file to list
a non root user. FAILED.

i have no idea what was the error is about. Pls give me suggestion on how to
solve this problem. FYI, i'm new to linux and apache.

thanks in advance.

JZL240I-U · 07-16-2003, 04:03 AM

Quote:

Originally posted by unSpawn
What does "netstat -anp -A inet| grep -e "^tcp.*ESTABLISHED.*httpsd" say?
...
...grepping the "netstat" output you posted above: "grep tmp/netstat -ce "^tcp.*ESTABLISHED.*httpd" I get 16 connections, can't see no problem with that.

@unSpawn:
You had a typo in your first post: ...*http_s_d, that's why ...

JZL240I-U · 07-16-2003, 04:09 AM

Quote:

Originally posted by jiena
... httpd failed to start. The error was: Starting httpd: Error:
Apache has not been designed to serve pages while running as root. There
are known
race conditions that will allow any local user to read any file on the
system. If you desire to serve pages
as root then add -DBIG_SECURITY_HOLE to the EXTRA_CFLAGS line in your
src/Configuration file and rebuild the
server. It is strongly suggested that you instead modify the User directive
in your httpd.conf file to list
a non root user. FAILED.
...

It would have been better to start a new thread for your problem. Who shall find it here?

Anyway: Read the error message you posted yourself: It's all there

. So, login as normal user, not root (administrator). That should do the trick.

MasterC · 07-16-2003, 04:24 AM

Quote:

Originally posted by JZL240I-U
@unSpawn:
You had a typo in your first post: ...*http_s_d, that's why ...

Yeah, actually he didn't. He was rather referring to an SSL secured apache setup, not really a typo but a look-over. He recognized it in one of his above posts

Cool

JZL240I-U · 07-16-2003, 04:45 AM

Quote:

Originally posted by MasterC
... referring to an SSL secured apache setup.

Now why would that be so? I mean, what's the reason that a secured apache has a different daemon? Couldn't they just do it in modular software and add a security layer between daemon and apache?

Quote:

Originally posted by MasterC
He recognized it in one of his above posts

That's right, so he did, sorry for stating the obvious, but I didn't reread the whole thread.