I upgraded my gallery2 installation from 2.1 to 2.2.2 by downloading a fresh copy from svn, copying over .htaccess and config.php and running the upgrader.
Everything went smoothly although I now get Error: (ERROR_STORAGE_FAILURE) as below when trying to access 'Get More Plugins'. I also have the error when trying to install existing plugins although on refresh, they appear to be installed successfully anyway.
Any ideas? I have already performed the maintenance tasks in Site Admin and have cleared browser cache and cookies.
Thanks, David.
Quote:
Error Detail
Error (ERROR_STORAGE_FAILURE)
in modules/core/classes/GalleryStorage.class at line 624 (GalleryCoreApi::error)
in modules/core/classes/GalleryCoreApi.class at line 2800 (GalleryStorage::getMapEntry)
in modules/core/classes/GalleryRepositoryUtilities.class at line 289 (GalleryCoreApi::getMapEntry)
in modules/core/classes/GalleryRepository.class at line 178 (GalleryRepositoryUtilities::getPluginPackages)
in modules/core/classes/GalleryRepository.class at line 320 (GalleryRepository::getPluginUpgradeInfo)
in modules/core/AdminRepository.inc at line 326 (GalleryRepository::getRepositoryPluginList)
in modules/core/SiteAdmin.inc at line 201 (AdminRepositoryView::loadTemplate)
in modules/core/classes/GalleryView.class at line 300 (SiteAdminView::loadTemplate)
in main.php at line 441 (GalleryView::doLoadTemplate)
in main.php at line 94
in main.php at line 83
System Information
Gallery version 2.2.2
PHP version 5.2.1 cgi
Webserver Apache/1.3.37 (Unix) Resin/3.0.9 mod_mono/1.0.2 mod_fastcgi/2.4.2 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a PHP-CGI/0.1b
Database mysqlt 4.1.22-standard
Toolkits ImageMagick, Thumbnail, NetPBM, Gd
Operating system Linux bruja.thewebhostingserver.com 2.4.21-50.ELsmp #1 SMP Tue May 8 17:18:29 EDT 2007 i686
Browser Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)
Posted: Wed, 2007-07-11 18:40
Posts: 32509
your core upgrade wasn't successful. one or more db tables have not been altered correctly.
do you have a backup from your database from g2.1? if so, i'd restore it and try the upgrade again.
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 28
Restored the database and ran the upgrader again. It told me the core module was up to date and skipped that step. Is there anyway to force the database upgrade again?
Posts: 32509
> It told me the core module was up to date and skipped that step.
restore the versions.dat file in g2data/versions.dat as well.
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 28
erm...not got that one! Anyway to get the old core module version number in order to change the current (upgraded) versions.dat?
Posts: 32509
> erm...not got that one!
no problem, it's just a 2 line file. you just need to change them correctly. you can get the versions from your modules/core/module.inc file.
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 28
No go I'm afraid. Recreated versions.dat (thank you!) and restored database again, performed upgrade but still get the same error_storage_failure when working with plugins.
Posts: 28
I've also tried downloading the full file version of 2.2.2 rather than using svn and repeating the upgrade but that also displays the same error.
Posts: 28
Anything else to try? I need to be able to upload more photos and try out some extra plugins and I'd rather not proceed until I know everything has upgraded correctly!
Thanks, Dave.
Posts: 32509
please post the exact error stack trace you get right now (even if it looks very similar to the ones you posted already).
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 28
Attached is the debug output when going to get more plugins. Thanks.
Posts: 32509
> mysqlt error: [1054: Unknown column 'g_locked' in 'field list'] in EXECUTE("SELECT g_locked, g_packageVersion, g_packageBuild, g_packageName FROM g2_PluginPackageMap
ok, that's still the same, original issue and my initial reply still applies.
> No go I'm afraid. Recreated versions.dat (thank you!) and restored database again, performed upgrade
so did it upgrade the core module this time?
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 28
Everytime I have tried to upgrade, the upgrader has completed without errors and the versions.dat file is altered. It is only when I go into site admin and try to do anything with the plugins that I get the errors.
Posts: 1
I'm still on Gallery 2.2.1 and I'm also getting this same error on "Get more plugins", referring to an unknown column 'g_locked'.
I've upgraded from the 2.0 versions to 2.1 versions all the way to 2.2.1. Since the other poster has also suffered this from upgrading from 2.1 to 2.2.2 it looks like the upgrader has forgotten to add this 'g_locked' column somewhere. I don't have backups of the previous galleries to check this.
If it helps, I upgraded from 2.1.2 straight to 2.2.1 by unpacking a full 2.2.1 installation over the 2.1.2 installation, hence I missed out version 2.2. It appears the other poster has done a similar jump over version 2.2.
Would it not be possible to tell us how to add this 'g_locked' column directly in MySQL?
Posts: 28
anyone?
Posts: 28
bump
Posts: 28
I really could do with being able to use some additional plugins. Will a future upgrade be able to set the corrections automatically or will any database repairs need to be made manually? If it requires manual editing can anyone provide the steps or info?
Posts: 28
still have this issue. is there an update coming anytime soon that might correct this issue or can you provide details about manually fixing it?
Posts: 32509
there is no known bug / issue.
your g2_PluginPackageMap table should have g_locked column.
the g_locked column is added to the table when upgrading the core module (upgrade/index.php -> core module upgrade step) from versions before core module 1.1.17 to version 1.1.17 or later. or in gallery 2 versions: from gallery 2.0/2.1 to 2.2 or later.
if the table isn't changed accordingly, maybe your database backup that you restore before every upgrade attempt is already a bit corrupt or your application files are incomplete / corrupt.
@application files:
FAQ: How can I make sure that my installation files are all intact?
@database backup:
the PluginPackageMap table should be listed as in version major = 1, minor = 0 in your Schema table from before the upgrade.
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 28
Thank you! No errors were reported by the System Check so I simply added the g_locked column using phpMyAdmin and hay presto, it works!