mysql-opt.exe encountered a problem

[babyewok]

I have been using uniform server for quite a wile now with no issues. I recently updated the version of a CMS I am testing on my Windows configuration and I keep getting this error:

 

mysqld-opt.exe encountered a problem and needs to close.

 

In the XP event viewer I see this:

 

Faulting application mysqld-opt.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.6055, fault address 0x00019af2.

 

There is nothing in the uniform server error logs

 

The CMS developers say it's an issue with MYSQL and Windows and it has nothing to do with their CMS althoguh if that's the case I really don't understand why it has only recently started happening. It happens at the point where I click save in the CMS - in other words hwen it is communicating with the database.

 

Does anyone have even the slightest clue as to what is going on? It seems to have adverse effects on the database as info seems to be lost (although I can see it in the CMS back office, it doesn't show on the website and the relevant info in the databse seems blank!) the only way I can restore the info is to restore the database from a previous back up.

 

Please help!!

[babyewok]

Does no one have any suggestions? This is driving me mad!!

[babyewok]

Just found this in the MYSQL error log - everytime it has crashed, it seems to be when trying to optimise the same table:

 

thd: 0x11da3a8

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

7C919AF2 ntdll.dll!RtlpWaitForCriticalSection()

7C901046 ntdll.dll!RtlEnterCriticalSection()

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort...

thd->query at 01227AB0=OPTIMIZE TABLE perch2_content_index

thd->thread_id=89

thd->killed=NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.

130204 13:22:42 [Note] Plugin 'FEDERATED' is disabled.

130204 13:22:42 [Note] Plugin 'InnoDB' is disabled.

130204 13:22:42 [Note] Event Scheduler: Loaded 0 events

130204 13:22:42 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: ready for connections.

Version: '5.1.41-community' socket: '' port: 3306 MySQL Community Server (GPL)

130204 14:17:46 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Normal shutdown

 

130204 14:17:46 [Note] Event Scheduler: Purging the queue. 0 events

130204 14:17:46 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Shutdown complete

 

130204 14:17:53 [Note] Plugin 'FEDERATED' is disabled.

130204 14:17:53 [Note] Plugin 'InnoDB' is disabled.

130204 14:17:54 [Note] Event Scheduler: Loaded 0 events

130204 14:17:54 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: ready for connections.

Version: '5.1.41-community' socket: '' port: 3306 MySQL Community Server (GPL)

130204 17:22:48 [Warning] Warning: Optimize table got errno 5 on my_cms.perch2_content_index, retrying

130204 18:06:41 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Normal shutdown

 

130204 18:06:42 [Note] Event Scheduler: Purging the queue. 0 events

130204 18:06:43 [Note] C:/UniServer5_5a/UniServer/usr/local/mysql/bin/mysqld-opt.exe: Shutdown complete

[babyewok]

This still keeps happening intermittently and I could really do with some help as it is a complete pain in the backside as it screws up my CMS and I have to keep replacing the MYSQL data files from my backup!