Navigate
Home
ArticleWiki
Forum
Journal
Search
Newsletter
Links
Tech News
expertsrt.com
Welcome Guest.
Username:

Password:

Remember me

Apache not working
Welcome, Guest. Please login or register.
December 02, 2008, 12:20:14 PM
11304 Posts in 1248 Topics by 498 Members
Latest Member: katCheeme
Experts Round Table Network  |  Webservers  |  Apache  |  Apache not working « previous next »
Pages: [1]
Author Topic: Apache not working  (Read 1380 times)
ScottInTexas

Offline Offline

Posts: 9


« on: July 21, 2007, 06:45:34 AM »

OK, I've read for hours now and see that geting Apache to work can be very frustrating.  So I know this is not a new topic.  However, none of the answers posted have helped.

Apache 2.0.59 is installed and running as a service, the service is started and the apache monitor has confirmed this.  My httpd.conf file has Listen:80 and ServerName localhost:80.  I am following the download and install directions located at http://www.expertsrt.com/tutorials/Matt/install-apache.html.  As he instructed I tested my installation with the basic http://localhost.  Nothing happened.  Explorer telss me it is connecting (on the tab), at the bottom of the window it tells me it is waiting on "Localhost"  that's it.  Nothing else is happening.  I had a working system some weeks ago but I had to uninstall that so I could upgrade to PHP 5.  None of the packaged programs have worked so I think there is something else going on that is preventing apache from serving a page.  And yes, I did suspend my firewall.

Windows XP, SP2
Toshiba Satellite
IE 7.0

Thanks for your help.
Logged

Thanks,
Scott
The Answer is 42
GrandSchtroumpf
Mentor

Offline Offline

Posts: 410



« Reply #1 on: July 21, 2007, 08:10:04 AM »

Apache 2 and PHP works better on *nix platforms.
Ubuntu is extremely easy to install (I read a 2-year old did it) and works well on laptops (power management included).
To install Apache 2 and PHP in Ubuntu, you just need to set 2 small flags in the software manager and click the "OK" button.
For obvious reasons, if your production site will run on linux (like most Apache/PHP sites do), it's better to use linux as development machine.

That said, you can try the following in Windoze:

1. Test DNS and TCP/IP connection (in a command prompt):
> ping localhost
If you get a response, then it's fine.

2. Test telnet (in a command prompt):
> telnet localhost 80
If you get a telnet prompt, then it's fine.

3. Use a "real" browser to access your site (firefox, opera, safari,...)
IE7 is full of "security features" that might block your site.

Good luck.
Logged
ScottInTexas

Offline Offline

Posts: 9


« Reply #2 on: July 21, 2007, 09:32:29 AM »

Thanks for your response.  I had this working at one time having used PHPDev5 from Firepages.  The problem was that it used PHP4 and I wanted features that weren't present in that version.  Since then I have had to fight this regardless of the number of times I have seen posts where people say "Installed and ran perfectly".

I did ping local host and got a response.  When I tried telnet I got a blank window.  It's still hanging there.  I guess I'll download firefox and see what happens.

Logged

Thanks,
Scott
The Answer is 42
ScottInTexas

Offline Offline

Posts: 9


« Reply #3 on: July 21, 2007, 09:47:15 AM »

OK.  I also tried Mozilla Firefox with the exact same results.  It just sits there trying to connect.
Logged

Thanks,
Scott
The Answer is 42
GrandSchtroumpf
Mentor

Offline Offline

Posts: 410



« Reply #4 on: July 21, 2007, 01:27:15 PM »

> When I tried telnet I got a blank window.

I'm not sure how telnet is supposed to work on windows...
Could you type things in that telnet window?
If so, try to type the following inside the telnet window:
Code:
GET /
And see if you get some HTML code back.
If that does not work, it means your apache configuration is wrong and there is no need to test different browsers.

There was another thread on this forum where someone had used the "default port" at installation which was "8080".
Although you said you specified port 80 in "httpd.conf", try http://localhost:8080/ in your browser, just in case.
You can also try telnet on port 8080 instead of port 80.
My Apache 2 installations on Linux do not use "httpd.conf"... Windows configuration seems to be different.

That's all i can do.  You'll need to wait for comments from Windows users for better guidance.
Logged
ScottInTexas

Offline Offline

Posts: 9


« Reply #5 on: July 21, 2007, 01:41:25 PM »

Thanks very much for your reply.  No I can't type in the window.  I can see the cursor move, but alas, nothing happens.  There has to be something specific to my machine!  The installations work everywhere else.  Unfortunately, since the 80386 went by the wayside I have lost touch with the system.  And so much of the system is buried deep in hidden files.  And Windows "Help" just plain sucks.  Sorry for venting.  I was getting frustrated.

Somewhere out there is an answer.  When I find it, or it is given to me, I'm going to write a paper and post it everywhere.
Logged

Thanks,
Scott
The Answer is 42
ScottInTexas

Offline Offline

Posts: 9


« Reply #6 on: July 21, 2007, 01:57:41 PM »

Just thought I'd add this bit of information for whoever may need it.  This comes from the error log.  I can see each time I started the Apache server and each time I shut it down.

[Sat Jul 21 07:22:09 2007] [notice] Apache/2.0.59 (Win32) configured -- resuming normal operations
[Sat Jul 21 07:22:09 2007] [notice] Server built: Jul 27 2006 15:55:03
[Sat Jul 21 07:22:09 2007] [notice] Parent: Created child process 3608
[Sat Jul 21 07:22:09 2007] [notice] Child 3608: Child process is running
[Sat Jul 21 07:22:09 2007] [notice] Child 3608: Acquired the start mutex.
[Sat Jul 21 07:22:09 2007] [notice] Child 3608: Starting 250 worker threads.
[Sat Jul 21 14:52:19 2007] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Sat Jul 21 14:52:19 2007] [notice] Child 3608: Exit event signaled. Child process is ending.
[Sat Jul 21 14:52:20 2007] [notice] Child 3608: Released the start mutex
[Sat Jul 21 14:52:21 2007] [notice] Child 3608: Waiting for 250 worker threads to exit.
[Sat Jul 21 14:52:21 2007] [notice] Child 3608: All worker threads have exited.
[Sat Jul 21 14:52:21 2007] [notice] Child 3608: Child process is exiting
[Sat Jul 21 14:52:22 2007] [notice] Parent: Child process exited successfully.

And here is the Install log.  NOTE:  I have since changed the Listen 8080 to listen 80.  I have even tried Listen 81.


Installing Apache HTTP 2.0 server with
 DomainName =  localhost
 ServerName =  localhost
 ServerAdmin = me@mydomain.com
 ServerPort =  8080
 ServerRoot =  C:/Webserver/Apache2
Rewrote C:/Webserver/Apache2/conf/httpd-win.conf
 to C:/Webserver/Apache2/conf/httpd.default.conf
Successfully removed C:\Webserver\Apache2\conf\httpd-win.conf
Duplicated C:/Webserver/Apache2/conf/httpd.default.conf
 to C:/Webserver/Apache2/conf/httpd.conf
Duplicated C:/Webserver/Apache2/conf/ssl.default.conf
 to C:/Webserver/Apache2/conf/ssl.conf
Duplicated C:/Webserver/Apache2/conf/magic.default
 to C:/Webserver/Apache2/conf/magic
Duplicated C:/Webserver/Apache2/conf/mime.types.default
 to C:/Webserver/Apache2/conf/mime.types
Successfully removed C:\Webserver\Apache2\conf\InstallConf.awk
« Last Edit: July 21, 2007, 02:01:59 PM by ScottInTexas » Logged

Thanks,
Scott
The Answer is 42
ScottInTexas

Offline Offline

Posts: 9


« Reply #7 on: July 22, 2007, 05:56:20 AM »

Finaly!  I got a response from the server. 

Firefox can't establish a connection to the server at localhost.

I changed the port back to 81 and this is the error I got.
Logged

Thanks,
Scott
The Answer is 42
VGR
Mentor

Offline Offline

Posts: 682



WWW
« Reply #8 on: July 22, 2007, 12:50:11 PM »

your httpd.conf configuration seems ok, apache 2 and PHP5 work like a charm on Zindoze and do install in a handful of seconds.

I suppose (assume) that you tried this URI : http://localhost
so :

1) does http://127.0.0.1/
produce the same results as http://localhost
?

2) have you tried http://localhost/
?
Logged

techie overlord, answers all kind of questions on http://www.europeanexperts.org
ScottInTexas

Offline Offline

Posts: 9


« Reply #9 on: July 22, 2007, 02:56:47 PM »

Thanks for your response.  Yes I have tried all of your suggested attempts.  They all produce the same result. If I change the Listen directive to 81 the page attempts to load forever.  No response of any kind.  I have checked firewalls to make sure nothing was being blocked.  It amazes me how many papers there are on the internet on how to install Apache and no-one seems to have any problem running it.  They all say the same thing.  Download the installer, run it and voila! you're server is up and running.
Logged

Thanks,
Scott
The Answer is 42
ScottInTexas

Offline Offline

Posts: 9


« Reply #10 on: July 23, 2007, 01:43:16 PM »

Well, I let my frustration get the better of me.  I uninstalled and reinstalled apache 2.0.59.  Same result as before.  So I reverted back to phpdev5Beta.  I installed and ran it.  I have apache running, it serves up pages as required and PHP is working.  So I just have to program my web pages without some of the features offered by PHP 5.  At least I can work.

Thanks Firepages for having a working install.  BTW I tried several install packages such as XAMP.  None of them worked either.  To all of you who would say "Just install and away you go", forget it.  It may be easy on your system with your unique set up.  But apparently there are issues that must be addressed.  I will continue to search for the answer and I will post it here if I ever get one.
Logged

Thanks,
Scott
The Answer is 42
VGR
Mentor

Offline Offline

Posts: 682



WWW
« Reply #11 on: July 25, 2007, 07:04:23 AM »

in fact, the problem could very well rely on your useage of "packages" like phpdev, php4all, XAMPP, PHPserver and the like (see http://en.wikipedia.org/wiki/List_of_AMP_Packages )

All those packages have inherent limitations and sometimes even defects.

I wrote installing is a piece of cake... when you install manually the three parts required !
probably mysql first
then apache
then php
http.conf editing
and off you go.

my.ini/my.cnf and php.ini tuning can take place as soon as http://localhost/ and http://localhost/phpinfo.php yields the proper result display. (of course, phpinfo.php contains <?php phpinfo(); ?> )
Logged

techie overlord, answers all kind of questions on http://www.europeanexperts.org
Pages: [1]
« previous next »
    Jump to: