Web Servers on Windows - Apache 2 thrashing, thrashing

This is Interesting: Free IT Magazines  
Home > Archive > Web Servers on Windows > July 2004 > Apache 2 thrashing, thrashing





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Apache 2 thrashing, thrashing
Aero Leviathan

2004-07-28, 6:08 pm

Hi - sorry for the newbie question as I'm sure it is

I just installed Apache 2 on WinXP.. during install I selected 'run
only when started on port 8080' because I don't like to have it
running all the time, it's just for design/test purposes, and I later
changed the port to 80 in http.conf... but ah...

When I start it in the console, it just thrashes the hard disk
endlessly. I've had it open for about 10 minutes now and my HD
activity light has been on constantly. Tried this a couple times,
opened, waited a while then closed and tried again with same results.
Nothing in the console window, not even the 'Apache v.xx running...'
like I used to remember with 1.x (which is gone now from a reformat).
And I can't connect to the server through a web browser either... just
times out.

My system resources should be quite sufficient, I have 700mb+ RAM and
a 1.5ghz Athlon.

Any advice would be greatly appreciated. Thanks..

Regards,
Dave
Kenneth Doyle

2004-07-28, 6:08 pm

aeroleviathan@gmail.com (Aero Leviathan) wrote in
news:270f2a86.0407272246.40d678b5@posting.google.com:

> Hi - sorry for the newbie question as I'm sure it is
>
> I just installed Apache 2 on WinXP.. during install I selected 'run
> only when started on port 8080'... I later
> changed the port to 80 in http.conf


I don't know the answer to you specific problem, but I'm curious if you
really meant to write 'changed the port to 80 in http.conf'. Shouldn't
that be 8080?

> My system resources should be quite sufficient, I have 700mb+ RAM and
> a 1.5ghz Athlon.


That's 10x more than enough. I'm currently running five different servers
on a 200mHz box with 72mb of ram; no problems at all.


--
CodeCutter - good, fast and cheap; pick two.
Aero Leviathan

2004-07-29, 5:50 pm

Kenneth Doyle <nobody@notmail.com> wrote in message news:<Xns9534AE807A59Anobodynotmailcom@61.9.191.5>...
> aeroleviathan@gmail.com (Aero Leviathan) wrote in
> news:270f2a86.0407272246.40d678b5@posting.google.com:
>
>
> I don't know the answer to you specific problem, but I'm curious if you
> really meant to write 'changed the port to 80 in http.conf'. Shouldn't
> that be 8080?

Actually I meant httpd.conf, but I did indeed change it to 80, from
8080 (which the installation wizard set).

>
>
> That's 10x more than enough. I'm currently running five different servers
> on a 200mHz box with 72mb of ram; no problems at all.

Kenneth Doyle

2004-07-29, 5:50 pm

aeroleviathan@gmail.com (Aero Leviathan) wrote in
news:270f2a86.0407291324.11d3f051@posting.google.com:

> Kenneth Doyle <nobody@notmail.com> wrote in message
> news:<Xns9534AE807A59Anobodynotmailcom@61.9.191.5>...


[vbcol=seagreen]
> ...I did indeed change it to 80, from
> 8080 (which the installation wizard set).


OK. I guess I'm just trying to figure out what 'run only when started on
port 8080' means. If you selected that option, then shouldn't you actually
start it on port 8080 if you want it to run?


--
CodeCutter - good, fast and cheap; pick two.
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com