The zoo!?

[ian_evil]

Alright. So the port deal got smashed, and everyone hates Bush. Good job, kids.
I didn't think there would ever be a stupid reason to hate Bush, but.. this is a really stupid reason to hate Bush.

To see everyone get so bent out of shape over a corporation from the United ARAB Emirates was embarrassing. "How is it OK to give up control of our ports

Comments

[geektron]

i dunno about OSX, but check the /etc/hosts file (if there is one)

from a command prompt, type 'hostname' and that will tell you what the machine thinks it's named.

and the apache conf should match what's in /etc/hosts (which contains what gets output by `hostname` )

it's not uncommon on a *nix-based system to forget to edit the config file that contains the hostname.

[flintultrasparc]

You can also try the IP address of http://127.0.0.1
If nothing still comes up, do a ps -ef | grep -i apache
and a ps -ef | grep -i httpd
if you've got nothing for either one, apache isn't even running
you might need to restart it
probably something like /etc/init.d/apache start (or restart)

[zigamorph]

Apache is a userland process. It's not at the "core" of anything.

First, Apache makes log files. By default, these are "access.log" and "error.log" (although the actual names are specified in the Apache config, which by default is in "httpd.conf" somewhere). I don't know anything about OS X, but typically Apache logs are in some directory such as "/usr/local/etc/httpd/logs" or "/var/apache/logs" or whatever. Look for anything unusual.

If the logs show that Apache is starting normally, then see if you can access it manually. The most basic way is "telnet 127.0.0.1 80" and seeing if that connects. If it does, try a browser to "http://127.0.0.1:80" and see what you get.

If connecting to raw IP addresses works but connecting to domain names does not, then your problem is localized to name resolution. Keep in mind that serious name resolution errors can even prevent Apache from starting up in the first place.