I've successfully got indexing working without Zebra so now I'm trying to configure with Zebra. I think I have Zebra installed (placed in my own /shared/zebra directory) and I ran the rebuild_zebra.pl and got resulting files: ./var/lib/zebradb/biblios/register ./var/lib/zebradb/biblios/register/isambA-0.mf ./var/lib/zebradb/biblios/register/isambC-0.mf ./var/lib/zebradb/biblios/register/isambD-0.mf ./var/lib/zebradb/biblios/register/recdA-0.mf ./var/lib/zebradb/biblios/register/gmatch-0.mf ./var/lib/zebradb/biblios/register/isambB-0.mf ./var/lib/zebradb/biblios/register/dict-0.mf ./var/lib/zebradb/biblios/register/reci-0.mf And the zebrasrv starts and looks like it is running. But, with searches now using the Zebra indexes, I get an ERROR 109 from zebrasrv: 11:30:34-27/04 zebrasrv(4) [request] Search biblios ERROR 109 1 1+0 RPN @attrset Bib-1 @not @or @or @attr 1=1003 @attr 4=1 @attr 6=3 @attr 9=32 @attr 2=102 "twain, mark" @attr 1=1003 @attr 4=1 @attr 9=26 @attr 2=102 "twain, mark" @attr 1=1003 @attr 5=1 @attr 4=6 @attr 9=26 @attr 2=102 "twain, mark" @attr 1=9011 1 What is ERROR 109? How can I track down what might be still missing? Thanks, Tom -- ----------------------------------------------------------------------------- Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 Any idiot can face a crisis, it is this day-to-day living that wears you out. Anton Chekhov -----------------------------------------------------------------------------
Hey everyone. I'd just like to introduce myself. I'm a lab tech at University of Vermont and started getting interested in Koha as an equipment cage management solution around v2. It just works way better than anything else I've tried! Anyway, congrats to all those hard workers who got 3.4 out! I installed it last night on Ubuntu 10.04 with zero problems. One question, has anyone got Koha to work with Shibboleth? Many institutions (like mine) are sheathing their LDAP authentication behind a Shibboleth layer. I found a few notes about it on a Koha 4 ideas page on the internet but nothing else so far. All the best! Walker Blackwell
Walker, Since it sounds like some others have had trouble (for various reasons) either upgrading or installing in Ubuntu, could you follow-up with some specifics regarding just what kind of set up you had before, and what you did to install with zero problems -- as a guide to those following in your footsteps. That is, were you upgrading? From which version of Koha? Where did you get your 3.4 from? Did you follow any particular set of instructions? Which? And so on. Thanks (from an Ubuntu user at home, but not work) Kurt A. Bodling
-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha- bounces@lists.katipo.co.nz] On Behalf Of Walker Blackwell Sent: Wednesday, April 27, 2011 12:54 PM To: Koha listserv Subject: [Koha] Hello to all!
Hey everyone. I'd just like to introduce myself. I'm a lab tech at University of Vermont and started getting interested in Koha as an equipment cage management solution around v2. It just works way better than anything else I've tried!
Anyway, congrats to all those hard workers who got 3.4 out! I installed it last night on Ubuntu 10.04 with zero problems.
One question, has anyone got Koha to work with Shibboleth? Many institutions (like mine) are sheathing their LDAP authentication behind a Shibboleth layer. I found a few notes about it on a Koha 4 ideas page on the internet but nothing else so far.
All the best! Walker Blackwell
On Wed, Apr 27, 2011 at 2:00 PM, Kurt Bodling <kbodling@mountvernon.org> wrote:
Walker,
Since it sounds like some others have had trouble (for various reasons) either upgrading or installing in Ubuntu, could you follow-up with some specifics regarding just what kind of set up you had before, and what you did to install with zero problems -- as a guide to those following in your footsteps.
People are reporting problems using debian packages, stock install following INSTALL.ubuntu.lucid included in the source works like a charm here. Regards To+
Related to questions about installing 3.4. I installed mine on a fresh Ubuntu 10.04 64bit server. ---------------- 1. Started with a new VMware image of Ubuntu 10.04 AMD64bit with all security and other packages updated. 2. Installed Apache2, MYSQL5 and set up the mysql DBs. 3. Downloaded using Git and followed the instructions for a Ubuntu install. (including test DB, etc.) 4. Ran the install procedure and then used CPAN for all remaining uninstalled perl modules. No problems with the CPAN. Amazing! 5. Finished setting up the virtual domains in for apache/koha. 6. Rebooted, logged into the server from another computer (theipaddress:8080) and finished the setup. 7. Imported some marc records from my 3.2 export. (I might just dump mysql from my 3.2 db to my 3.4 db so I can retain item types. I don't know if this is possible.) (If I dump all my mysql tables from my old db and import into the new one, will 3.4 recognize that it is an old db and update it? I wish their was an "export database" button in the staff client.) ---------------- Today I'm getting koha to give staff access at https: and opac access at http: All the best, Walker
On 28 Apr 2011 05:34, "Walker Blackwell" <forums@walkerblackwell.com> wrote:
Related to questions about installing 3.4. I installed mine on a fresh
Ubuntu 10.04 64bit server.
----------------
1. Started with a new VMware image of Ubuntu 10.04 AMD64bit with all
security and other packages updated.
2. Installed Apache2, MYSQL5 and set up the mysql DBs.
3. Downloaded using Git and followed the instructions for a Ubuntu
install. (including test DB, etc.)
4. Ran the install procedure and then used CPAN for all remaining
uninstalled perl modules. No problems with the CPAN. Amazing!
5. Finished setting up the virtual domains in for apache/koha.
6. Rebooted, logged into the server from another computer
(theipaddress:8080) and finished the setup.
7. Imported some marc records from my 3.2 export. (I might just dump mysql
from my 3.2 db to my 3.4 db so I can retain item types. I don't know if this is possible.)
(If I dump all my mysql tables from my old db and import into the new one,
will 3.4 recognize that it is an old db and update it? I wish their was an "export database" button in the staff client.)
Yes, that will work, but read the UPGRADE section of the INSTALL file, after the webinstaller has done its thing, you will need to run a command to move all the item data of of the biblio data, then rebuild your zebra index. The commands are in that file. This is a major change between 3.2.x and 3.4.0, anyone upgrading needs to read that part of the INSTALL file. Chris
----------------
Today I'm getting koha to give staff access at https: and opac access at http:
All the best, Walker _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
On 28 Apr 2011 05:07, "Tomas Cohen Arazi" <tomascohen@gmail.com> wrote:
On Wed, Apr 27, 2011 at 2:00 PM, Kurt Bodling <kbodling@mountvernon.org>
wrote:
Walker,
Since it sounds like some others have had trouble (for various reasons) either upgrading or installing in Ubuntu, could you follow-up with some specifics regarding just what kind of set up you had before, and what you did to install with zero problems -- as a guide to those following in your footsteps.
People are reporting problems using debian packages, stock install following INSTALL.ubuntu.lucid included in the source works like a charm here.
Id be amazed if someone managed to install 3.4.0 from packages, since a package for it doesn't exist yet. So no I dont think its that :) The problems reported here are from people who didn't use the INSTALL file that comes with Koha. So I recommend using that, in this case (ubuntu) the INSTALL.ubuntu or INSTALL.ubuntu.lucid. And of course download.koha-community.org is where you should grab the tarball from. Basically if it hasnt come from a .koha-community.org site (either git or download) its not really Koha, thats where all official releases are from, accept no imitations :) Chris
Regards To+ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
The problems reported here are from people who didn't use the INSTALL file that comes with Koha. So I recommend using that, in this case (ubuntu) the INSTALL.ubuntu or INSTALL.ubuntu.lucid.
I used the INSTALL.ubuntu file from the git source. Worked well! All the best, Walker
Tom, Are you starting your zebrasrv per the INSTALL.<distro> file, with the correct options? For instance the INSTALL.debian one is something like: sudo -u <kohausername> -f <path_to_koha-conf.xml> You also want to have all of the zebra related directories owned by your koha user, and make sure you export the PERL5LIB and KOHA_CONF variables too. I had a hard time getting zebra working, and it was all related to file permissions. I don't have specifics for you there, I just remember I had to go back and make sure all the zebra related stuff had the koha user as owner. Best, Doug -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Tom Hanstra Sent: Wednesday, April 27, 2011 9:52 AM To: Koha listserv Subject: [Koha] Zebra errors I've successfully got indexing working without Zebra so now I'm trying to configure with Zebra. I think I have Zebra installed (placed in my own /shared/zebra directory) and I ran the rebuild_zebra.pl and got resulting files: ./var/lib/zebradb/biblios/register ./var/lib/zebradb/biblios/register/isambA-0.mf ./var/lib/zebradb/biblios/register/isambC-0.mf ./var/lib/zebradb/biblios/register/isambD-0.mf ./var/lib/zebradb/biblios/register/recdA-0.mf ./var/lib/zebradb/biblios/register/gmatch-0.mf ./var/lib/zebradb/biblios/register/isambB-0.mf ./var/lib/zebradb/biblios/register/dict-0.mf ./var/lib/zebradb/biblios/register/reci-0.mf And the zebrasrv starts and looks like it is running. But, with searches now using the Zebra indexes, I get an ERROR 109 from zebrasrv: 11:30:34-27/04 zebrasrv(4) [request] Search biblios ERROR 109 1 1+0 RPN @attrset Bib-1 @not @or @or @attr 1=1003 @attr 4=1 @attr 6=3 @attr 9=32 @attr 2=102 "twain, mark" @attr 1=1003 @attr 4=1 @attr 9=26 @attr 2=102 "twain, mark" @attr 1=1003 @attr 5=1 @attr 4=6 @attr 9=26 @attr 2=102 "twain, mark" @attr 1=9011 1 What is ERROR 109? How can I track down what might be still missing? Thanks, Tom -- ----------------------------------------------------------------------------- Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 Any idiot can face a crisis, it is this day-to-day living that wears you out. Anton Chekhov ----------------------------------------------------------------------------- _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
participants (6)
-
Chris Cormack -
Doug Dearden -
Kurt Bodling -
Tom Hanstra -
Tomas Cohen Arazi -
Walker Blackwell