Re: [Setup] database version mismatch error after 4.1 upgrade

[Maurits van Rees]

Op 26-03-12 16:44, tdavenport schreef:
> Hi,
>
> I recently upgraded my plone site from 4.0 to 4.1. Everything looked like it
> was going well for about 3 weeks. A couple of days ago I ran buildout to
> troubleshoot some plugin issues and got this error after restarting:
> ___
> WARNING! Your database requires a newer version of Plone than you are
> currently using. This is a dangerous situation. Please upgrade your Plone
> version as soon as possible.
> Version Overview
>
> Plone 4.1
> Zope 2.13.8
> Python 2.6.7 (r267:88850, Sep 15 2011, 16:00:05) [GCC 4.4.5]
> ___
>
> From this message it looks like I have a version of zope that is too new
> should be (2.12.x). I am guessing that this is because I screwed something
> up when I upgraded before.

No, Plone 4.1 and Zope 2.13 are fine to use together; that is the default.

> I am not sure of the best way to proceed. We are using the site as a company
> intranet and users have been adding content for the last 3 weeks. I could
> not find any documentation about downgrading, and 4.2 is not stable yet.
> Does anyone have suggestions on a strategy for getting back to a stable
> state?
>
> So far my best idea is to make a new Plone install from scratch on another
> host and try to import a database dump of my current site. I am not sure
> that this would even work due to database changes.
>
> Any ideas or insight would be appreciated. I am new to plone and not quite
> sure what the right information to include is.
>
> Best,
>
> Todd Davenport

Hi Todd,

It looks like your database is now using a lower Plone version than what
was previously used. So I wonder if the bin/buildout has somehow caused
a (small) downgrade in the Plone version.

Log in as admin and go to these urls (change example.org to your own
domain):

This is the Plone 'profile' version that is installed in your database:
http://example.org/portal_migration/getInstanceVersion

This is the file system version of the Plone profile:
http://example.org/portal_migration/getFileSystemVersion

I guess that last one will report 4109 and the first one will be higher.

Report those versions back here and we may have a better idea of how to
solve this. If getInstanceVersion is higher thatn 4109 but still lower
than 4200 then I guess you should just change your buildout.cfg to extend
http://dist.plone.org/release/4.1.4/versions.cfg

Kind regards,

--
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl

_______________________________________________
Setup mailing list
Se...@lists.plone.org
https://lists.plone.org/mailman/listinfo/plone-setup

[Todd Davenport]

Greetings Maurits,

Thanks for your kind response. I was out of the office for a few days and just got back in.

Looks like your suspicions are correct.

> It looks like your database is now using a lower Plone version than what was previously used.  So I wonder if the bin/buildout has somehow caused a (small) downgrade in the Plone version.
>

> http://example.org/portal_migration/getInstanceVersion
>
Reports: 4113

> http://example.org/portal_migration/getFileSystemVersion

Is, as you predicted 4109.

> I guess that last one will report 4109 and the first one will be higher.
>
> Report those versions back here and we may have a better idea of how to solve this.  If getInstanceVersion is higher thatn 4109 but still lower than 4200 then I guess you should just change your buildout.cfg to extend
> http://dist.plone.org/release/4.1.4/versions.cfg

I'll change buildout.cfg and update as you suggested this evening and report back if I have problems.

Thanks so much for your help and explanation,

Todd Davenport