Critical Error after server goes down... Critical Error after server goes down...
 

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

Critical Error after server goes down...

Started by unquiet_void, August 03, 2006, 06:01:11 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

unquiet_void

My hosts server went down during the process of adding albums earlier this morning. As a result, There is apparently an error in the database stopping visitors from viewing my gallery at all. In addition, I cannot delete the category the albums were supposed to be in, even when in Debug Mode. Here is the error message. I can supply Debug Information if needed.

Thanks. ^_^


CRITICAL ERROR:
While executing query "SELECT a.aid, count( p.pid )  AS pic_count, max( p.pid )  AS last_pid, max( p.ctime )  AS last_upload, a.keyword FROM cpg148_albums AS a  LEFT JOIN cpg148_pictures AS p ON a.aid = p.aid AND p.approved =  'YES' WHERE a.aid IN (10, 11, 12, 13, 14, 23, 15, 16, 17, 18, 19, 20)GROUP BY a.aid" on 0

mySQL error: Got error 127 from table handler

Stramm

means a table got corrupted. Use a tool like phpmyadmin to repair the table or ask your host for support

unquiet_void

okay. well my hosts "support" isn't exactly brilliant and i'd be lucky if i got a reply tomorrow, lol. And unfortunately I don't have access to anything like phpMyAdmin...

I only installed my gallery yesterday, would it be okay to just delete the database altogether, make a new one and re-install the gallery from install.php?

or will that end up creating 2 galleries/more problems?

Stramm

Possible... but it's always good to have a tool like phpmyadmin. Download it, install and repair the table. Eventually your server will go down again and you have the same problem. To avoid that think about regular db backups (-> phpmyadmin)
http://www.phpmyadmin.net/home_page/index.php

unquiet_void