Path to upgrade from 3.2 installed with deb packages to 3.8
Hi all, We have a production machine that we installed on ubuntu 10.10 quite a while ago using debian packages. We got it working good enough for our purposes at the time and just let it be (because of no time to work on it more). Now we have a volunteer computer engineer helping us for several weeks and he has updated the OS to Ubuntu 12.04 and we are working on the next step of upgrading Koha to the latest 3.8 version. We have made several attempts and haven't been able to figure out how to get it done and keep rolling back. One of the main issues we have is that the original machine was installed using the koha package (not Koha-common). But the recommendation is to use Koha-common on the newer versions. So we need to know how to get apache set up for multiple virtual sites and OPAC and Intraet. Any recommendation on the proper upgrade path to do this would be helpful. We have already tried just building anew machine and importing a SQL dump, but while all the data showed up, there were numerous errors with schema structure. Any recommendation on the proper upgrade path to do this would be helpful. Thanks, Brad Gabbert IT Director International School of Wuxi
Brad Gabbert schreef op wo 17-10-2012 om 08:41 [+0800]:
We have already tried just building anew machine and importing a SQL dump, but while all the data showed up, there were numerous errors with schema structure.
This would be my approach if you're deleting/rebuilding everything anyway. What do you mean by errors with the schema? In general, you should get the instance set up, load in the data dump, run koha-upgrade-to-3.4, then run koha-upgrade-schema (or do it through the web interface.) It's not unexpected for there to be a lot of errors during this process, they're typically reporting that it's trying to do something that's already been done. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
Robin wrote:
In general, you should get the instance set up, load in the data dump, run koha-upgrade-to-3.4, then run koha-upgrade-schema (or do it through the web interface.)
Is there an advantage in doing it that way, rather than editing the package configuration file to load the data dump as the instance is set up, then commenting the data dump line out again? I expect both work, yes. And most of the errors are attempts to repeat things already done - the schema upgrade scripts are rather conservative, to cope with people who upgrade in, errrr, "unexpected" ways, shall we say? Usually work, too. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
MJ Ray schreef op do 18-10-2012 om 10:17 [+0100]:
Is there an advantage in doing it that way, rather than editing the package configuration file to load the data dump as the instance is set up, then commenting the data dump line out again?
Both should work just fine. There is the issue (or feature) that the password of user id 1 (by default) will be reset to a random value if you use the config file/--defaultsql to load a dump as it's really intended to be a template. Also, loading a dump is really easier: zcat library-2012-10-19.sql.gz | sudo koha-mysql library then just wait a while. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
participants (3)
-
Brad Gabbert -
MJ Ray -
Robin Sheat