The network is working OK and I can ping my Fedora box but there is no port 80 shown as open.

Upon boot the Apache server complains that it can not bind to the IP address. I has a lot of other text but it is only up for 2 seconds and I haven't been able to read it. I think I need to read that message.

Q: Is there a way to stop the boot sequence on Fedora 9 so I can read the Apache boot message? I've looked all over the hard drive for a copy of the boot log but I haven't found it.



eth0 Link encap:Ethernet HWaddr 00:48:54:8F:16:B8
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::248:54ff:fe8f:16b8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1057 errors:0 dropped:0 overruns:0 frame:0
TX packets:1132 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:845247 (825.4 KiB) TX bytes:219758 (214.6 KiB)
Interrupt:17 Base address:0xe000

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
default dslrouter 0.0.0.0 UG 0 0 0 eth0


Q: The gateway is at 192.168.1.1 so why does the route map show 192.168.1.0 ? What is 192.168.1.0 anyway?

Q: Does the IP address of the Apache Server need to be the same or different than the IP address of the Computer. I've tried both ways and Apache can't bind to whatever IP address I ask it to use.

A couple more pieces of information. Although the network is working (I can browse and print over the network) there are a few anomalies ever since I set a fixed IP address.
1) At the top of the Gnome desktop there is a small network icon. Putting a mouse on that reports that there is no network connection.
2) When I start Mozilla Firefox it always comes up in the Work Offline setting. Unchecking the work offline box allows for perfect browsing.
3) The System->Admin->Add/Remove program can search the web for catalogues successfully but if you ask it to add one it reports back that there is no network connection.

ok, 1 question per thread in future... much less confusing.


1 - look in /var/log/httpd/error_log or /var/log/apache/error_log (or very similar)

2 - that's your local network, your gateway is clearly listed as "dslrouter" from your local dns server, probably running on the router.

3 - at your level, yes. but normally you wouldn't bother specifiying an IP address, you'd just bind to * by default, which would use all locally assigned addresses. you don't explicitly bind to an ip not already in use by the box, that makes no sense.

Quote: acid_kewpie;3394911]ok, 1 question per thread in future... much less confusing.

From Bob @ ScottHill in blue

1 - look in /var/log/httpd/error_log (Empty Directory) or /var/log/apache/error_log (or very similar) No directory named similarly. I've spent quite a bit of time looking for a boot log file in the /etc/ and /var/ directories and their subs and I haven't found it yet

2 - that's your local network, your gateway is clearly listed as "dslrouter" from your local dns server, probably running on the router. Yes the Westell DSL Modem is the gateway and the router. It's IP address is 192.168.1.1

3 - at your level, yes. but normally you wouldn't bother specifiying an IP address, you'd just bind to * by default, which would use all locally assigned addresses. you don't explicitly bind to an ip not already in use by the box, that makes no sense. I'm sorry I got lost here. So I take it that the Apache server should bind to the same IP address as the box. No matter I've tried it both ways with no difference. I have to set up port forwarding in the router so the Apache Server has to have a static IP Address for the router to forward to --- as far as I know.

When you did your install did you turn on selinux. If so then you might want to check and see if it is blocking port 80 access. Also try a
or just drop the pipe and check to see if it is listening on 80. to view the the output of the kernel at boot up just type in

I would do netstat -lanp | grep :80 to see what process, if any, is bound to port 80.....


apache2ctl start should manually start the apache web server if it's not running.. do that in a shell and you should be able to see any error messages. you can also use apache2ctl to verify your config is good, or what the current server status is..


iprtables -L - is the local firewall on the Fedora box, blocking the web server from being accessed from other machines ?