can't access local server (slackware 12.2)

vonbiber · 10-23-2009, 07:17 AM

on my slackware 12.2 box I can't access local server.
I was able to in the past and I haven't modified the config
files lately (http.conf, ...).
The exit code of

Code:

/etc/rc.d/rc.httpd start

is 0.
The file

Code:

/var/log/httpd/error_log

doesn't report any errors.
And yet when I try to go to any of these addresses

Code:

http://localhost/
http://127.0.0.1/
http://127.0.0.1:80/

in my browser, it takes for ever to load and eventually I'd get an error page:
...
Could not connect to remote server
...

Have I missed something on my checklist?

stormtracknole · 10-23-2009, 07:22 AM

Quote:

Originally Posted by vonbiber

on my slackware 12.2 box I can't access local server.
I was able to in the past and I haven't modified the config
files lately (http.conf, ...).
The exit code of

Code:

/etc/rc.d/rc.httpd start

is 0.
The file

Code:

/var/log/httpd/error_log

doesn't report any errors.
And yet when I try to go to any of these addresses

Code:

http://localhost/
http://127.0.0.1/
http://127.0.0.1:80/

in my browser, it takes for ever to load and eventually I'd get an error page:
...
Could not connect to remote server
...

Have I missed something on my checklist?

What do you get when you run this command:

Code:

ps -ef | grep httpd

vonbiber · 10-23-2009, 08:12 AM

Code:

# ps -ef | grep httpd
root      2597     1  0 15:12 ?        00:00:00 /usr/sbin/httpd -k start
apache    2598  2597  0 15:12 ?        00:00:00 /usr/sbin/httpd -k start
apache    2600  2597  0 15:12 ?        00:00:00 /usr/sbin/httpd -k start
apache    2601  2597  0 15:12 ?        00:00:00 /usr/sbin/httpd -k start
apache    2602  2597  0 15:12 ?        00:00:00 /usr/sbin/httpd -k start
apache    2603  2597  0 15:12 ?        00:00:00 /usr/sbin/httpd -k start
root      2605  2590  0 15:12 pts/2    00:00:00 grep httpd

stormtracknole · 10-23-2009, 09:13 AM

Take a look at /var/www/htdocs and make sure you still have an index.html file. Sometimes, it gets replaced during upgrades.

vonbiber · 10-23-2009, 09:30 AM

Quote:

Originally Posted by stormtracknole

Take a look at /var/www/htdocs and make sure you still have an index.html file. Sometimes, it gets replaced during upgrades.

no, it's still there.
besides if it were missing I'd get the contents of the directory
but no error message
Before that I tried some php pages that I wrote and I know
that php is working because

Code:

php -i

displayed phpinfo contents

manwichmakesameal · 10-23-2009, 09:44 AM

What kind of firewall rules do you have in place?

vonbiber · 10-23-2009, 10:37 AM

Quote:

Originally Posted by manwichmakesameal

What kind of firewall rules do you have in place?

I never touched these. I kept the default settings that came with
the slackware installation.
So I guess there are none.

mRgOBLIN · 10-23-2009, 06:38 PM

Code:

apachectl -t

Will show any errors in your config.

Code:

netstat -ltp| fgrep http

Will show you if you have a http server listening on a port.

Did you specify a "Listen" directive in your httpd.conf?

The Default is "Listen 80"

If you bind the httpd server to a specific ip address then it won't listen on localhost unless told to do so.

vonbiber · 10-24-2009, 05:36 AM

Quote:

Originally Posted by mRgOBLIN

Code:

apachectl -t

Will show any errors in your config.

I already ran that command. There are no syntax errors in the config.

Quote:

Code:

netstat -ltp| fgrep http

Will show you if you have a http server listening on a port.

I'll try that later. Right now httpd is not running.

Quote:

Did you specify a "Listen" directive in your httpd.conf?
The Default is "Listen 80"
If you bind the httpd server to a specific ip address then it won't listen on localhost unless told to do so.

I didn't change the original settings and in my browser
even

Code:

http://127.0.0.1:80/

didn't work

And, by the way, I don't have that issue with slax
(with xampp).

mRgOBLIN · 10-24-2009, 07:56 AM

Not running through a proxy of any kind?

vonbiber · 10-24-2009, 08:12 AM

Quote:

Originally Posted by mRgOBLIN

Not running through a proxy of any kind?

nope

stormtracknole · 10-24-2009, 09:13 AM

Just for the heck of it, type this as root:

Code:

iptables -nvL

and post the results.

Also, on your httpd.conf file, look for this section (ServerName www.example.com:80) to see what it says.

Last, but not least, take a look at /etc/hosts.allow and /etc/hosts.deny to make sure that nothing there is being block.

vonbiber · 10-25-2009, 06:15 AM

Quote:

Originally Posted by stormtracknole

Just for the heck of it, type this as root:

Code:

iptables -nvL

and post the results.

Code:

# iptables -nvL
FATAL: Module ip_tables not found.
iptables v1.4.2: can't initialize iptables table `filter': iptables who
? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

Quote:

Also, on your httpd.conf file, look for this section (ServerName www.example.com:80) to see what it says.

Here's what I have

Code:

#
#ServerName www.example.com:80
ServerName 127.0.0.1:80
#

Quote:

Last, but not least, take a look at /etc/hosts.allow and /etc/hosts.deny to make sure that nothing there is being block.

There's nothing in there, just comments

@mRgOBLIN

Code:

# netstat -ltp | fgrep http
tcp    0  0 *:http  *:*   LISTEN      2221/httpd

stormtracknole · 10-25-2009, 01:00 PM

The iptables command needs to be done as root. I doubt this is the problem though. Go ahead and comment out the ServerName section. I don't think it is necessary to manually put in 127.0.0.1 in there. Once you make the change, go ahead and restart the service:

Code:

/etc/rc.d/rc.httpd restart

vonbiber · 10-27-2009, 05:04 AM

Thanks for the suggestion about /etc/httpd/httpd.conf
I commented out the ServerName line and restarted apache
and that did the trick
However every time the daemon would start I'd get this message

Code:

httpd: Could not reliably determine the server's fully qualified  domain name, using 127.0.0.1 for ServerName

So I thought I would put this line instead

Code:

ServerName localhost

It worked and this time I didn't get the annoying message.

Again, thanks a lot to everybody who tried to help

Quote:

Originally Posted by stormtracknole

The iptables command needs to be done as root.

I ran all the commands as root