fop2GroupButton Table Crashing

[Sharvanek]

Hello,

When we create a new button group, the table fop2GroupButton is dropped and recreated many many times, sometimes it crashes the table-

ERROR 145 (HY000): Table './asterisk/fop2GroupButton' is marked as crashed and should be repaired

We're able to recover the table but this shouldn't be happening and it's entirely reproducible, does anyone know if this is a known issue? A brief search of the forum didn't yield anything that seemed to be the same as what we're experiencing.

Running the latest and greatest 2.30.02

Thanks!!

[nicolas]

Recreating a table in mysql should not crash it, ever. You have a problem with MySQL or your hard drive. Do you have free space on that drive?

Best regards,

[Sharvanek]

There's free space, and no other tables exhibit this issue, every time you visit the manager home it deletes the entries in the fop2GroupButton table and recreates them, is this normal? It looks like multiple managers may be colliding on it in some way or something.

Here's what I see when I load the manager home-

| 147418 | asteriskuser | localhost | asterisk | Query | 0 | updating | DELETE FROM fop2GroupButton WHERE group_name='All Buttons' |
| 147418 | asteriskuser | localhost | asterisk | Query | 0 | updating | DELETE FROM fop2GroupButton WHERE group_name='All Extensions' |
| 147418 | asteriskuser | localhost | asterisk | Query | 0 | update | INSERT INTO fop2GroupButton (group_name,id_button,context_id) VALUES ('All Extensions','346','0') |
| 147419 | asteriskuser | localhost | asterisk | Query | 0 | Sending data | SELECT extension, name, IF(dial IS null,CONCAT('VIRTUAL/',extension),dial) AS dial, IF(voicemail='no |
| 147419 | asteriskuser | localhost | asterisk | Query | 1 | updating | DELETE FROM fop2GroupButton WHERE group_name='All Extensions' |
| 147419 | asteriskuser | localhost | asterisk | Query | 0 | updating | DELETE FROM fop2GroupButton WHERE group_name='All Queues' |

Thoughts?

[nicolas]

That is normal. Multiple simultaneous deletes should not crash a table. If they do, then it is a problem with the database engine, not with the tool issuing those commands.

[Sharvanek]

Interesting, out of curiosity, why does it do this every time the fop2 manager is loaded?

[nicolas]

If you add an extension, or a queue, or whatever in your backend (FreePBX, Elastix, MiRTA, Thirdlane, etc), you need to update the default groups that FOP2 has as a convenience for users (All Extensions, All Queues, etc). So the reload fop2 action will recreate all those groups, that means that it has to add or remove entries that were added or removed from your backend. If you load the dashboard it will also recreate those groups. If you think that is the cause of a problem you can edit /var/www/html/fop2/admin/index.php and comment the line that calls "fop2_recreate_default_groups".

Again, doing this, even simultaneously, should not crash a table. If that happens your mysql is broken.

Also, I really doubt that you could have many users logged into the fop2 manager refreshing the index page just to do perform those group refreshes.

[Sharvanek]

Thanks, yea I've gone over everything and all is normal, I appreciate the detail. You'd be surprised what some zealous department operators can do

I've made some adjustments and we'll see how this goes, thank you for your responsiveness!!