75ZT Community

I see the other side is down again,
lucky when I cant sleep there is this one now.

7.17 am and still down

7.50am and still down...........................

Think this one had a slight blip too, or could I be wrong?

"there but for the grace of God, go I"

Yertiz wrote:Think this one had a slight blip too, or could I be wrong?

Yes, it did - the same problem we had just after it went live & I thought I'd fixed it. However, I can live with a reboot once a week for a while longer till we move it to a new server. In the meantime I'll tweak the web server settings a little more which. That should extend the time between reboots & might even fix the problem completely

If anyone wants to know the techie details: It looks like there is a memory leak in one of the Apache modules. By lowering the maximum number of reuses per worker process, the workers are killed & restarted before they can cause the system to run out of memory & hence lock it up.

hbb wrote:

Yertiz wrote:
If anyone wants to know the techie details: It looks like there is a memory leak in one of the Apache modules. By lowering the maximum number of reuses per worker process, the workers are killed & restarted before they can cause the system to run out of memory & hence lock it up.

Is this or was I unable to understand it.

kevin wrote:

hbb wrote:

Yertiz wrote:
If anyone wants to know the techie details: It looks like there is a memory leak in one of the Apache modules. By lowering the maximum number of reuses per worker process, the workers are killed & restarted before they can cause the system to run out of memory & hence lock it up.

Is this or was I unable to understand it.

Trust me!!
Nothing to do with me, it's all gobblydigook to me

'Twas techspeak. If I don't post the "reasons why" someone will always ask so years ago I started pre-empting them. Feel free to ignore it

hbb wrote:'Twas techspeak. If I don't post the "reasons why" someone will always ask so years ago I started pre-empting them. Feel free to ignore it

The trouble is, as I read it, it makes the quote appear to be from me

Anyway, with the problems on the other side it would be a good time to canvas for new members

Still down at 8:50, oh well I have work to do anyway!

hbb wrote:If anyone wants to know the techie details: It looks like there is a memory leak in one of the Apache modules. By lowering the maximum number of reuses per worker process, the workers are killed & restarted before they can cause the system to run out of memory & hence lock it up.

I thought that was obvious......

Yertiz wrote:The trouble is, as I read it, it makes the quote appear to be from me

I thought it was something I'd done but it wasn't It's easy enough to get quoting in a twist.

Yertiz wrote:Anyway, with the problems on the other side it would be a good time to canvas for new members

Oh dear. What a shame.

Thanks Dave (hbb) a good dose of Techspeak in the morning just gives me brain ache.

We can't prevent anybody canvassing for new members from other forums. It's a free country and the internet is even more so.


Obviously we can't condone it.

hbb wrote:If anyone wants to know the techie details: It looks like there is a memory leak in one of the Apache modules. By lowering the maximum number of reuses per worker process, the workers are killed & restarted before they can cause the system to run out of memory & hence lock it up.

Thanks for sharing a few details, Dave.

For those that might have noticed, we had a momentary outage about 5 minutes ago resulting in your browser delivering an "internal server error" message. This was all my fault as I was playing with some core-level functions. Apologies for anyone affected

Didn't notice here.

Jürgen wrote:Didn't notice here.

That can only be a good thing that no-one noticed

SpongeBob wrote:

Jürgen wrote:Didn't notice here.

That can only be a good thing that no-one noticed

Noticed what?

Yertiz wrote:Think this one had a slight blip too, or could I be wrong?

I noticed, do I get a prize??