fatal error: cpg_sessions is crashed fatal error: cpg_sessions is crashed
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

fatal error: cpg_sessions is crashed

Started by lotoazul, July 11, 2010, 12:24:42 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

lotoazul

hello! i'm hoping someone can help me.

a few weeks ago, out of the blue one of my galleries (URL here) began throwing out a fatal error and wouldn't even let me view the main page, let alone log into the admin panel. i haven't touched that gallery in months, so i'm pretty sure it wasn't something i did. i'm running CPG 1.4.25, i actually tried to upgrade to 1.4.26 to see if that fixed things, but the upgrade failed-- i'm guessing because of the error.

i looked the error up, and found the tutorial for the debug mode. after i turned that on, the script gave me the standard "table cpg_sessions is marked as crashed" explanation that i know many previous posters have gotten. so i looked up the docs and learned that i had to repair the table. i went back to phpMyAdmin and ran the REPAIR TABLE sql query; you can see the result in the attachment to this post.

i figured that "table is up to date" meant something good, so i went back to my gallery and tried again-- nothing, i still get the error. cpg_sessions still seems to be marked as crashed when i look it up in phpMyAdmin.

is there anything else i could try? any help is appreciated.

Nibbler

Drop and re-create the table in phpMyAdmin.


DROP TABLE cpg_sessions;
CREATE TABLE IF NOT EXISTS cpg_sessions (
  session_id varchar(40) NOT NULL default '',
  user_id int(11) default '0',
  time int(11) default NULL,
  remember int(1) default '0',
  PRIMARY KEY (session_id)
) TYPE=MyISAM COMMENT='Used to store sessions';

lotoazul

that worked! thank you very much, nibbler.  :)

phill104

Thanks for coming back and resilving your thread.

I am sure you know you are a couple of versions behind (we are currently on 1.4.27) so please try and upgrade asap as you are at risk if you don't. This might be a good time to make the jump to the new 1.5.x line. ;)
It is a mistake to think you can solve any major problems just with potatoes.