[Solved]: mySQL error: Got error 134 from storage engine

[marcus123]

Hi there,

Our client has been using your gallery for a couple of months with no problems, but now when they try to view gallery (www.domain/gallery/index.php) it shows fatal error.

We saw posting and have activated debug mode, and it now displays mySQL error: Got error 134 from storage engine

There is more text displayed in the error message, but you request not to put debug output in a posting??

Gallery is version 1.4.1

Can someone help please?

Many thanks,
Marcus

[Hein Traag]

Your cpg is outdated. First you need to upgrade. Wait and watch the frontpage of this site as 1.4.18 is about to be released and is the latest stable version. or upgrade now to 1.4.17 and then later to 1.4.18

Houdoe
Hein

[marcus123]

Hi Hein,

Okay, have downloaded 1.4.17. Where do i find a simple set of instructions to perform an upgrade?

I want to make sure we do this right, as the client's gallery is a key part of their site, and they have several months of active/live images etc...

Thanks,
Marcus

[Hein Traag]

http://coppermine-gallery.net/demo/cpg14x/docs/index.htm

Open the documentation , all the instructions you need to perform a upgrade are in there.

Houdoe
Hein

[marcus123]

Hi Hein,

Done upgrade to 1.4.17, error message still appearing as before. Do you want me to post full error message?

Marcus

[Hein Traag]

http://forum.coppermine-gallery.net/index.php?topic=23411.0
http://forum.coppermine-gallery.net/index.php?topic=23490.0

and many such other posts....

Please do search before posting.

[marcus123]

Hi Hein,

Yes, I searched before posting, on error 134, and the other part of error text, but forum search comes up with no entries.

The full error message is:

While executing query "SELECT session_id FROM `databasename`.cpg140_sessions WHERE session_id=MD5('4e2108e892f31ce1f435fcb1b3196031e428fd4f5b017e504d6e74f430ca9589')" on Resource id #5

mySQL error: Got error 134 from storage engine


What could be causing this?

Marcus

[Hein Traag]

It's a problem with your database. Run a repair using phpmyadmin or contact your host.

[marcus123]

Hi Hein,

Contacted host and they did repair, and now working fine again.

Many thanks for your help.

Marcus