610Part VRunning ServersYou can use the netstatcommand to (Free web host)
610Part VRunning ServersYou can use the netstatcommand to view the list of programs (including Apache) with TCP ports in the LISTENstate: # netstat -nltpActive Internet connections (only servers) Proto Local Address Foreign Address State PID/Program nametcp 0.0.0.0:80 0.0.0.0:* LISTEN 2105/apacheThe output from netstat(which was shortened to fit here) indicates that aninstance of the apacheprocess with a process ID of 2105 is listening (as indicated bythe LISTENstate) for connections to any local IP address (indicated by 0.0.0.0) onport 80 (the standard HTTP port). If a different program is listening to port 80, it willbe shown there. You can use the killcommand to terminate the process, but if it issomething other than apache(or httpd), you should also find out why it is running. If you don t see any other processes listening on port 80, it could be that you haveaccidentally told Apache to listen on the same IP address and port combination inmore than one place. There are three configuration directives that can be used forthis: BindAddress, Port, and Listen: .BindAddressenables you to specify a single IP address to listen on, or youcan specify all IP addresses using the *wildcard. You should never have morethan one BindAddressstatement in your configuration file. .Portspecifies which TCP port to listen on but does not enable you to specifythe IP address. Port is generally not used more than once in the configuration. .Listenenables you to specify both an IP address and a port to bind to. TheIP address can be in the form of a wildcard, and you can have multiple Listenstatements in your configuration file. Generally, it is a good idea to use only one type of these directives to avoid confu- sion. Of the three, Listenis the most flexible, so it is probably the one you ll wantto use the most. A common error when using Listenis to specify a port on all IPaddresses (*:80) as well as that same port on a specific IP address (1.2.3.4:80), which will result in the error from make_sock. Configuration errors relating to SSL (discussed later in this chapter) will commonlyresult in Apache not starting properly. Make sure all key and certificate files existand that they are in the proper format (use opensslto examine them, as shownlater in this chapter). For other error messages, try doing a Web search to see if somebody else hasencountered the problem. In most cases, you can find a solution within the firstfewmatches.
If you are looking for cheap and quality webhost to host and run your website check Jboss Web Hosting services.