Thanks, the database upgrade was successful! I just had to import the settings table and everything seems fine!

 

Now about the xsds and workflows, I still don’t know what those are or are for, but I’ll just take your word for it and leave the xsds alone for now, but re-import the workflows.

 

Thanks again for the help, I appreciate it! I’m sure I’ll be posting again if I run into further issues.

 

Thanks,

Doug

 

From: Peter Newman [mailto:Peter.Newman@cdu.edu.au]
Sent: Wednesday, April 08, 2009 9:27 PM
To: fez-users@lists.sourceforge.net
Subject: Re: [Fez-users] Upgrading Fez and Fedora...

 

Hi Doug

 

I have updated the sql upgrade script so that the create table statements only execute if the tables don't already exist (which should get around your issue there). 

 

Note that the upgrade script will not proceed past the point it fails and there are a significant number of updates that will cause you problems if they are not run.

 

Currently Christiaan has some experiemental code in the trunk for collaboration so testing of this is limited but I have been keeping the release 2.1 branch up-to-date with fixes from the trunk and testing it's stability.  Also I'm currently running a production system off this branch which has helped to identify some minor issues already.  So my advise is to use the release 2.1 branch ;)

 

Things to note about this branch is that it now uses:

 - upgrade/xsds.xml uses svn trunk revision 1603

 - upgrade/workflows.xml uses trunk revision 2177

 

This is temporary (and what I'm using in production).  I'm working on issues with the current versions of these files and will fix them before a new (and hopefully final) release candidate for release 2.1 is completed.

 

So after an sql upgrade you will also need to delete workflows and reload them.  I probably wouldn't delete xsds and reload them yet because the release candidate will have cleaned up the xsd displays somewhat...

 

Hope this helps...

 

Also any new functionality in the trunk will be merged into the branch after a cooling off period and further testing (unless that functionality is a major change).

 

Cheers

Pete

 

 


From: STANLEY, DOUGLAS [mailto:dmstanle@kent.edu]
Sent: Thursday, 9 April 2009 4:04 AM
To: fez-users@lists.sourceforge.net
Subject: [Fez-users] Upgrading Fez and Fedora...

Hello all,

 

I’m new to this list (and to fez and fedora actually). I was recently tasked with migrating our old server running fedora 2.2 and fez (version, unknown, my best guess is it’s an svn export from roughly revision 1303).

 

I’m trying to move everything to a new server, and at the same time, upgrade fedora to 2.2.4 and fez to, well I guess svn trunk or release-2.1 from svn (which ever might be best). My problem is that I’m a bit lost as to how to upgrade without losing any of our data. Or does it even matter?

 

I get fedora up and running, and I can re-index the data, and I can poke around with the java gui and everything looks like it’s there, but fez just isn’t happy! If I try to do the upgrade process for fez, it fails with the error:

 

The upgrade failed (At upgrade '2008022700') - check error_handler.log.

 

If I ignore this, the site mostly works, but it can’t fetch stuff from fedora, and re-indexing fails. I’m just not really sure how to proceed. Is there a way to simply rebuild what’s in fez’s DB? Can I just start with a blank DB and then re-index or something?

 

Any tips or pointers would be of immense help!

 

Thanks,

Doug