Site slow again tonite..

[MyGlockRocks19]

Seems like its all ok now.

 

[MoparMan]

 

[Militarypol21]

Just now able to get back on after seeing "This page cannot be displayed" for about 20 minutes but I was able to go to google, yahoo, msn, ect...

 

[360]

What are you talking about we need Go Daddy?

I never looked before I made that comment...you ARE at GoDaddy...or is the domain registered there and the site hosted somewhere else?

Dang...is someone jacking with the database again?

Just my but wouldn't it be better to do maintenance between 2-5 am when the site is asleep?

 

[Fenway]

What do you mean we are at Go Daddy? This site is not hosted at Go Daddy but I do use Go Daddy for domains.

Who said we were doing maintenance?

I never looked before I made that comment...you ARE at GoDaddy...

Dang...is someone jacking with the database again?

Just my but wouldn't it be better to do maintenance between 2-5 am when the site is asleep?

 

[360]

I said it.

 

[HICKMAN]

I notice it was REALLY slow a while ago when we had 240 people on the site.

260 on right now and it's delaying again, but not as bad as it was earlier.

 

[Lars]

What do you mean we are at Go Daddy? This site is not hosted at Go Daddy but I do use Go Daddy for domains.

Who said we were doing maintenance?

Unrelated items Fenway.

The site went sideways tonight. Unfortunately Scutter was driving back from Michigan, and I was on the road. I pulled into the Watson's parking lot, fired up the laptop and fixed it.

We're putting a crutch in place to keep "this" problem from happening while I continue to test configurations on a local copy of the site.

 

[IndyGunworks]

so what was the problem?

 

[360]

Last time I dealt with something like this, it was a licensing callback issue.

 

[Lars]

mpm_prefork

The threads aren't dying when they reach the "MaxRequestsPerChild" value and continue to grow in ram use.

Working on rebuilding apache so we can move to mpm_worker which is FAR superior.

 

[360]

which version of Apache are you using?

 

[printcraft]

mpm_prefork

The threads aren't dying when they reach the "MaxRequestsPerChild" value and continue to grow in ram use.

Working on rebuilding apache so we can move to mpm_worker which is FAR superior.

Yes, obviously that was the problem...

I was going to suggest you drop boot the ram and add the attacking apache application support PRAM values to the boot list, thereby creating an adverse inference due to the PerChild listing via the in use mpm_agent setting
afterward inserting the prespork system stats.

 

[360]

mpm_prefork

The threads aren't dying when they reach the "MaxRequestsPerChild" value and continue to grow in ram use.

Working on rebuilding apache so we can move to mpm_worker which is FAR superior.

Yup. Mem leaks suck.

 

[42769vette]

good on my end

 

[Andre46996]

Yes, obviously that was the problem...

I was going to suggest you drop boot the ram and add the attacking apache application support PRAM values to the boot list, thereby creating an adverse inference due to the PerChild listing via the in use mpm_agent setting
afterward inserting the prespork system stats.

Please step away from the keyboard!!!

It has been awhile but I am reasonable sure that is all sarcasm. I hope.

 

[T-rav]

I though it was just me I was abut the throw the mac out the window

 

[Bigum1969]

Yes, obviously that was the problem...

I was going to suggest you drop boot the ram and add the attacking apache application support PRAM values to the boot list, thereby creating an adverse inference due to the PerChild listing via the in use mpm_agent setting
afterward inserting the prespork system stats.

If that doesn't work, you could consider a reboot...


Seriously, Lars we owe you a debt o gratitude for all your hard work on the site. It is appreciated!

 

[Fenway]

Yes we do. We are fortunate to have Lars and Scutter who can work on this stuff!

 

[Roadie]

Yes we do. We are fortunate to have Lars and Scutter who can work on this stuff!