Advanced search  

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

Pages: [1]   Go Down

Author Topic: [Solved]: Fatal Error. Debugged already, what to do next?  (Read 5717 times)

0 Members and 1 Guest are viewing this topic.

VikiL

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
[Solved]: Fatal Error. Debugged already, what to do next?
« on: December 08, 2008, 06:20:10 am »

Hello,

My gallery: http://viiki-world.net/gallery

My gallery was working last night when I checked but when I went to my site today, the link to my gallery shows "fatal error." I read some topics here saying that I should go to "debug mode." I did and now I receive the following message:

"While executing query "delete from `coppermine`.cpg14x_sessions where time<1228709486 and remember=0;" on Resource id #6

mySQL error: Can't open file: 'cpg14x_sessions.MYI' (errno: 145)"

Did I get hacked? What should I do?

Thanks so much in advance! I am not very good with this business so please be patient with me.


« Last Edit: March 13, 2009, 07:47:34 am by Joachim Müller »
Logged

François Keller

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: fr
  • Offline Offline
  • Gender: Male
  • Posts: 9094
  • aka Frantz
    • Ma galerie
Re: Fatal Error. Debugged already, what to do next?
« Reply #1 on: December 08, 2008, 07:22:02 am »

a quick search on this board with your error message give this result
http://forum.coppermine-gallery.net/index.php/topic,10409.0.html
next time search the board before asking for support  ;)
Logged
Avez vous lu la DOC ? la FAQ ? et cherché sur le forum avant de poster ?
Did you read the DOC ? the FAQ ? and search the board before posting ?
Mon Blog

VikiL

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: Fatal Error. Debugged already, what to do next?
« Reply #2 on: December 08, 2008, 09:53:22 am »

I did search and I found the same thread. However, where do you change the table name? I logged onto my phpMyAdmin but I don't where where to "Replace cpg131_pictures with your table name" What is "my table name"? Can you give me an example?
Logged

François Keller

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: fr
  • Offline Offline
  • Gender: Male
  • Posts: 9094
  • aka Frantz
    • Ma galerie
Re: Fatal Error. Debugged already, what to do next?
« Reply #3 on: December 08, 2008, 10:00:17 am »

Quote
While executing query "delete from `coppermine`.cpg14x_sessions
your table name is cpg14x_sessions (it's in th error message)
Logged
Avez vous lu la DOC ? la FAQ ? et cherché sur le forum avant de poster ?
Did you read the DOC ? the FAQ ? and search the board before posting ?
Mon Blog

VikiL

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: Fatal Error. Debugged already, what to do next?
« Reply #4 on: December 08, 2008, 10:39:34 am »

Hi, I must sound really stupid or something...

so do I replace "cpg131_pictures" to "cpg14x_sessions"? If so, where can I do that in the database?

Thanks in advance! Sorry but I am very slow with this stuff.
Logged

Fabricio Ferrero

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: 00
  • Offline Offline
  • Gender: Male
  • Posts: 1996
  • From San Juan, Argentina, to the World!
    • http://fabricioferrero.com/
Re: Fatal Error. Debugged already, what to do next?
« Reply #5 on: December 08, 2008, 12:49:08 pm »

If you read carefully the thread that François linked it says:

Quote
The error:

Can't open file: 'cpg131_pictures.MYI'. (errno: 145)

The problem:

Your table is corrupted.

The solution:

Use your website's Control Panel to repair the table, or use phpMyAdmin to execute this sql query: repair table cpg131_pictures
(Replace cpg131_pictures with your table name)

And, the answer in that thread it says:

Quote
ask your webhost for support, this issue is not directly related to coppermine.

So please, do a little bit of learning before keep posting... ;)
Logged
Read Docs and Search the Forum before posting. - Soporte en español
--*--
Fabricio Ferrero's Website

Catching up! :)

VikiL

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: Fatal Error. Debugged already, what to do next?
« Reply #6 on: December 08, 2008, 10:20:33 pm »

Hi,

I would love to learn but you can direct me to a place to learn how to fix this problem?

I asked my webhost for help but they said they don't support third-party stuff...if you guys are not suppose to help me since it's not a coppermine problem, can you direct me to a place where I can fix this?

Now I've got this problem...the error message changed.

"While executing query "delete from `coppermine`.cpg14x_sessions where time<1228767558 and remember=0;" on Resource id #6

mySQL error: File './coppermine/cpg14x_sessions.MYD' not found (Errcode: 13)"
Logged

Nibbler

  • Guest
Re: Fatal Error. Debugged already, what to do next?
« Reply #7 on: December 08, 2008, 10:24:17 pm »

Go into phpmyadmin, click on the SQL tab and enter

Code: [Select]
REPAIR TABLE `coppermine`.cpg14x_sessions
Then press 'Go'. If that doesn't help run this instead and then run update.php.

Code: [Select]
DROP TABLE `coppermine`.cpg14x_sessions
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: Fatal Error. Debugged already, what to do next?
« Reply #8 on: December 21, 2008, 12:18:19 am »

And tell your webhost that the issue does not lie within a "third party application". The database is broken. This usually happens if there is something wrong with the server setup. That is the business of your webhost and none of ours. If your webhost is so ignorant and doesn't realize that, you better look for a new webhost.
Logged

VikiL

  • Coppermine newbie
  • Offline Offline
  • Posts: 7
Re: Fatal Error. Debugged already, what to do next?
« Reply #9 on: March 13, 2009, 06:09:28 am »

Thank you Nibbler, the first code solve the problem!
Logged
Pages: [1]   Go Up
 

Page created in 0.043 seconds with 19 queries.