In conversations with a few other forum members, I have come to realize I'm not the only one experiencing various SQL errors, driver errors, and general site slowness.

Since I have encouraged others to make use of the Site Info forum to inform site admins (since how else will they know, right?), I figured I should do it also.

I am posting the error (snap shot of the page) and any pertinent info I can provide. Here is my first:

SQL Error encountered at approximately 10:00am Pacific Time after posting a reply to a thread ("Patty and Me") in the Vintage section of the forum. I am also noticing slow page loads at this time as well. Other sites are loading fine. Browser in use: Chrome.

 

https://www.s2ki.com/s2000/topic/100...-server-error/

lots of posts, no answers.

 

ok. Well, I figure squeaky gear and all that...

 

I will follow-up on this.

 

Various SQL errors (sorry, nothing specific but a couple of the same that Murph is experiencing), double-posting now and then due to slowness. System takes approximately 30 to 45 seconds to do initial page loads. Can take up to 45 seconds (if indeed it does) to load new notifications. At times, have to stop page load and do a refresh/reload to get pages to load. Overall very slow, non-responsive.

 

Slow speeds are often due to ads, install AdBlock Plus and it speeds up tremendously.

 

Tapatalk doesn't display ads. Slowing there can't be contributed to ads.

 

And they reared their ugly heads again tonight at 9:10pm Pacific Time. Multiple pages I tried to get to on the forum in Site Info and S2000 Talk.

An error occured with the SQL server:
This is not a problem with IP.Board but rather with your SQL server. Please contact your host and copy the message shown above.

 

And soooooooo sloooooooooowwww too. Took long enough to load two pages (in different tabs in Chrome) that I toggled over to another Window to do something else while it decided whether to load, post, or error out again. It generally takes more than a minute for me to lose patience and toggle away. It eventually loaded the one page and posted the other (the above post in this thread).

 

FYI:

I have an update on this. It looks like there is an optimize tables cron that runs every day around 9pm that causes this error and site slowness. We are going to test to see if we can completely remove it, but for the weekend we moved it to a later time