Topic: Fatal Error: adter upgrade (Read 10269 times)

stilgs · « **on:** February 20, 2006, 08:50:34 am »

I am trying to upgrade from 135 to 143.

I am following the instruction in the doco word by word and still having no luck at all.

When i run the update.php the results say Already Done, and the last 10-15 lines are blank (results say already done).

When i then try to continue (checkversion or front page) all i get is Fatal Error:

Any help would be appreciated.

Joachim Müller · « **Reply #1 on:** February 20, 2006, 08:58:59 am »

make sure you replaced all needed files, make sure you have uploaded using the proper FTP mode, make sure you mySQL user has ALTER permissions, post a link for details

stilgs · « **Reply #2 on:** February 20, 2006, 09:03:51 am »

yeah i saw an earlier post about the ALTER and made sure of that one...

www.stilgs.com

Joachim Müller · « **Reply #3 on:** February 20, 2006, 09:10:10 am »

You haven't done as suggested, looking at your HTML output clearly shows that you're using cpg1.3.5 code. Re-read the upgrade section again and do as suggested. Make sure to not only replace the files in coppermine's root folder, but the files in the sub-folders (particularly the include folder) as well.

stilgs · « **Reply #4 on:** February 20, 2006, 09:15:20 am »

sorry about that... after i got the fatal error... i restored old files to get i working again..

Nibbler · « **Reply #5 on:** February 20, 2006, 01:48:09 pm »

Enable debug mode to get a more descriptive error message.

Cyberpawz · « **Reply #6 on:** February 20, 2006, 11:21:17 pm »

I am getting this same error, and I have followed the directions... I am upgrading from 1.3.5 to 1.4.3, and as of now nothing works, thankfully this is a backup but still...I am not happy, I can't upgrade at all... I can't side grade, and as far as I can tell I can't do squat... I need help and I'm getting lost in the process...

This is what I am reading...

http://www.cyberpawz.com/Coppermine2/docs/index.htm#13

And this is what I get as results...

http://www.cyberpawz.com/Coppermine2/

Something isn't right in Denmark, and it's not me. On that note, whenever I do the update.php it seems for some reason the updates aren't taking, but all folders and subfolders, and files have the CHMOD of 777

http://www.cyberpawz.com/Coppermine2/versioncheck.php

Oh, and this is what my database looks like now...thankfully it hasn't messed up the old server at all... and I do have backups thankfully even if it did.

(https://forum.coppermine-gallery.net/proxy.php?request=http%3A%2F%2Fwww.cyberpawz.com%2Fimages%2FPicture1.jpg&hash=e763c96f0e296a2193f95384dcb52f7757c04676)

stilgs · « **Reply #7 on:** February 20, 2006, 11:48:13 pm »

Okay have tried the update with the debug mode on. This is what i get on the page as well as Fatal error:

While executing query "delete from `cpg135`.cpg135_sessions where time<1140471913 and remember=0;" on Resource id #6

mySQL error: Table 'cpg135.cpg135_sessions' doesn't exist

I havent restored back to the old working site, so you can check it out if you want... www.stilgs.com

Ta

Nibbler · « **Reply #8 on:** February 20, 2006, 11:51:27 pm »

Give your mysql user the CREATE privilege and run the update.php again.

stilgs · « **Reply #9 on:** February 21, 2006, 12:35:48 am »

Just double checked and my sql user has ALL priveledges for my database.

kegobeer · « **Reply #10 on:** February 21, 2006, 12:53:52 am »

Looks like the MySQL dot in the database name problem. Do you agree, Nibbler?

Nibbler · « **Reply #11 on:** February 21, 2006, 01:24:59 am »

That dot is supposed to be there, it separates the db name from the table name. The problem is when there is a dot in the db name itself.

Something's adding extra single quotes to the queries like this:

Code: [Select]

INSERT INTO cpg135_filetypes VALUES (''jpg'', ''image/jpg'', ''image'', '''')
which causes the queries to fail due to bad syntax, it should of course be like this.

Code: [Select]

INSERT INTO cpg135_filetypes VALUES ('jpg', 'image/jpg', 'image', '')
A presumably similar problem has caused the file to not be split up into queries properly which is why the output of update.php looks incomplete.

The update.sql file is correct however, so I suspect something odd with your php setup that may be the same issue as http://forum.coppermine-gallery.net/index.php?topic=27586.0 and http://forum.coppermine-gallery.net/index.php?topic=23584.0

stilgs · « **Reply #12 on:** February 21, 2006, 01:46:51 am »

Is there a way to see if php was compiled with the --with-pcre-regex option?

Nibbler · « **Reply #13 on:** February 21, 2006, 01:48:18 am »

It will show on a phpinfo()

stilgs · « **Reply #14 on:** February 21, 2006, 01:58:48 am »

ah okay it has

'--with-pcre-regex=/usr'

Nibbler · « **Reply #15 on:** February 21, 2006, 02:16:55 am »

That's the issue then, contact your local server admin.

stilgs · « **Reply #16 on:** February 21, 2006, 02:19:31 am »

its my server

Nibbler · « **Reply #17 on:** February 21, 2006, 02:39:07 am »

That's convenient then.

Joachim Müller · « **Reply #18 on:** February 21, 2006, 04:35:20 am »

the joys of self-hosting

Cyberpawz · « **Reply #19 on:** February 21, 2006, 04:55:50 am »

Quote from: Nibbler on February 20, 2006, 11:51:27 pm

Give your mysql user the CREATE privilege and run the update.php again.

It does, and it still doesn't work.

News:

Author Topic: Fatal Error: adter upgrade (Read 10269 times)

Nibbler

Nibbler

Nibbler

Nibbler

Nibbler

Nibbler