David,

Try to have them change your shared server, that has the beehive software on it. They will resist I'm sure. I had to threaten to cancel serveral accounts to get my provider to make the change.

They really don't like to host sql based forums, In all rights they are correct in saying the server doesn't have any any problems. They will probably also tell you that the sql databases are an added bonus feature and are not meant to be used with a forum.

The other solution is to go to a dedicated maintained server that has the sql database on the same server as the software, but as you remember that can also have problems. The other solution is to have multiple servers with different providers and load share them, which is how I have WOE, the downside to this is the software required to manage and sync them. In theory with the multiple servers you should never be down and have resonable speeds.

In any event, good luck.

It is timing out contacting the sql server! When I posted to you I received this error and had to post it 3 times to make it work.

Error Message for server admins and developers:

Unknown error [2013]

Lost connection to MySQL server during query

SELECT USER_THREAD.UID, USER.NICKNAME, USER.EMAIL FROM EE_USER_THREAD USER_THREAD LEFT JOIN USER USER ON (USER.UID = USER_THREAD.UID) WHERE USER_THREAD.TID = 5803 AND USER_THREAD.INTEREST = 2 AND USER_THREAD.UID NOT IN (200, 4)

Unknown error in line 132 of file db_mysql.inc.php

Beehive Forum 0.7.1 on PHP/4.3.11 Linux CGI-FCGI, MySQL/40027

Thanks again Ken.

You're correct in saying that Go Daddy regards the Beehive (sql database) software as some sort of Martian invention and points to it as the likely problem.

Looks like a server/hosting change will be comiing in the near future.

I appreciate the info.

127 function db_query($sql, $connection_id)
128
129 {
130
131     if ($result = @mysql_query($sql, $connection_id)) {
132
133        return $result;
134
135     }

Philadelphia, PA (Really Bensalem)

When you finally understand it completely... it changes.

It's timing out from the query on line 131 before it returns any results (line 133). Sounds like an internal routing problem.

Since you are also having FTP problems, it looks like getting to the server is no problem, but getting anything back from the server is the slow down.

Maybe the super bowl ad showing everyone in the marketing room having a party is the problem B-)

As Ken points out, the error was actually on the line number before the line number it mentions. That is typical with error messages. The error happens trying to get past line 131, so is marked as being at line 132. But the actual problem occured while trying to complete line 131.

I have had similar MySQL delays and errors on shared servers. Again, as Ken points out, the database server is often a seperate server and is also shared by a lot of sites. Any one of them could cause a problem. Growing log files in the database can also start to bog a database server down.

I had a forum that had similar slowdowns every few months and I had to call the host and have the MySQL server restarted each time. I finally gave up and moved to a different host and the problem went away.

If there are delays in doing FTP, that points away from the database server, and points more to the web server itself or a router in the system. A router problem can also cause the database errors. And if it's a router problem, the server could test out fine in-house, but have a problem getting to it from the web.

David,

When I logged on about 10 minutes ago it was slooooooow. But within the past minute it is back to normal. Hopefully it is fixed.

David,

Here is a free, for 30 days at least, monitoring program that tests the websites speed in opening and uptime every 5 minutes, 24/7

http://www.webmetrics.com

Yes, for the 30 days free trial. I didn't pursue after the trial.

Dave

Well ^)^%)())!!!!!

We just went with a new hosting service with a wonderful reputation for up time.

So after a few days we went down. ^&)&^^*(!!!!!

I will say that they were responsive and we were up in about an hour. Let's hope it is the last time. :/

Philadelphia, PA (Really Bensalem)

When you finally understand it completely... it changes.

I didn't want to say anything................but I was starting to get worried.

Glad it's back up and running.......

Hopefully it's all done hiccuping. :)