New Message: Frontier chrashing up to 100 times an hour

[Brad Marsh]

Hello,

I have had this same problem. For a while, I thought I had it licked. I used
to have a static server (Apache, running on port 80 on a different machine)
serve my .js and .css files. When I changed it to run on port 90 of the same
machine (and changed all my pages to ask for it there), Frontier suddenly
stopped crashing.

Then, starting July 17, I added some other components to the web site (which
did not change how these files were served), and Frontier started crashing
again. I have since changed it so that all .js and .css files are served by
Frontier from an "include" table (a subtable of the main Manila site), but
this has not slowed down the crashes.

Another symptom I've noticed is that the system.temp.pageTableAddresses
fills up with entries - like, up to 60 or 70 - that stay there until
Frontier crashes. It's like Frontier is holding on to the pages and never
finishing the processing.

I have not noticed RAM or CPU usage increase radically (I have a dual CPU
machine with 1GB of RAM). CPU usage typically runs at 8% (first CPU, less
for the second), and I usually have ~650MB physical memory available. We're
averaging ~150k hits per month.

I just throwing this out as a data point...maybe it will help light the
lightbulb for one of you gurus. Pleeeeeeeze.

Cheers,

Brad Marsh

On 8/4/03 10:07 AM, "webmaster at userland.com" <webmaster at userland.com> wrote:

> A new message was posted:
> 
> Address: http://manila.userland.com/discuss/msgReader$164
> 
> By: Tom Fuerstner (tom at fuerstner.at)
> 
> hi,
> 
> i'm completely frustrated. some days ago frontier started to crash several
> times a day. now it doesn't stop crashing any more.
> 
> we use a simple script to restart frontier automatically but this is just a
> work-around.
> 
> we are also serving our pictures from a different machine and we have already
> replaced all root-files, guest-databases and son on with backup-files.
> 
> i also stopped every possible threaded service and stopped every service we
> didn't need.
> 
> so finally i ran out of ideas.
> 
> we run manila version 9.1b3 on a dedicated windows 2000 machine as our
> cms-server. the crash logs of dr. watson tell me that it's obvioulsy the same
> error andre radke believed to have solved by turning off the
> radioCommunityServer. but... we've never activated this functionality.
> 
> the problem is even worse because we are serving manila website to paying
> customers who are starting to be obset.
> 
> i consider this a dramatic failure because it's impossible for a single
> developer outside of userland as a company to solve this kind of problems.
> 
> so, help is more than appreciated !!!
> 
> - Thomas Fuerstner
> 
> This is a Manila site.. http://manila.userland.com/.
> 
>