Print

[funiran]

Hi
i installed version 1.2.1 twice, after some days the cpg_pictures table damaged
i don't know why
i had about 170 pictures in it.
please help me

[Joachim Müller]

link?

GauGau

[funiran]

Hi
I don't know why after about 1 month , the database of this script will damage.
you can find this error on my site here :
http://www.funiran.com/album/

please help me....

[Casper]

Turn on debug mode in config.  If that does not help you solve the problem, post the debug info here.

[funiran]

hi
the link is : http://www.funiran.com/album/

please help me

[Joachim Müller]

do not double post - I merged your two identical postings into one :evil:

GauGau

[funiran]

hi
i turned on debug mode.
now , what should i do???
I know the DB was damaged. what should i do?
i don't want doing recovery actions every 20 or 30 days.

url is
http://www.funiran.com/album/index.php

[Joachim Müller]

Well, you seemed to have discovered the problem on your own: your mySQL database table is broken. Try to use the built-in repair functions of mySQL (either with phpMyAdmin or shell access - refer to mySQL documentation), or contact your webhost and ask them for a backup of the mySQL database (some webhosts actually back up the databases for you).
This is not related to coppermine - coppermine will not break your database file itself, but usually something has become broken on your server (sometimes hard drive sectors just "die"), so if you manage to get this fixed, this usually won't happen again. To be safe, backing up the mySQL db on a regular schedule is recommended.

GauGau

[funiran]

dear
my host hasn't any problem,
because i have several database and tables on it and they are working very good
but the pictures database of this program after evrey 20 or 30 days will destroy.
i think there is a hidden problem ...
 :cry:

[Joachim Müller]

you're the first user to report this - with thousands of installs of coppermine: I don't think that coppermine "destroys" the database. Make regular backups (preferably with cron jobs) and run a server log (apache log preferably) to check what could be wrong.

GauGau

[quikman]

Unfortunately funiran is not the only one that has experienced the problem. I too have had this happen twice. The first was about a day after I first set up coppermine. That wasn't too much of a problem as there were only a few images and I reinstalled the database. It has happened today (3 months later). The only file damaged is the picture file:

Code: [Select]

Select failed: select * from cpg11d_pictures
Can't open file: 'cpg11d_pictures.MYD'. (errno: 145) I manage around 20 databases with over 300 files. In 4 years,  I have only had problems with 1 file which has been corrupted twice. This seems too much of a coincidence to me.

Could it be because I am running version 1.2.0 - RC2?

[Joachim Müller]

usually broken mySQL tables can easily be repaired using mySQL's built in repair functions (either use them from the shell or by script, preferably with a tool like phpMyAdmin). Broken mySQL tables usually indicate a server hardware problem - if the hard disk in your server is about to break and sectors keep "dying", this is expected behaviour. A php script running mySQL queries should not be capable of ruining your database file this way.
Of course you could say it's only natural I'm trying to defend coppermine, but I can tell you from my experience that mySQL tables do break from time to time, no matter what application is accessing it (and I know what I'm talking about, I'm a server/network admin in "real life" and have experienced broken mySQL db files with various apps).

GauGau

[quikman]

Thanks for the fast response. I couldn't see how a script could actually break a table in this manner. The coincidence seemed just too much. It's unlikely to be hardware in this case as the ISP runs AIX on IBM risc servers. I guess I'll have to put it down to "one of those things".

Unfortunately shell access isn't possible. I'll try installing phpMyAdmin. This ISP doesn't provide database backup. I presume I will be able to use phpMyAdmin for that.

2 questions:

1. Have you considered including a backup routine in coppermine?
2. If the table is unrecoverable, would this be a good opportunity to upgrade to ver 1.2.1?

[Casper]

1. This has been discussed, http://forum.coppermine-gallery.net/index.php?topic=816

2.  upgrading to the latest stable version is always recommended, but as a fully stable release of 1.3.0 is very close, and the beta version is running well, with just a few minor probs to sort, such as a glitch when uploading from a bridged gallery, you may want to go straight to that.