Re: [Koha] Upgrade 3.01 to 3.6 on Diff Server
On Mon, Apr 2, 2012 at 6:34 PM, Josh Mikow joshmi...@gmail.com wrote: The koha-upgrade-to-3.4 command kept returning a bunch of Use of uninitialized value in pattern match (m//) at /usr/share/koha/lib/C4/Biblio.pm line 2953 messages. It's still running and I'm not sure if that is a problem or not. You may safely ignore those warnings. Before I had created brdglibrary I had tried creating a few other instances and now would like to remove them but the koha-remove doesn't work. It appears that when it tries to drop the mysql user, it fails because it doesn't pass the name of the instance properly to the DROP statement. Do you know how I can fix that to make the removal of an instance easier? I'm not sure about this. Someone more familiar with the packages will have to answer. Kind Regards, Chris (another one) ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Upgrade 3.01 to 3.6 on Diff Server
Hello, I'm new to Koha, library management and freshening up my Debian skills. Recently I was tasked with migrating our current Koha system to a new server. The prior admin is no longer around and I have been trying to understand how Koha works and get a good backup of the system (haven't had any to date). I think I have a backup of the database and all of the files/folders that specified in the koha-install-log file to use on the new server, but I want to get the update steps down so I know what to do before I try to upgrade/migrate our production system. On the new server I've done the following: * installed Debian 6. * installed Koha 3.06.04.000 * created a test instance to make sure it works on the localhost I'm having trouble with the koha-remove command. When I run it against my libtest instance, it returns with an Error 1396 about not being able to drop the user 'koha_--'@'%'. It appears that it is not using the instance name that I passed in within the DROP command. I've gone through and run all of the steps in the koha-remove manually and they work if I type the instance name for each of the commands. My biggest questions are: 1. What is the best way to make sure I backup all of the necessary files on the 3.01 system so that I can successfully get them over to the 3.06 system to restore? 2. What is the best way to properly restore the 3.01 files under the 3.06 install without causing future problems? 3. What steps do I need to do to upgrade the 3.01 to the 3.06 system? 4. Currently the system is working on localhost but we will need to get it working on our internet site. What configuration changes are needed to work both internally and externally? Any assistance you can provide as I begin to learn Koha and library management is greatly appreciated. Thank you for your time. Josh Mikow Volunteer IT Admin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade 3.01 to 3.6 on Diff Server
On 3 April 2012 08:52, Josh Mikow joshmi...@gmail.com wrote: Hello, My biggest questions are: 1. What is the best way to make sure I backup all of the necessary files on the 3.01 system so that I can successfully get them over to the 3.06 system to restore? Unless you have done some local customisation by editing the perl scripts or templates. All you need is the database itself. So a database dump of that. 2. What is the best way to properly restore the 3.01 files under the 3.06 install without causing future problems? You don't want to do that :) You will cause problems. What you want to do is import your 3.1.x database into your 3.6.4 instance, then run koha-upgrade-schema instancename then koha-uprade-to-3.4 instancename What this second one does is remove the item data from the marcxml blob in biblioitems. This was changed in 3.4.0 hence the name, since you are going from 3.1.x to 3.6.4 you need this to be done. It will then start a zebra reindex. After that you will be up on 3.6.4 .. the next thing to do would be to work through all the settings and check they are ok (circulation rules, systempreferences etc). Get the librarians to test. If its all ok, do this again and call it live :) 3. What steps do I need to do to upgrade the 3.01 to the 3.06 system? See above :) 4. Currently the system is working on localhost but we will need to get it working on our internet site. What configuration changes are needed to work both internally and externally? You will need to play with the apache config file in sites-enabled to get the virtual host listening on the names/numbers you want it too. Hope this helps Chris ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade 3.01 to 3.6 on Diff Server
Thanks Chris! I don't believe any customizations to the .pl files would have been done. Is there a way to determine that? I have a database dump from 3.1.0 restored on the 3.6.4 box. That's all I've done so far. I also have a copy of all the files in all the folders, but I haven't done anything with them yet. The instance on the 3.1.0 is called biblioteka. I restored the database of the same name on the 3.6.4 server. I tried running a koha-upgrade-schema biblioteka but it returned an error like it can't find the koha-conf.xml file. Should I restore the /etc/koha/ folder to /etc/koha/sites/biblioteka? Is that what you referred to as an import? I think on the old server it was installed as a single instance but on the new server I'd like to have a test instance available if we want to try things out first. Thanks again for the help! Josh On Mon, Apr 2, 2012 at 2:35 PM, Chris Cormack ch...@bigballofwax.co.nzwrote: On 3 April 2012 08:52, Josh Mikow joshmi...@gmail.com wrote: Hello, My biggest questions are: 1. What is the best way to make sure I backup all of the necessary files on the 3.01 system so that I can successfully get them over to the 3.06 system to restore? Unless you have done some local customisation by editing the perl scripts or templates. All you need is the database itself. So a database dump of that. 2. What is the best way to properly restore the 3.01 files under the 3.06 install without causing future problems? You don't want to do that :) You will cause problems. What you want to do is import your 3.1.x database into your 3.6.4 instance, then run koha-upgrade-schema instancename then koha-uprade-to-3.4 instancename What this second one does is remove the item data from the marcxml blob in biblioitems. This was changed in 3.4.0 hence the name, since you are going from 3.1.x to 3.6.4 you need this to be done. It will then start a zebra reindex. After that you will be up on 3.6.4 .. the next thing to do would be to work through all the settings and check they are ok (circulation rules, systempreferences etc). Get the librarians to test. If its all ok, do this again and call it live :) 3. What steps do I need to do to upgrade the 3.01 to the 3.06 system? See above :) 4. Currently the system is working on localhost but we will need to get it working on our internet site. What configuration changes are needed to work both internally and externally? You will need to play with the apache config file in sites-enabled to get the virtual host listening on the names/numbers you want it too. Hope this helps Chris ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade 3.01 to 3.6 on Diff Server
On 3 April 2012 11:12, Josh Mikow joshmi...@gmail.com wrote: Thanks Chris! I don't believe any customizations to the .pl files would have been done. Is there a way to determine that? I have a database dump from 3.1.0 restored on the 3.6.4 box. That's all I've done so far. I also have a copy of all the files in all the folders, but I haven't done anything with them yet. The instance on the 3.1.0 is called biblioteka. I restored the database of the same name on the 3.6.4 server. I tried running a koha-upgrade-schema biblioteka but it returned an error like it can't find the koha-conf.xml file. Should I restore the /etc/koha/ folder to /etc/koha/sites/biblioteka? Is that what you referred to as an import? I think on the old server it was installed as a single instance but on the new server I'd like to have a test instance available if we want to try things out first. You will have to have done a koha-create biblioteka on the new one then you can do koha-mysql biblioteka name_of_your_dump.sql Then run the other commands Chris Thanks again for the help! Josh On Mon, Apr 2, 2012 at 2:35 PM, Chris Cormack ch...@bigballofwax.co.nz wrote: On 3 April 2012 08:52, Josh Mikow joshmi...@gmail.com wrote: Hello, My biggest questions are: 1. What is the best way to make sure I backup all of the necessary files on the 3.01 system so that I can successfully get them over to the 3.06 system to restore? Unless you have done some local customisation by editing the perl scripts or templates. All you need is the database itself. So a database dump of that. 2. What is the best way to properly restore the 3.01 files under the 3.06 install without causing future problems? You don't want to do that :) You will cause problems. What you want to do is import your 3.1.x database into your 3.6.4 instance, then run koha-upgrade-schema instancename then koha-uprade-to-3.4 instancename What this second one does is remove the item data from the marcxml blob in biblioitems. This was changed in 3.4.0 hence the name, since you are going from 3.1.x to 3.6.4 you need this to be done. It will then start a zebra reindex. After that you will be up on 3.6.4 .. the next thing to do would be to work through all the settings and check they are ok (circulation rules, systempreferences etc). Get the librarians to test. If its all ok, do this again and call it live :) 3. What steps do I need to do to upgrade the 3.01 to the 3.06 system? See above :) 4. Currently the system is working on localhost but we will need to get it working on our internet site. What configuration changes are needed to work both internally and externally? You will need to play with the apache config file in sites-enabled to get the virtual host listening on the names/numbers you want it too. Hope this helps Chris ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
