|Posted: Fri, 2006-06-23 10:34|
I just performed an upgrade from Gallery 2.0-rc-1+ (core 0.9.34) to the current version via CVS - the command I used was:
The CVS update started up w/o issue, starting with...
-> main loop with CVSROOT=:pserver:email@example.com:/cvsroot/gallery
...and then scrolling thru hundreds of files; but ultimately it ended with an error; trailing portion of output follows...
I tried the same command several more times, but it continued to fault with the same "dying gasps" error ... and it always died just after the unlink_file(CVS/Entries.Log) line - does anyone know what this ENTRIES.LOG file is?
Anyway, I chanced it and accessed the g2 web admin console, whereupon it immediately started the "Gallery 2.1 Upgrader" ... the updater seemed to be functional, so I continued on; it worked ok for the most part, though one anomaly during this web portion of the upgrade was the following, in the "system check" (step 3, iirc):
Missing files (1168)
Continuing on, though, the good news is that the core version updated w/o issue (in fact, the version info you see at the top of this post is post-upgrade)...here's the info displayed just prior to the core upgrade:
Core Module Upgrade: Currently installed 0.9.34 New version 1.1.2 Config.php upgrade Required
However, during the "modules update" my luck ran out, and I ran into a series of issues/faults - was ultimately able to complete this step (and update *most* of the modules) by disabling the ffmpg module. Too, the "ImageMagick" and "URL Rewrite" modules appear to have failed the update (former didn't display an error during update, but the error displayed for the latter was Fatal error: Cannot instantiate non-existent class: modrewriteparser in /home/arc/public_html/webapps/gallery2/modules/rewrite/classes/RewriteHelper.class on line 74; and a current poll in site admin shows that the "URL Rewrite" module is not even installed).
Which brings me to the present and the matter at hand - the gallery albums seem to be working ok, but I'm having a problem with accessing the PLUGINS section of the Site Admin tool - upon selecting _any_ action for a given plugin (e.g., install, configure, deactivate, etc), the browser immediately displays an error page:
Really very odd - I checked the server, and sure enough in the "webapps" dir (where I have the gallery2 instal;" there is *no* MODULE directory; there is, however, a MODULES directory?!? So I tried renaming this latter dir to MODULE; but this only resulted in changing the error to:
Too, it cause some weird issues with the rest of the site admin console, so I quickly changed the dir name back to MODULE.
Re: the "forbidden" access error - this was odd, because said folder has drwxr-xr-x rights, as do all the files/folders within. For instance, here's a list of the imagemagick module's directory
drwxr-xr-x 10 arc arc 4096 Jun 23 01:37 . drwxr-xr-x 50 arc arc 4096 Aug 14 2005 .. -rw-r--r-- 1 arc arc 8762 Jun 23 01:37 AdminImageMagick.inc drwxr-xr-x 2 arc arc 4096 Jun 23 01:37 CVS -rw-r--r-- 1 arc arc 10770 Jun 23 01:37 MANIFEST drwxr-xr-x 3 arc arc 4096 Jun 23 01:37 classes drwxr-xr-x 3 arc arc 4096 Jun 23 01:37 data drwxr-xr-x 3 arc arc 4096 Aug 14 2005 debug drwxr-xr-x 26 arc arc 4096 Aug 14 2005 locale -rw-r--r-- 1 arc arc 9521 Jun 23 01:37 module.inc drwxr-xr-x 3 arc arc 4096 Jun 23 01:37 po drwxr-xr-x 3 arc arc 4096 Jun 23 01:37 templates drwxr-xr-x 7 arc arc 4096 Aug 14 2005 test
Any thoughts re: what could have broken and caused the modules to flaked out, and how to resolve? I'm guessing that the problems I'm seeing are due to the original problem with the CVS update, where it aborts; if this is the case, was hoping someone could advise what this "dying gasps" error means, and how to resolve it?