Hello Andrew,

Have you try to temporary disable the Admin Tools component and see how it goes? I'm afraid that Admin Tools automatically run the optimization in the background.

It made no difference. I disabled Admin Tools, which no longer has the automatic optimise/repair option, but my discuss_posts still crashes every 30-60 minutes.

My site has been out of action most of today. Even after repairing the discuss_posts table, the site produces blank pages.

Hello Andrew,

Sorry for the late reply. I've tried to access your backend but failed. And also I don't have permission to update file in your FTP. Please advise.

Both frontend and backend access are difficult because of the constant crashing of the discuss_posts table. I need to repair them all the time. I give you Cpanel access so that you can repair the table (database: rebelins_new). After you did that, you can get into the backend of the site.

Hello Andrew,

I suspect that your server has run out of disk space. Can you check with your hosting provider about it? Because our site also using Easydiscuss as a forum and I believe our table has more discuss post. As mentioned in article here: http://dba.stackexchange.com/questions/15075/why-do-mysql-tables-crash-how-do-i-prevent-it

If you run out of disk space while adding rows to a MyISAM table, no error occurs. The server suspends the operation until space becomes available, and then completes the operation.

Hope this helps.

I have plenty of disk space on my dedicated enterprise server. It's got terrabytes of storage left for site users to upload videos of up to 2GB each. But I think I found the problem. In the process of upgrading the site, first from the old Joomla 2.5/JA T3 platform to the the Joomla 2.5/T3 platform, then from Joomla 2.5/T3 to Joomla 3.3/T3 my 1GB database got duplicated twice. Having 3 x 1GB databases was a bit much even for my top-of-the-range dedicated server. After deleting the two old database, my server seems much happier.

Hello Andrew,

Is the issue with discuss_post table solved?

My site, which I upgraded to Joomla 3.3 last weekend, works perfectly fine now except for EasyDiscuss (http://therebel.org/forum) and EasyBlog (http://therebel.org/blog). It times out and produces blanks. I need your help with this.

This might be just a coincidence, but the problem with the two components went away after I disabled the Akeeba admin tools. I had remembered that I had turned them back on last night after deleting those two 1GB databases that were causing all that trouble with crashing tables.

However, I still have one more problem. EasyBlog is now producing an error message that wasn't there before I upgraded from Joomla 2.5 to Joomla 3.3.

http://awesomescreenshot.com/0a53yqc09c

Hello Andrew,

I've fixed it for you. Please have a look.

Thanks for that, Nik. It is much appreciated. I couldn't check it yet though, because my site won't let me into neither EasyBlog nor EasyDiscuss again. Siteground's engineers, who I've contacted about the problem are saying this:

They both started loading just fine after I disabled access to the site in order to strace the loading process. Then I noticed a lot of slow database queries in the log and I could suppose that - when the forum and the blog get a lot of visitors, their database queries are not well optimized for performance, the sites generate a lot of slow queries, while the prior slow query is executed, it locks the tables that it uses and makes all of the other requests queue up and wait.

You should talk to a professional developer and have them optimize the slow database queries of your site.

Please note that the rest of the site (Joomla Content, K2, HD Videoshare, DocManager) works fine. It's just EasyDiscuss and EasyBlog that time out.

I was able to get into the blog section. It's fixed, as you said. Many thanks.

Andrew

Hello Andrew,

As for the database optimization, I will consult with our database expert about it. Thanks for the information. We will see what we can do. And Glad that your issue has solved.

My discuss_posts table has crashed again overnight, after behaving well for about 12 hours, bringing my site to a grinding hold for hours. It is a very busy site, with - according to Google Analytics - a minimum of 10-20 visitors connected at any given moment (150,000 to 200,000 pageviews per day) I work in between 20-24 hours on my site, but I can't repair that discuss_posts table all the time. I've noticed that it is the biggest table in my database, with 50, 171 records and 450.3MB and it brings my site to a halt every time it crashes.

I urgently need a solution for this.

Hello Andrew,

Sorry for the late reply. Can you enable Slow Query Logs from the server and send us the logs file so we can see what is going on there?

You can download it from this link:

http://therebel.website/mysql-slow.tar.gz

Hello Andrew,

I've consulted with our SQL expert, and he said that your issue is caused by the buffer_size is too low. As you can see here, I hit this error http://screen.stackideas.com/2014-12-05_1648.png in your phpmyadmin when I try to run this:

optimize table j25_discuss_posts

and right after that your tabled has crashed. You might want to ask your hosting provider to increase the buffer_size of the server and also allocate more system memory to it. As I mentioned before, I believe our forum has more data than yours and doesn't hit this error.

By the way, I'm a bit curious about this issue that it's suddenly hit your site. Did you changing hosting provider recently?

Thanks for the feedback. I've notified Siteground of your suggestion concerning the buffer_size and allocated system memory. I haven't change hosting firm. What's changed is that I've upgraded from Joomla 2.5.27 to Joomla 3.3.6 which was a double upgrade, because I had to upgrade the template first to a version that is compatible with Joomla 3.3. Obviously I had to upgrade all of my extensions too. I've spent almost a month - and almost a thousand dollars on subscription renewals - on this project so far, the last week alone on trouble shooting after the Joomla 3.3 upgrade.

Siteground have come back to me with this response:

Per your request we have increased the following values in the MySQL configuration:

join_buffer_size
myisam_sort_buffer_size
sort_buffer_size
read_buffer_size
read_rnd_buffer_size

The PHP memory is also set to 2048MB. Please keep monitoring the server and let us know if more problems occur.

It's much better now. Thanks to switching on Memcache this morning and increasing the mySQL buffer sizes, EasyBlog and EasyDiscuss no longer produce error 500's or cache errors, even with the Akeeba Admin tools enabled. However they are still slow to open, compared to the other components (Joomla Content, K2 Content, HD Videoshare, DocManager). Thank you though for your help so far in getting my site working again.

Hello Andrew,

You're welcome. Glad to hear that from you.

The discuss_posts table has crashed again over night. The only difference this time that this crash didn't bring the entire site to a grinding hold. All the optimisations and finetuning I have done, have paid out that way, but I can constantly monitor my site for crashed discuss_posts tables and repair them. I have to sleep sometimes. Please go back to your SQL gurus and ask them how to stop these crashes from happening once and for all. I'd also be interested in what their buffer memory allocations are since they are running a forum with an even bigger discuss_posts table than me.

Hello Andrew,

I believe this has something to do with the total number of posts that you are having. To be honest, after much testing and sampling with EasyDiscuss, we realize that our database structure is not perfectly optimized because we store both discussion and replies within the same table which often leads to similar issues that you are having (especially when you try to optimize the table).

By the way, are you getting anything new on your slow error log file?

Since switching to memcache for both cache and session table, and increasing the memory allocation for the buffer to 20MB, the number of slow queries has gone down considerably, but i still have the problem that more often than not, EasyComment gets stuck in the entry form when saving a comment/reply and does not provide feedback that the comment/reply has been saved. This is frustrating for the user because it makes him think that his post has not been saved. They either save it repeatedly or give up. If I'm lucky, they email the comment to me and tell me that commenting is not working. It must have to do with the size of the discuss_posts table. It's much bigger than the content table even though it has less records. I didn't have that problem with Kunena which I was using before switching to EasyDiscuss, but I prefer the way your product is integrated with Jomsocial.

Hello Andrew,

When you mention EasyComment, did you mean Komento?

Sorry, I meant EasyDiscuss

Hello Andrew,

Sorry for the late reply. I've tried to post a reply and I do get the message telling me this: http://screen.stackideas.com/2014-12-12_0108.png . Did missed anything?

Since changing the editor from JCE to the built-in BBEdit one, posting new discussions/comments and replies has been working, however it takes a long time (30-60 seconds) to go to the next screen. That's way too long for a top-of-the-range dedicated server. It shouldn't take longer than a couple of seconds.

Hello Andrew,

It is advisable to use built in BBCode editor instead of other Editor because it renders faster. However, what did you mean by it takes a long time (30-60 seconds) to go to the next screen?

What I mean by that is that after switching from JCE to the built-in BBCode editor, EasyDiscuss no longer times out after posting a topic or reply, but goes to the next page. Unfortunately it takes 30-60 seconds to do so, a long wait for the users. As I said I have a very fast dedicated server with lots of RAM, harddisk space and processing power, so it shouldn't take that long.