Website slow

[Forest#2]

Yes. (very slow or no go.

I had to copy/paste my post into word and then come back couple hours later and try again. By saving to word I did not have re-type all again.

 

[Auto Doc's]

No one is maintaining this site, they have left it on autopilot.

 

[Auto Doc's]

No one is maintaining this site, they have left it on autopilot.

 

[MarkoBohm]

Thank you.

 

[Forest#2]

No one is maintaining this site, they have left it on autopilot.

and autopilot let it crash!!!!!!!!!!!!!!!!!!!!! (and burn)

still really slow in most threads.

 

[Ibrahim]

I am monitoring it and have been noticing the slowdowns. I haven't been able to find what's causing them yet, but I've put more active monitoring in place.

 

[Auto Doc's]

It happens even at 2AM when I'm working all night or cannot sleep. The afternoons are the worst.

I have the impression that the server is constantly overloaded and nothing is being archived.

 

[Ibrahim]

It happens even at 2AM when I'm working all night or cannot sleep. The afternoons are the worst.

I have the impression that the server is constantly overloaded and nothing is being archived.

Well the server is being monitored more now. I did find a misconfigured script that hopefully was the culprit with our constant timeouts. But I'll be monitoring it and we'll see.

 

[Auto Doc's]

Your efforts are appreciated; some very good members have dropped out due to the hangups.

We are all just trying to help people the best way we can without added aggravations of a slow site.

 

[Ibrahim]

Your efforts are appreciated; some very good members have dropped out due to the hangups.

We are all just trying to help people the best way we can without added aggravations of a slow site.

We appreciate you using the forum! And I want to apologize for the really crappy performance over the past several months. I thought it was more stable than it was because I had "fixed" it a few times over the past months. But while I thought it was something taking time to build up, it was a bug that was almost immediately gumming up the works. It's been only 12 hours since I tried a fix but it SEEMS like I may have found the culprit.

For those curious: A monitoring script was "half-installed" but not configured so it kept trying to login to check the status of the database. But using a wrong username. No big deal? Sure, except it was also set to try to check EVERY MINUTE.

That's been cleared up and fixed and so far it's been about 12 hours and it's been ok. A little too early to claim victory, but fingers crossed.

If anyone notices bugs going forward, comment here and I'll read it and take a look. Thanks again for your patience.