Fatal error (one of the reasons) Fatal error (one of the reasons)
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Fatal error (one of the reasons)

Started by djarnis, March 05, 2007, 09:01:16 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

djarnis

This entry is mostly ment for people who run in to the same problem.

Today when I looked at my gallery, I saw nothing but the "Fatal error: " mesasge. I haven't made any changes within the last few days, so I actually feared that I had been hacked, however the problem was not even close to that.

It seemed that the table "cpg_sessions" had crashed and a repair was all that was needed to get the gallery up'n'running again.

Maybe there should be added some extra info to the "Fatal error:", so it clearly says that it's because a table has crashed?

I know there are other reasons that can trigger the message, but afaik then it should be possible to catch the above one. On the other hand, then I have no idea how the table got crashed in the first place or how you can force a crash to debug it :(.

/dj

Nibbler

Database error messages are not shown to website visitors for security reasons. There are instructions on how to get the detailed message and how to repair a crashed table available on this site. The most common cause for the tables to become corrupted is the MySQL server shutting down or restarting unexpectedly.