problems with apache 1.3 on windows

screw3d

Diamond Member
Nov 6, 2001
6,906
1
76
I had Apache 1.3.31 running fine on my Windows XP SP2 system.. the logs indicate that the last time it was running fine is on dec 3. I'm only running apache for local PHP app development.

Now, when I tried localhost or 127.0.0.1, the browser doesn't show anything and just returns a "documents contains no data". I nuked the entire installation and put in Apache 1.3.33 and still nothing.

localhost responds to ping though, i've replaced my httpd.conf with the default, still no dice :|

i've googled to death and still can't a solution. what is going on here?

edit: and oh, there is NOTHING on the access and error log now :|
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
netstat -an
Look for the port you set apache up on to be in a LISTENING state, preferably on the IP address you used. Double check the port you think you're using too.
 

screw3d

Diamond Member
Nov 6, 2001
6,906
1
76
This is what I got:

TCP 127.0.0.1:80 127.0.0.1:1839 CLOSE_WAIT
TCP 127.0.0.1:80 127.0.0.1:1842 CLOSE_WAIT

What is the problem?

I have tried restarting the service but no go :(
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Originally posted by: screw3d
This is what I got:

TCP 127.0.0.1:80 127.0.0.1:1839 CLOSE_WAIT
TCP 127.0.0.1:80 127.0.0.1:1842 CLOSE_WAIT

What is the problem?

I have tried restarting the service but no go :(

You should get one that says LISTENING at the end instead of CLOSE_WAIT. Check the Windows event log.
 

screw3d

Diamond Member
Nov 6, 2001
6,906
1
76
Originally posted by: n0cmonkey
Originally posted by: screw3d
This is what I got:

TCP 127.0.0.1:80 127.0.0.1:1839 CLOSE_WAIT
TCP 127.0.0.1:80 127.0.0.1:1842 CLOSE_WAIT

What is the problem?

I have tried restarting the service but no go :(

You should get one that says LISTENING at the end instead of CLOSE_WAIT. Check the Windows event log.

how would i do that? :eek:
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Control panel -> Administrative tools (or something like that, I don't have access to this stuff ATM :p) -> event viewer

Just look at the errors and warnings in there to see if any of them apply to Apache.