Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/19/23 16:54, Hector Gonzalez Jaime wrote: You are still missing /usr/sbin in your PATH variable. That's been added. It mighty not have been added permanently. to verify what is on your path, you can type: echo $PATH Aha! It wasn't. I've put it back again, but results of that have already been posted with a new stop point. You didn't get to a new stop point, start-stop-daemon is at /sbin which was NOT on your path, you need to add that and run koha-plack --start library again so we see what happens. /sbin is in my path. When I run: root@store:/usr/sbin# koha-plack --start library [FAIL] Error: Plack already running for library: failed! Which is what I call a stop point, as Koha is still not up. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/19/23 15:19, Hector Gonzalez Jaime wrote: What does sudo koha-plack --start instancename Do? root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found Which seems even more weird. Are the permissions wrong? You are still missing /usr/sbin in your PATH variable. That's been added. It mighty not have been added permanently. to verify what is on your path, you can type: echo $PATH Aha! It wasn't. I've put it back again, but results of that have already been posted with a new stop point. if it is missing any of the directories, add it with: PATH=/sbin:/usr/sbin:$PATH, followed by export PATH it might be part of .bashrc, but if you are editing root's one, you might want to check your regular user's .bashrc first. Okay, you lost me here. I'm not aware of .bashrc, so am not aware if I am, or should be, editing it. Thanks again for trying. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/18/23 21:35, Hector Gonzalez Jaime wrote:
What does sudo koha-plack --start instancename Do?
root@store:/usr/sbin# koha-plack --start library bash: koha-plack:
command not found
Which seems even more weird. Are the permissions wrong?
You are still missing /usr/sbin in your PATH variable.
That's been added.
The command would have run if you had typed:
/usr/sbin/koha-plack --start library
Let me try:
root@store:/usr/sbin# /usr/sbin/koha-plack --start library
/usr/share/koha/bin/koha-functions.sh: line 285: start-stop-daemon:
command not found
[ ok ] Starting Plack daemon for library:.
Okay, a step forward, but a new challenge. (Been a lot of that in this
project!)
Line 285 is:
if start-stop-daemon --pidfile "/var/run/koha/${instancename}/plack.pid" \
File /var/run/koha/library/plack.pid does exist. It contains a
five-digit number only.
Okay, I'm stuck again!
Thanks again for all the help.
Regards,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
your system seems to be in a strange situation, you might want to
uninstall koha, remove all dependencies, and install it again:
apt-get remove koha-common <- this does not affect your database
or configuration files. apt-get autoremove <- this
deletes every dependency that is no longer needed, which should be a
ton of perl libraries. apt-get install koha-common <- this
should reinstall koha, and every one of its dependencies. If your
system has problems, this command would eventually fail.
If this last command fails, I'd like to see the contents of your
/etc/apt/sources.list file and every file at /etc/apt/sources.list.d
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan
Library ___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz Unsubscribe:
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/18/23 17:35, Chris Cormack wrote: What does sudo koha-plack --start instancename Do? root@store:/home/bruce# koha-plack --start library bash: koha-plack: command not found Which I thought was pretty odd, so I went to the /usr/sbin directory, and: root@store:/usr/sbin# ls -l koha-p* -rwxr-xr-x 1 root root 13538 May 13 23:26 koha-plack then root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found Which seems even more weird. Are the permissions wrong? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/18/23 16:51, Chris Cormack wrote: Ok, so I think now you can try seeing if you have the koha commands back does sudo koha-list work and list your instance? Yes and yes. If so, you might want to run a koha-dump... Done. Seems to have worked. ... then try restarting all the Koha services Okay, not sure how to do this, so I just rebooted the server. The other services came back up, but not Koha. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/18/23 15:53, Chris Cormack wrote: Hi Bruce I Chris. I remember meeting you in Reno! We've found the problem. root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is the issue right here, koha-common can't be installed cleanly because a package it depends on is missing. What does sudo apt install libtest-dbix-class-perl Result in? root@store:/etc/koha# apt install libtest-dbix-class-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libtest-dbix-class-perl : Depends: libdata-uuid-perl (>= 1.215) E: Unable to correct problems, you have held broken packages So, I did: root@store:/etc/koha# apt install libdata-uuid-perl Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libossp-uuid16 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: libossp-uuid-perl libsoap-lite-perl libxmlrpc-lite-perl The following NEW packages will be installed: libdata-uuid-perl 0 upgraded, 1 newly installed, 3 to remove and 1 not upgraded. Need to get 24.8 kB of archives. After this operation, 833 kB disk space will be freed. etc. Now when I do: root@store:/etc/koha# apt install libtest-dbix-class-perl It all seems to run correctly. And when I enter: root@store:/etc/koha# apt install koha-common That too seems to run correctly. But still no love for the OPAC or admin interface. Feels like good progress though. What next? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/18/23 15:52, Hector Gonzalez Jaime wrote: On 5/18/23 13:46, Bruce A. Metcalf wrote: On 5/18/23 14:52, David Liddle wrote: 2.a. Path. What is the result of this command? env | grep -i 'path' root@store:/# env | grep -i 'path' PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games I am aware that the path should contain several sbin directories, but I don't know how to add them. with these commands: PATH=/sbin:/usr/sbin:$PATH export PATH Okay, that seems to have worked. Still no love from apt-get install --reinstall koha-common though. 3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"? Yes. The resultant is: root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. This unchanged after the PATH correction. You should try: apt-get dist-upgrade which would install the missing dependencies. This seems hopeful: root@store:/etc/koha# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libmoosex-types-perl libsub-exporter-formethods-perl The following packages have been kept back: koha-common The following packages will be upgraded: koha python-ipaddress 2 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. ... etc. I am concerned by the koha-common being kept back though. Also apt-get -f install should fix that too. No change from that. ... and still no OPAC or admin access. Curiously: root@store:/etc/koha# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libossp-uuid-perl : Conflicts: libdata-uuid-perl E: Broken packages Suggestions? Thanks all for the continuing effort. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/18/23 14:52, David Liddle wrote: Hello, Bruce. You've been good about chasing down the information folks have asked for. I'm sorry that we haven't brought you closer to a solution. I'm no less appreciative of your efforts for that. I have some follow-up questions: 1.a. Database. Once you listed the databases, did you exit the mysql prompt and back up the koha_library database with the mysqldump command? Yes, and it appeared to work. I have a 450MB file called backup.sql. 1.b.Can you use an FTP client such as FileZilla to download such files? I assume so. 2.a. Path. What is the result of this command? env | grep -i 'path' root@store:/# env | grep -i 'path' PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games I am aware that the path should contain several sbin directories, but I don't know how to add them. 2.b. Path. Did you already establish that the Koha commands are or are not installed? ls /usr/sbin/koha* Yes, the usual list of commands is there. This suggests to me that the inadequate PATH command is at least part of my problem. 3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"? Yes. The resultant is: root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. The current version is 21.11.20. Right, but I haven't been able to employ any earlier version, either. Yes, koha-common appears to be running, though maybe I'm reading it wrong. Have you checked the Apache config file for your instance, probably /etc/apache2/sites-available/library.conf There are two links in that file, one for the OPAC and one for admin access. SSL Certificate information will be important. There is no mention of SSL Certificates in the file. There are also Apache-related config files in /etc/koha, which I think could have been overwritten in the upgrade; that may or may not be important. There are such files. I don't know what to make of them. 5. This situation is a good opportunity to research and document the elements on the server that you need to back up manually and download in the event that you need to rebuild the server from scratch. I'm guessing you don't do this work full-time, but having this information written will save you and/or your successor a lot of time when that day comes. Yeah, I should be so lucky as to have someone take over for me! The organization is a non-profit with declining participation. Is this hosted server just running: 1. the main website (what platform or site-building tool?), 2. a wiki (MediaWiki?), and 3. Koha? That backup will probably come down to the databases you've listed and one or more directories for each service. The virtual server is running an Online Store, a Wiki, and Koha. Minor file storage is all else that's there. What I suspect at this point is that I need to add the sbin directories to the PATH. Can someone point me to a tutorial? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/16/23 15:31, Hector Gonzalez Jaime wrote: Can I buy a clue about how to run mysqldump? you can make a backup wich mysqldump like this: mysqldump -u root -p --all-databases > backup.sql you can reinstall koha-common by issuing this command: sudo apt-get install --reinstall koha-common Aha! Here's a failure: root@store:/home/bruce# apt-get install --reinstall koha-common Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 42.7 MB of archives. After this operation, 0 B of additional disk space will be used. Err:1 http://debian.koha-community.org/koha oldoldstable/main i386 koha-common all 21.11.19-1 404 Not Found [IP: 67.220.127.145 80] E: Failed to fetch http://debian.koha-community.org/koha/pool/main/k/koha/koha-common_21.11.19-1_all.deb 404 Not Found [IP: 67.220.127.145 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? This makes it look like the oldoldstable repository is broken? Have you tried to backup your koha instance with "koha_dump" ? This command is missing. Thanks again for the ideas. Any clue about the failure above could be crucial. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/16/23 15:29, David Liddle wrote: Yet another command that may shed some light on the status of your installation: ~# systemctl status koha-common root@store:/etc/koha# systemctl status koha-common ● koha-common.service - LSB: Start required services for each Koha instance Loaded: loaded (/etc/init.d/koha-common; generated) Active: active (running) since Sun 2023-05-14 12:45:09 EDT; 3 days ago Docs: man:systemd-sysv-generator(8) Process: 2082 ExecStart=/etc/init.d/koha-common start (code=exited, status=0/SUCCESS) Tasks: 6 (limit: 4915) Memory: 172.2M CGroup: /system.slice/koha-common.service ├─2408 daemon --name=library-koha-zebra --pidfiles=/var/run/koha/library/ --errlog=/var/log/koha/library/zebra-error.log --output=/var/log/koha/library/zebra- ├─2410 /usr/bin/zebrasrv -v none,fatal,warn -k 1024 -f /etc/koha/sites/library/koha-conf.xml ├─2658 daemon --name=library-koha-worker --errlog=/var/log/koha/library/worker-error.log --stdout=/var/log/koha/library/worker.log --output=/var/log/koha/libr ├─2659 /usr/bin/perl /usr/share/koha/bin/background_jobs_worker.pl ├─2698 daemon --name=library-koha-indexer --errlog=/var/log/koha/library/indexer-error.log --output=/var/log/koha/library/indexer-output.log --pidfiles=/var/r └─2699 /usr/bin/perl /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 19 Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. So, it looks like Koha is running, but it's not responding to calls from Apache? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/16/23 15:10, David Liddle wrote: Bruce, here are some more suggestions: 1. When it comes to the logs, perhaps a command such as these (and similar) will reveal when and how something went wrong: grep -inr --include \*.log 'koha-common' /var/log/ Results: Binary file /var/log/daemon.log matches zgrep -in 'koha-common' /var/log/dpkg.log* This results in many lines like: /var/log/dpkg.log.10.gz:161:2022-04-29 13:51:36 status unpacked koha-common:all 21.05.14-1 And a few like: /var/log/dpkg.log.10.gz:161:2022-04-29 13:51:36 status unpacked koha-common:all 21.05.14-1 /var/log/dpkg.log.1:20:2023-04-12 23:07:03 status half-configured koha-common:all 21.11.17-1 /var/log/dpkg.log.1:22:2023-04-12 23:07:04 status half-installed koha-common:all 21.11.17-1 Needless to say, I have no idea what these messages mean or how to fix them. 2. You should double-check that your installation source file is correct, as covered by https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources. For example, mine shows after the following command: ~# cat /etc/apt/sources.list.d/koha.list deb [signed-by=/usr/share/keyrings/koha-keyring.gpg] > https://debian.koha-community.org/koha 22.05 main Mine is: deb http://debian.koha-community.org/koha oldoldstable main 3. If APT seems to be working, then you could install 'debsums' (apt install debsums) and see what it reveals with this command: debsums --all --silent # /etc/koha# debsums --all --silent debsums: changed file /etc/koha/zebradb/etc/default.idx (from koha-common package) debsums: changed file /etc/cron.d/koha-common (from koha-common package) debsums: changed file /etc/koha/zebradb/lang_defs/en/sort-string-utf.chr (from koha-common package) debsums: changed file /etc/default/koha-common (from koha-common package) debsums: changed file /etc/koha/zebradb/etc/word-phrase-utf.chr (from koha-common package) debsums: changed file /etc/koha/koha-sites.conf (from koha-common package) debsums: changed file /etc/cron.daily/mlocate (from mlocate package) plus some unrelated lines of that ilk. dpkg --verify koha-common root@store:/etc/koha# dpkg --verify koha-common ??5?? c /etc/cron.d/koha-common ??5?? c /etc/default/koha-common ??5?? c /etc/koha/apache-shared-opac.conf ??5?? c /etc/koha/koha-sites.conf ??5?? c /etc/koha/zebradb/etc/default.idx ??5?? c /etc/koha/zebradb/etc/word-phrase-utf.chr ??5?? c /etc/koha/zebradb/lang_defs/en/sort-string-utf.chr dpkg --audit koha-common This generates no response. Those are going to look for errors in packages and list the configuration files that have been altered from their default. It listed nicely the files that I already knew I changed for both Koha and Apache. 4. You may want to try the following commands, too: apt --fix-broken install apt --fix-missing install Both result in no actions. 5. If the Koha installation is incomplete, despite what the system seems to report, then you may want to use 'dpkg' to remove 'koha-common' and then reinstall with 'apt' according to the instructions. dpkg --remove koha-common root@store:/etc/koha# dpkg --remove koha-common dpkg: warning: 'ldconfig' not found in PATH or not executable dpkg: warning: 'start-stop-daemon' not found in PATH or not executable dpkg: error: 2 expected programs not found in PATH or not executable Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin Aha! my $PATH contains no mention of any sbin directory. Let me see if I can add it. Hmm. My ~/.bashrc file is effectively empty, with all lines commented out. It also looks "wrong". 6. When it comes to listing the databases, here's what you might expect to see: ~# mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 348 Server version: 10.5.19-MariaDB-0+deb11u2 Debian 11 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; ++ | Database | ++ | information_schema | | koha_library | | mysql | | performance_schema | ++ 4 rows in set (0.000 sec) MariaDB [(none)]> quit Bye This generates: ++ | Database | ++ | aug_wiki | | augustan | | information_schema | | koha_library | | mysql | | performance_schema | ++ The instance name is "library", so that's the 4th entry. "aug_wiki" is from our wiki installation, not sure what "augustan" is. So, we have some new data, but nothing that shows me what needs to be done. I hope someone here can tell me what it is. Regards, / Bruce /
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/16/23 12:31, David Liddle wrote: What are the results of the following commands? Clearly your installation is incomplete. dpkg -l koha-common root@store:/var/lib/mysql# dpkg -l koha-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii koha-common21.11.19-1 all integrated (physical) library management system dpkg -s koha-common root@store:/var/lib/mysql# dpkg -s koha-common Package: koha-common Status: install ok installed Priority: optional Section: web Installed-Size: 574598 Maintainer: Mason James Architecture: all Source: koha Version: 21.11.19-1 Depends: ... [many lines deleted] They are similar, in that the first is a summary and the second is more detailed. For example, one of my systems shows the following with the first: ~# dpkg -l koha-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== hi koha-common22.05.12-1 all integrated (physical) library management system Which is a pretty fair match. Not at all sure what the latter is supposed to show me. (Full dump on request.) And the same system shows this with apt: ~# apt policy koha-common koha-common: Installed: 22.05.12-1 Candidate: 22.05.12-1 Version table: *** 22.05.12-1 500 500 http://debian.koha-community.org/koha 22.05/main amd64 Packages 100 /var/lib/dpkg/status root@store:/var/lib/mysql# apt policy koha-common koha-common: Installed: 21.11.19-1 Candidate: 21.11.19-1 Version table: *** 21.11.19-1 500 500 http://debian.koha-community.org/koha oldoldstable/main i386 Packages 100 /var/lib/dpkg/status Again, pretty much a match. So if these responses are good, where is my problem lurking? In case you need the commands for grabbing your database: ~# mysql -uroot -p show databases; Mine shows: root@store:/var/lib/mysql# mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 18971 Server version: 10.3.38-MariaDB-0+deb10u1 Debian 10 (take note of KOHA_DB in the table) No table there to take note of. ~# mysqldump --databases KOHA_DB > koha_db_dump.sql This command gives me "access denied" for both root and myself. If your other configuration files – most of which are in /etc/koha/ and /var/lib/koha/ – are missing, you may be able to copy them from within the full-drive backup. Buncha stuff in both directories. Not sure if they're complete or not. Some formats are easier to mount and browse than others. What do you use? I use the automatic backup run by my virtual machine service. It restores just fine, but don't know if it can do file-by-file restores. Thanks for your continuing efforts, glad to test and post other items. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/15/23 16:41, Galen Charlton wrote: 3. Can I install a new instance in the same virtual machine and transfer the settings and data? Almost everything worth permanently keeping in a typical Koha system is stored in the database. Is MySQL/MariaDB running and can you get a mysqldump? I'm not sure. How can one tell? There is a MySQL instance running, but I suspect that may be for one of the other servers. There is no MariaDB running, which I recall having switched to some time back. Can I buy a clue about how to run mysqldump? If not, are there at least database files present in /var/lib/mysql? If /var/lib/mysql/ibdata1 is the right file, then yes. It's almost a GB in size, which seems reasonable for the library's data. A current copy of the database could be imported into a fresh install of Koha (either in a new VM or after a wipe and recreation of the existing one - though if you do a wipe, triple-check that your database export is good!). Right. Tried to delete Koha and reinstall, but there was no change in the resultant. Wiping the whole VM is impractical due to the other servers on it, though that may prove necessary. I continue to suspect that the problem lies with the upgrades from Debian 9 to 10 and Koha 21.05 to 21.11. Something didn't upgrade correctly, or there's a hidden incompatibility, that's stopping work. Thanks for the ideas. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/15/23 16:35, David Liddle wrote: Bruce, it’s an intriguing problem But I do have some more questions: - What other services are running on that server? Are they all still working correctly? There is another Apache server and a MediaWiki server (which may also run under Apache). Both are working as before with no problems or noticeable slowdowns. - What clues are there in the logs in /var/log/? The only logs with any entries are access logs which show that the Chinese and Eastern Europeans are trying to hack the system. I don't think those are relevant. What may be relevant is that TOP does not show that Koha is running, though this could be just that the command isn't obvious. - Is the apt installer working generally, or do you perhaps have a broken Debian installation? Can you update or install other packages successfully? The apt installer appears to be working, but it is not updating Koha apps, and there have been several updates since this began. The repository link appears to be correct; I'm (trying to run) on "oldoldstable". - Can you access the database server to do a manual dump of the Koha database? Not using any Koha tools or commands. I might be able to do so manually, but am clueless about how to do so. Thanks for your continuing efforts. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/15/23 12:12, David Liddle wrote:
I see now that I overlooked your statement that commands such as
'koha-dump' are not recognized. Do they appear in the directory
/usr/sbin/?
No. Not a single koha- command present in that directory.
Do you have automated Koha backups configured that are available in
/var/spool/koha/{instance}?
No, though that would have been smart of me. I don't even have a
directory /var/spool/koha, much less /var/spool/koha/instance.
Appreciate the effort.
Respectfully,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Fwd: Dead Koha Resuscitation
Greetings, I have a problem with a dead Koha instance than I cannot resolve: I had Koha 21.05 installed on Debian 9 with packages. Previous updates to both had worked fine. I recently tried to update to 21.11 and Debian 10 (with packages). I did both at once because both were at end-of-life and 21.11 needs Deb 10 or better anyway. The virtual machine came back up fine, as did other apps on the machine (including other Apache servers). Koha, however, did not come back up. I tried a variety of ways to start and restart, without any response (i.e.: not even an error message). The logs don't offer any intelligible data (which may be my fault). I am also unable to locate commands like koha-create, koha-enable, koha-dump, koha-list, etc., getting a "command not found" error. I tried apt remove koha-common / apt install koha-common without a change in symptoms. Any suggestions about what to try next would be most appreciated. 1. Is there something undocumented that is needed for such an upgrade? 3. Can I install a new instance in the same virtual machine and transfer the settings and data? 4. Any other suggestions that don't involve firearms? Thanks for whatever suggestions you may have to share. Cheers, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
On 3/15/23 23:44, Mason James wrote: On 15/03/23 11:22 am, Bruce A. Metcalf wrote: On 3/14/23 01:05, Mason James wrote: On 14/03/23 5:53 pm, Mason James wrote: On 13/03/23 5:13 am, Bruce A. Metcalf wrote: On 3/12/23 10:34, Katrin Fischer wrote: There is a log3perl.conf file in my /etc/koha/sites/(instance)/ directory, and it looks just like the one suggested. did you restart koha? - specifically after you upgraded? /etc/init.d/koha-common restart No change. did the following error stop? AH01215: Configuration not defined at /usr/share/perl5/Log/Log4perl/Config.pm line 579.: /usr/share/koha/intranet/cgi-bin/mainpage.pl I don't see that error. Line 579 of the first file is: die "Configuration not defined" unless defined $config; Two lines earlier, I see: my($config) = @_; Which suggests to me that something is missing, but I don't know the language so can't tell what. do you have new errors in your log files? The only error I see in the logs right now is: root@store:/var/log/koha/library# tail worker-output.log Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 26. Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 26. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/background_jobs_worker.pl line 28. Which doesn't mean anything to me, and without a date stamp, I'm not even sure when it showed up. At least this feels like we're getting close. Thanks all, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
On 3/14/23 01:05, Mason James wrote: On 14/03/23 5:53 pm, Mason James wrote: On 13/03/23 5:13 am, Bruce A. Metcalf wrote: On 3/12/23 10:34, Katrin Fischer wrote: To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results in [Internal Server Error] screens. the short version is that your koha instance is probably missing a log4perl.conf file a simple way to correct the problem would be to create a new instance, then copy the missing log4perl.conf file from the new instance I'll check to see if I have room for this. here is an example of a log4perl.conf file - please search/replace it, as required :) # cat /etc/koha/sites/tp3/log4perl.conf I had to create the tp3 directory to do this. Now the system reports two instances, my original and tp3. Does this sound wrong? There is a log3perl.conf file in my /etc/koha/sites/(instance)/ directory, and it looks just like the one suggested. Perhaps it's something else. Any other ideas? Cheers, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
On 3/12/23 10:34, Katrin Fischer wrote: the internal server error will resolve to something more meaningful in the logs. Check your logs on the server for the full error message. I've looked at the tail of all logs in /var/log/koha/(instance)/, but most are empty and the others don't give me any meaning. One example, intranet-error.log gives: [Sun Mar 12 09:18:00.882412 2023] [cgi:error] [pid 25446] [client 185.224.128.17:41784] AH01215: Configuration not defined at /usr/share/perl5/Log/Log4perl/Config.pm line 579.: /usr/share/koha/intranet/cgi-bin/mainpage.pl I've viewed both files listed, but not being a programmer, I can't see what might be wrong with them. To review, an upgrade to 21.11 (OldOldStable) and Debian 10 results in [Internal Server Error] screens. TIA, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
Hi gang Back again after a forced suspension of work. I am trying to upgrade from Koha 21.05 on Debian 9 to 21.11 (OldOldStable) on Debian 10. The upgrade appears to go through, but both public and staff interface display [Internal Server Error]. System was working fine on 21.05/9, and all but Koha work under Debian 10. All suggestions will be appreciated. Cheers, / Bruce / Bruce A. Metcalf, Librarian Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Another DBI Exception for foreign key constraint in upgrade to Koha
Hi Pablo, Both bugs are resolved, but I'm having this issue while upgrading today from 20.05 to 22.05 on a Debian 9.13: It's my understanding that 22.05 requires Debian 10 or 11, per <https://wiki.koha-community.org/wiki/System_requirements_and_recommendations>. (Don't ask me how I learned this!) Respectfully, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
Jonathan Druart wrote: > Yes, definitely, it must be owned by the $INSTANCE-koha user PETRIDIS wrote: Just checked my system’s files and log4perl.conf is indeed owned by root, however has rw set for all. FWIW, in order to get back to work, I restored from backup and found: -rw-r--r-- 1 root root 2134 Dec 19 2020 /etc/koha/sites/library/log4perl.conf Which works properly. I also discovered that 21.11 needs Debian 10 or 11, and I'm still on Debian 9, so my bad. After the next system backup, I'll try to upgrade Debian to 10, followed by an upgrade of Koha to 21.11. No news is good news. Thanks to all for the suggestions. Regards, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
On 11/28/22 16:52, Jonathan Druart wrote: Did you upgrade using the debian packages? Yes; always. The error is saying you don't have the log4perl config file, which needs to be at /etc/koha/sites/$INSTANCE/log4perl.conf This file exists, but I note that it's owned by "root", and not "instance-koha". Could this be the issue? Regards, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Upgrade to 21.11 Fails
On 11/28/22 15:07, Jonathan Druart wrote: Did you restart koha-common? Yes, I rebooted the whole virtual machine. No change. Do you have an error in the Koha logs? intranet-error.log [Mon Nov 28 09:30:06.112562 2022] [cgi:error] [pid 13388] [client ... ] AH01215: Configuration not defined at /usr/share/perl5/Log/Log4perl/Config.pm line 579.: /usr/share/koha/opac/cgi-bin/opac/errors/500.pl [Mon Nov 28 09:30:06.148729 2022] [cgi:error] [pid 13388] [client ... ] End of script output before headers: 500.pl Doesen't give me a clue. Anyone else? Thanks, / Bruce / Bruce A. Metcalf Augustan Library Yes, I'm slow on the uptake, I've been running oldoldstable for some time now. With the release of 22.11, it's time for me to move up. My system was installed from deb packages under Debian 10, and has been updating fine. After an update (with no error messages), I find I am unable to access either the OPAC or the admin interfaces. Both give an "Internal Server Error" message, with a note that a 500 error was thrown by the ErrorDocument handler as well. Probably something simple, but not something I can see or find in the release notes. Help! ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Upgrade to 21.11 Fails
Greetings, Yes, I'm slow on the uptake, I've been running oldoldstable for some time now. With the release of 22.11, it's time for me to move up. My system was installed from deb packages under Debian 10, and has been updating fine. After an update (with no error messages), I find I am unable to access either the OPAC or the admin interfaces. Both give an "Internal Server Error" message, with a note that a 500 error was thrown by the ErrorDocument handler as well. Probably something simple, but not something I can see or find in the release notes. Help! Regards, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Does Koha support barcode scanners and more questions?
On 6/2/22 02:48, Karthick Babu Sai Sankar Gupta wrote: 1) Could this software be installed in a webspace and used or should this be in a standalone (local) computer ? Yes. I've been running Koha in a virtual server at a remote site since version 3. If you do want to host it locally, I would recommend a single-purpose computer, so it isn't slowed by other programs. Some functions are a bit of a resource hog, though this is usually temporary. I also recommend using Debian, not a derivative like Mint. It's possible to run it under different OS, but it's much simpler with pure Debian. I'll have to leave the other questions to those with more knowledge in those topics. Cheers, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Very, very beginner question: Followup
On 5/18/22 15:41, Caroline Cyr La Rose wrote: As for which servers to add, I wouldn't really know. Maybe university libraries since the texts you seem to catalog seem very specialized. I select new servers by first looking up items in WorldCat <https://www.worldcat.org/> to see who holds it. I then look up Z39.50 servers in IRSpy <http://irspy.indexdata.com> to see if any of the holding libraries have open Z39.50 servers, and add them to my list. Note that IRSpy lists Connection Reliability. Those showing 0% reliability are either closed, private, or dead, so don't bother with them. If anyone else has a useful list of Z39.50 servers, I'd appreciate hearing about them. Cheers, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Very, very beginner question: Followup
C.S. Hayward wrote: Having added a first test item, I thought I would try to add to the catalog the dozen or so books that happened to be on a desk on the library. I tried to search by ISBN, and the next two books were at least technically findable on Amazon by ISBN, but did not come up in the Z39.50/SRU search. I am curious as to which Z39.50 resources you are using. LC does not contain all books. Indeed, I find I need to use five primary Z39.50s to cover most books I catalog, with another 35 held in reserve for the very rare. I would expect to see most books on Amazon represented in LC, but they skip many foreign publishers. Oxford is my primary backup. Regards, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] koha controll number
Katrin Fischer wrote: this is not so easy to answer as Koha has no default feature for generating a number in 001 in the normal cataloguing editor (which I gather from your URL is the one you use). This feature does exist in the Advanced Editor for biblios. Pull down the Settings tab and select same. Regards, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] adding unique field
On 10/25/21 8:05 AM, Mohamad F Barham wrote: I need 952$i to be unique field as barcode. Is there some compelling reason you can't use 952$p for this, which is what it's designated use is? If you must use a different field, you might want to try selecting the "barcode.pl" from the pull-down list of Plugins on the 952$i editing page. Just be sure you do this for every Framework in use. I will leave it to those more knowledgeable than I to explain why this might be a bad idea. It may, for example, interfere with the barcode number in field 952$p. Regards, / Bruce / Bruce A. Metcalf Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Marc File to sort in spanish
Hi gang, Thought I'd bump this as I haven't seen a response in a month: My library has an international collection which means a lot of diacritical marks. I need help getting this to sort in a more nearly alphabetical order. I haven't been able to find guidance in the manual, wiki, or the archives of this list. I'd be happy to just have a link to a possible solution. Koha 19.11.08 installed from packages Linux Debian 8.3.0 Zebra 2.0.59 Regards, / Bruce / Bruce A. Metcalf, FAS Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Marc File to sort in spanish
On 8/12/20 9:44 AM, Luis Moises Rojas wrote: I am running Koha 19.11 on Ubuntu 18.04 and Mysql Ver 14.14 Distrib 5.7.31. After upgrade from version Koha 18 to 19 where are having problem to sort our catalog when trying to search a book, capital letter ( *É* , *Á, etc) are not recognize.* *I think the problem was on these files: *sort-string-utf.chr and word-phrase-utf.chr , but now someone told me the error is on a MARC file. You're not alone. My library has an international collection which means a lot of diacritical marks. I too need help getting this to sort in a more nearly alphabetical order. Koha 19.11.08 installed from packages Linux Debian 8.3.0 Zebra 2.0.59 Regards, / Bruce / Bruce A. Metcalf, FAS Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 17.11.01 released
On 01/08/2018 09:14 PM, Hector Gonzalez wrote: Try this: apt-get install koha-common It should mark it as "to be installed", try to resolve its dependencies, and upgrade it to the latest version. It looks like it is marked to be removed, and this it should be corrected. That worked! Koha is now running 17.11.01. A subsequent apt-get upgrade updated six packages, which is pretty unremarkable. But a subsequent apt-get dist-upgrade still wants to delete koha-common and others: == root@store:/# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... The following packages were automatically installed and are no longer required: [long list of files omitted] Use 'apt-get autoremove' to remove them. Done The following packages will be REMOVED: koha-common libtest-exception-perl libtest-mockobject-perl The following packages have been kept back: libtest-simple-perl 0 upgraded, 0 newly installed, 3 to remove and 1 not upgraded. After this operation, 453 MB disk space will be freed. Do you want to continue? [Y/n] == Curiouser and curiouser. Thanks, at least I've made the update, / Bruce / Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 17.11.01 released
On 01/08/2018 03:59 PM, Chris Cormack wrote: What happens if you try sudo apt-get install libtest-simple-perl ? Results: == root@store:/# apt-get install libtest-simple-perl Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [long list deleted] Use 'apt-get autoremove' to remove them. The following extra packages will be installed: libmojolicious-plugin-openapi-perl The following packages will be REMOVED: koha-common libplack-middleware-reverseproxy-perl libplack-perl libtest-exception-perl libtest-mockobject-perl libtest-sharedfork-perl libtest-tcp-perl starman The following NEW packages will be installed: libmojolicious-plugin-openapi-perl The following packages will be upgraded: libtest-simple-perl 1 upgraded, 1 newly installed, 8 to remove and 0 not upgraded. Need to get 362 kB of archives. After this operation, 439 MB disk space will be freed. Do you want to continue? [Y/n] == Odd thought: Is there a clue in my /etc/apt/sources.list? == deb https://debian.koha-community.org/koha stable main deb http://http.us.debian.org/debian/ jessie main non-free contrib deb http://security.debian.org/ jessie/updates main == Thanks again all, / Bruce / Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 17.11.01 released
btext-recordparser-perl libtext-tabulardisplay-perl libtext-unaccent-perl libtext-vfile-asdata-perl libtidy-0.99-0 libtie-ixhash-perl libtime-fake-perl libunicode-map-perl libuniversal-can-perl libuniversal-isa-perl libuniversal-require-perl libuuid-perl libwww-mechanize-perl libxml-dumper-perl libxml-filter-buffertext-perl libxml-libxslt-perl libxml-rss-perl libxml-sax-writer-perl libxml-twig-perl libxml-writer-perl libxml-xpathengine-perl libxml2-utils libyaz4 pwgen sgml-data starman tinymce ttf-dejavu ttf-dejavu-core ttf-dejavu-extra unzip xmlstarlet xsltproc yaz Use 'apt-get autoremove' to remove them. Done The following packages will be REMOVED: koha-common libtest-exception-perl libtest-mockobject-perl The following NEW packages will be installed: libmojolicious-plugin-openapi-perl The following packages have been kept back: libtest-simple-perl 0 upgraded, 1 newly installed, 3 to remove and 1 not upgraded. Need to get 29.0 kB of archives. After this operation, 439 MB disk space will be freed. Do you want to continue? [Y/n] ====== TIA, / Bruce / Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 17.11.01 released
On 01/04/2018 05:56 PM, Liz Rea wrote: If you are really on Debian Squeeze (6.0), that's super old Debian and Koha 17.11 won't work with that - as you noticed some of the dependencies aren't there for that old a version of Debian. This upgrade will be a slightly bigger project for you, as you'll need to upgrade your OS before you can upgrade Koha. You should probably do that anyway, sooner rather than later. Debian is now up to version 9, code name Stretch. My error. I am indeed running Debian ver. 8, which appears to still be supported. I tend to avoid version upgrades in the OS, as one never knows what won't be supported after, but will try that if all else fails. Thanks, / Bruce / Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 17.11.01 released
On 01/03/2018 12:25 PM, Jonathan Druart wrote: The Koha community is proud to announce the release of Koha > 17.11.01. Packages are also available. When I attempt to upgrade using apt-get, the system proposes to remove koha-common, but not to replace or upgrade it. This is not how previous upgrades have been done. Is this correct? Koha 17.05.05 installed via packages under Debian Squeeze. Regards, / Bruce / Bruce A. Metcalf, FAS Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Slightly OT: Cataloging Comics
On 07/07/2017 01:15 PM, Chad Roseburg wrote: We are going to be carrying comics again. Anyone with experience they'd be willing to share? Comics are very fragile compared to most materials and seem hardly worth the trouble as far as cataloging. Do you catalog them as an individual item or go generic? This question has arisen -- not about comics, but about a wide variety of other items over the years -- and the final decision of the libraries I've been with has always been, "If it's worth shelving, it's worth cataloging." Of course, there have been times when information about the _cost_ of such cataloging has influenced the decision to shelve. Regards, / Bruce / Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] 17.05 Edit Challenge
On 06/15/2017 02:01 AM, Fridolin SOMERS wrote: You may try flushing the Firefox cache : https://support.mozilla.org/en-US/kb/how-clear-firefox-cache#w_clear-the-cache Flushing the browser cache fixed it, thanks! Regards, / Bruce / Le 15/06/2017 à 00:02, Bruce A. Metcalf a écrit : Greetings, Package install on Jessie, was current16.11, just upgraded to 17.05. Now when I click on a title to edit an item, instead of an editing window, I get one named "Exporting to Dublin Core..." What's that and how do I edit? No joy from docs. Regards, / Bruce / Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] 17.05 Edit Challenge
Greetings, Package install on Jessie, was current16.11, just upgraded to 17.05. Now when I click on a title to edit an item, instead of an editing window, I get one named "Exporting to Dublin Core..." What's that and how do I edit? No joy from docs. Regards, / Bruce / Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] is koha right for our project run by volunteers?
On 03/08/2017 03:59 AM, King, Fred wrote: First of all, I should say that like everybody else on this list I'm > biased--I think Koha is wonderful, user-friendly, and a great > product. That it's free and open-source is icing on the cake. It's > also supported by a great bunch of people. > > Still, as much as I love it, I wouldn't recommend Koha unreservedly > for everyone for all purposes. It's a fully-functional ILS, and it > does take a little time and effort to learn. > Though I always recommend Koha, a lot of people there decide to go > with LibraryThing, mainly because they find it easier to use and they > don't need all the (wonderful!) features that Koha provides. I have to agree on both points. Koha will do nearly everything a library might need, and it gives you more flexibility than you might imagine how to use (I've been quietly ignoring whole sections of its powers for now). But you do need a server, someone to run it, and someone with a little library experience to help you set it up (and explain the technical terms). It won't be a zero cost project even if the software is free. While I use Koha at work, my personal collection is online with LibraryThing because all I want to do is to create a public bibliography and perhaps a few trades with others in the very narrow field. For this, Koha is overkill; perhaps so for your situation. However, if you want to manage circulation or do anything else "library-like", it's likely that you'd benefit from Koha. Just ask us for help in turning off the parts you don't need. Check out both and see which is the better match. Regards, / Bruce / Bruce A. Metcalf, FAS Librarian The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Data Leakage through Cover Requests
Greetings, An article came to my attention today that suggests that private data is being read by Amazon and Google when patrons use an OPAC that pulls cover images from these services. The article is here: <https://go-to-hellman.blogspot.com/2016/12/how-to-check-if-your-library-is-leaking.html> What is not clear to me is if Koha has this same problem, and if so, if it can be prevented. The blog post outlines a procedure for testing for this issue, but it's beyond my skill level to try it; perhaps someone else has the time and interest. If such evil is the price of having cover images served by third parties, then we can each decide if it's worth it, or if we want to develop a workaround. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Suggestion Challenge
Jonathan Druart wrote: Yes, by default you will only see the suggestion from your library. To see all the suggestions, you can change the filter on the left (Acquisition information block) and select "Any" That did it, thanks! It appears that those suggestions were attached to the deleted location. Now those suggestions are deleted as well (who know my library suffered from ED?). Now, to go set limits on who can post suggestions! Thanks all, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. 2016-04-08 0:11 GMT+01:00 Kerrie Stevens <kstev...@harvest.edu.au>: Hi Bruce, Do you have multiple locations in your catalogue? I am shown there are # suggestions but if they are from another location then I can't see them until I change my library to that same location. Then I can see them and deal with the suggestions before changing back to my normal library location. Hope this helps, Kerrie Stevens Harvest Bible College Message: 6 Date: Thu, 7 Apr 2016 19:01:32 -0400 From: "Bruce A. Metcalf" <bruce.metc...@augustansociety.net> To: Koha <koha@lists.katipo.co.nz> Subject: [Koha] Suggestion Challenge Message-ID: <5706e6cc.5020...@augustansociety.net> Content-Type: text/plain; charset=utf-8; format=flowed Greetings, The Acquisition Page tells me my system has over 9000 suggestions, but when I go to the Suggestions management page to look a them, it says "No data available in table". I'm thinking this is some sort of glitch, but I have no idea where to go to reset the suggestion number to zero. Any suggestions (no pun intended)? Koha 3.22.5from packages under Debian 7.10, both current on updates. Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society,Inc. -- Subject: Digest Footer ___ Koha mailing list Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha -- End of Koha Digest, Vol 126, Issue 12 * ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Suggestion Challenge
Greetings, The Acquisition Page tells me my system has over 9000 suggestions, but when I go to the Suggestions management page to look a them, it says "No data available in table". I'm thinking this is some sort of glitch, but I have no idea where to go to reset the suggestion number to zero. Any suggestions (no pun intended)? Koha 3.22.5from packages under Debian 7.10, both current on updates. Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society,Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Indexing Not Updating
On 12/28/2015 10:58 PM, Chris Cormack wrote: Your paths still appear to be messed up for sudo try sudo /usr/sbin/koha-shell instancename That seems to have worked, which brings us to zebrasrv -v none,fatal,warn -f /etc/koha/sites//koha-conf.xml Replacing with the name of your koha instance This failed again, but I thought to check the permissions of this file and found them wanting. That corrected, it worked a bit better, giving: $ zebrasrv -v none,fatal,warn -f /etc/koha/sites/library/koha-conf.xml 15:07:30-29/12 [fatal] Zebra server already running [Resource temporarily unavailable] At this time, the "About Koha / System Information" page now suggests that Zebra is running, with the message: Zebra 2.0.44 (C) 1994-2010, Index Data ApS Zebra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. SHA1 ID: 419ad759807269fdfa379799a051ed3a551c6541 Using ICU As I don't have the password to use the koha-shell, I dropped back into the regular shell and ran koha-zebra-reindex. Success! Recently cataloged materials now show! My sincere thanks to all who helped. This community is a very big part of why Koha is such an excellent tool. Thanks again, Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Indexing Not Updating
On 12/27/2015 12:25 PM, Bruce A. Metcalf wrote: I wonder if you still have other path issues, or it might be the switch from grs1 to dom. What version did you upgrade from ? I think it was Version 3.12 that you helped me install at KohaCon13 (thanks again). I've since been upgrading each release as it comes out using packages. Ahh that may be it, take a look at http://wiki.koha-community.org/wiki/Switching_to_dom_indexing We tend to not try to update the config file automatically as we might accidentally clobber some of your intentional changes, so it might be that it hasn't switched to DOM I'd back up the file, make the changes, restart the zebraserver (service koha-common restart) run a full reindex (koha-rebuild-zebra -f) and see if that fixes it, you can always roll back if it doesn't It doesn't. The instructions say to check "/About Koha/ > /System information"/ for GRS1/DOM-related warnings. I see two warnings: > WarningYou are missing the entry in your koha-conf.xml file. > WarningYou are missing the entry in your koha-conf.xml file. I can't say if these were there previously, and neither appears to be related. I also notice that in "/About Koha/ > /Server information"/ there's an error that does seem related: *> Error *Zebra server seems not to be available. Is it started? Perhaps this is a clue? In the absence of new ideas, I have tried switching to the indexing daemon using by: - Comment the rebuild_zebra.pl line in /etc/cron.d/koha-common - Enable the indexer daemon in /etc/default/koha-common - Restart Koha's daemons: $ sudo service koha-common stop ; sudo service koha-common start I also looked at my zebra-error.log, which turns out to be filled with this sequence, repeating every 30 seconds: 20151228 15:16:48 library-koha-zebra: client (pid 20683) exited with 1 status 20151228 15:16:48 library-koha-zebra: client (pid 20684) exited with 1 status 20151228 15:16:48 library-koha-zebra: client (pid 20685) exited with 1 status 20151228 15:16:48 library-koha-zebra: client (pid 20686) exited with 1 status 20151228 15:16:48 library-koha-zebra: client (pid 20687) exited with 1 status 20151228 15:16:48 library-koha-zebra: terminating too quickly, waiting 30 seconds Note that this log tail was observed after switching to the indexing daemon. Lots of data, very little understanding here! Thanks in advance, Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Indexing Not Updating
On 12/28/2015 10:34 PM, Chris Cormack wrote: I think the problem might not be the indexing itself, but that your Zebra server is not running. That does seem to be the issue. This might help: sudo service restart koha-common Ahh typo sudo service koha-common restart That runs without generating errors, but no change. Then you can do: ps axf | grep "zebrasrv" To see if it's running. I can't tell from this if it's running or not. It's definitely not, the daemon to start it is running, but it isn't running. The log had a hint with it's respawning too fast. zebrasrv itself is not starting, there could be quite a few reasons, but most likely it's something to do with permissions. What you could try doing is sudo koha-shell Fail: "sudo: koha-shell: command not found" Tried "sudo apt-get install koha-shell", but the package isn't available. Should it be? Also tried "sudo apt-get check" without result. zebrasrv -v none,fatal,warn -f /etc/koha/sites//koha-conf.xml Replacing with the name of your koha instance Tried that (in the regular shell) and got a permissions error. Hopefully that will show an error message that will help us figure out what is going on That would be nice. Thanks to all, Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Indexing Not Updating
On 12/26/2015 09:11 PM, Chris Cormack wrote: I wonder if you still have other path issues, or it might be the switch from grs1 to dom. What version did you upgrade from ? I think it was Version 3.12 that you helped me install at KohaCon13 (thanks again). I've since been upgrading each release as it comes out using packages. Ahh that may be it, take a look at http://wiki.koha-community.org/wiki/Switching_to_dom_indexing We tend to not try to update the config file automatically as we might accidentally clobber some of your intentional changes, so it might be that it hasn't switched to DOM I'd back up the file, make the changes, restart the zebraserver (service koha-common restart) run a full reindex (koha-rebuild-zebra -f) and see if that fixes it, you can always roll back if it doesn't It doesn't. The instructions say to check "/About Koha/ > /System information"/ for GRS1/DOM-related warnings. I see two warnings: > WarningYou are missing the entry in your koha-conf.xml file. > WarningYou are missing the entry in your koha-conf.xml file. I can't say if these were there previously, and neither appears to be related. I also notice that in "/About Koha/ > /Server information"/ there's an error that does seem related: *> Error *Zebra server seems not to be available. Is it started? Perhaps this is a clue? Thanks, Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Indexing Not Updating
Greetings, Koha 3.22.1 installed via packages, running on Debian "Wheezy" 7.9, both recently updated. Cataloging works, and I can see the biblioand item records using the Inventory tool, but Search does not return any hits. It had previously worked, but as Imostly work on the back end, it may have been a version or two back when last I tried, and patron feedback is nil. I did try running the Zebra Permission Repair process at <http://wiki.koha-community.org/wiki/Fix_zebra_permissions>, but it fails with messages like: "sudo: koha-create-dirs: command not found" and "sudo: koha-rebuild-zebra: command not found". Suggestions? Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Indexing Not Updating
On 12/26/2015 03:08 PM, Chris Cormack wrote: On 27 December 2015 8:54:43 am NZDT, "Bruce A. Metcalf" <bruce.metc...@augustansociety.net> wrote: Koha 3.22.1 installed via packages, running on Debian "Wheezy" 7.9, both recently updated. Cataloging works, and I can see the biblioand item records using the Inventory tool, but Search does not return any hits. It had previously worked, but as Imostly work on the back end, it may have been a version or two back when last I tried, and patron feedback is nil. I did try running the Zebra Permission Repair process at <http://wiki.koha-community.org/wiki/Fix_zebra_permissions>, but it fails with messages like: "sudo: koha-create-dirs: command not found" and "sudo: koha-rebuild-zebra: command not found". Well that is definitely a symptom of your problem, koha-rebuild-zebra is what the cron job runs to update the index. Can you do an ls /usr/sbin please, are those files there, if so try running them with the full path, eg sudo /usr/sbin/koha-create-dirs instancename That should get the index rebuilt. Then you could look up how to fix the path in sudo. This appears to have worked for most of the commands from that FAQ page. However, when I ran "koha-rebuild-zebra" it reported "Records exported: 2904" at one point, then "Records exported: 10279" at another. Given that I have about 3300 items at present, neither looks quite right. And while it did report starting zebra for this instance, the catalog search function still fails to find anything. As for the path in sudo, I get: > # echo $PATH > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin So, some progress, but still questions. Thanks, Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Indexing Not Updating
On 12/26/2015 04:29 PM, Chris Cormack wrote: Koha 3.22.1 installed via packages, running on Debian "Wheezy" 7.9, both recently updated. Cataloging works, and I can see the biblioand item records using the Inventory tool, but Search does not return any hits. It had previously worked, but as I mostly work on the back end, it may have been a version or two back when last I tried, and patron feedback is nil. I did try running the Zebra Permission Repair process at <http://wiki.koha-community.org/wiki/Fix_zebra_permissions>, but it fails with messages like: "sudo: koha-create-dirs: command not found" and "sudo: koha-rebuild-zebra: command not found". Well that is definitely a symptom of your problem, koha-rebuild-zebra is what the cron job runs to update the index. Can you do an ls /usr/sbin please, are those files there, if so try running them with the full path, eg sudo /usr/sbin/koha-create-dirs instancename. That should get the index rebuilt. Then you could look up how to fix the path in sudo. This appears to have worked for most of the commands from that FAQ page. However, when I ran "koha-rebuild-zebra" it reported "Records exported: 2904" at one point, then "Records exported: 10279" at another. Given that I have about 3300 items at present, neither looks quite right. 2904 will be the biblio records, 10279 will be your authority records. Okay, that sounds reasonable. And while it did report starting zebra for this instance, the catalog search function still fails to find anything. I wonder if you still have other path issues, or it might be the switch from grs1 to dom. What version did you upgrade from ? I think it was Version 3.12 that you helped me install at KohaCon13 (thanks again). I've since been upgrading each release as it comes out using packages. Thanks, Bruce A. Metcalf Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Buggy OS Upgrade
Greetings, Koha 3.18.5 installed using packages under Debian squeeze. This week we upgraded our distro from squeeze to wheezy. Now when we try to save a biblio found using Z39.50 search, we get this error message: Byte order is not compatible at /usr/lib/perl/5.14/Storable.pm line 416 at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 401 Clearly, we muffed something in the upgrade, but I haven't a clue what. Any suggestions, or should I roll back to last week's backup? ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Hardware requirements
On 09/07/2014 01:50 AM, Witoszynskyj Stephan wrote: we are a (very) small library. We are using Koha since a couple of months. So far our installation is „offline“ (on an old Mac Mini that is not accessible from the internet). Now we want to go online. Due to our limited budget the only option will be renting a virtual server. However, I have no idea which specifications will be sufficient in our case. I know that more is always better, but our financial resources are really limited. The offerings that I currently have, have following specifications: * Single Core, 512 MB RAM, 20 GB hard disk * Single Core, 1024 MB RAM, 40 GB hard disk We have less than 5000 books and less than 250 customers. Even the small size should be more than adequate, though take note of comments others have made about speed vs. RAM. I'm running a Dual Core, 2000 MB RAM, 8 GB hard disk for 3000 books. It runs as fast as a dedicated box on my test bench, and there's plenty of overhead. (Though as I'm a reference library, there's no circulation use.) What I suggest you consider is a virtual hosting service that permits you to adjust your RAM, hard drive space, and perhaps bandwidth on the fly. I've changed my configuration a dozen times as my wee system has grown, and it's nice to know I'm only 5 minutes from more drive space! My provider is RimuHosting (more Kiwis!) and the above system is costing me about US$20/month. One could do well with much less. Buy small and upgrade as you feel the need. I’m sorry that I’m asking a question that has been asked a hundred times… No apology needed. It's an excellent question, and the answer will evolve over time, so it's good to ask again. Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] call number sort problem
Fridolin SOMERS fridolin.som...@biblibre.com wrote: Look into database the values of items.cn_sort for thoses callnumbers. The call numbers are fine. It's the sorting sequence I wanted to change. As in my previous post, I effected this by changing to a different set of Classification Filing Rules. LCC did what I wanted, Generic did not. Regards, / Bruce / Bruce A. Metcalf Librarian The Augustan Society, Inc. Le 11/06/2014 05:29, Bruce A Metcalf a écrit : Fridolin SOMERS fridolin.som...@biblibre.com wrote: Le 21/03/2014 22:05, Margo Duncan a écrit : We're having some issues with call number sort in our reports and I'm wondering if anyone has any insights. It appears that cn_sort has two different methods of sorting call numbers. One way is that 0 is added so that a call number of HD30.19 is HD003019. The other way is with _ so HD30.19 is HD_0030_19. ... So can I adjust the sorting method, or is there something wrong with my data? items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref DefaultClassificationSource). I think I understand this, but I don't understand how to make a call number like H B34 sort before one like HM B34. It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!). Can this be changed, and if so, how? Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] sorting long Cutter's
Giuseppe Angilella giuseppe.angile...@ct.infn.it wrote: call numbers having Cutter parts made of several substrings currently are not sorted correctly. Here are examples: | itemcallnumber | cn_source | cn_sort| | 530 F435 1996 v1 | ddc | 530_F435_1996000_V1| | 530 F435 1996 v2p1 | ddc | 530_F435_1996000_V2P1 | | 530 F435 1996 v2p2 | ddc | 530_F435_1996000_V2P2 | Despite being in the Dewey 530 class, these items are sorted after any 530.xy item (and before any 531, which is OK). Any hint? I've been experimenting ways to address this, and may have an option worth testing: In Home Administration Classification sources you can specify the Filing Rule to apply to each Classification Source. A second table allows you to specify the Sorting routine for each Filing Rule. I found that by changing the Sorting routine from generic to LCC, I got my system to sort properly. You might find this worth testing. Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] call number sort problem
Fridolin SOMERS fridolin.som...@biblibre.com wrote: Le 21/03/2014 22:05, Margo Duncan a écrit : We're having some issues with call number sort in our reports and I'm wondering if anyone has any insights. It appears that cn_sort has two different methods of sorting call numbers. One way is that 0 is added so that a call number of HD30.19 is HD003019. The other way is with _ so HD30.19 is HD_0030_19. ... So can I adjust the sorting method, or is there something wrong with my data? items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref DefaultClassificationSource). I think I understand this, but I don't understand how to make a call number like H B34 sort before one like HM B34. It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!). Can this be changed, and if so, how? Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 3.16.0 released
Robin Sheat ro...@catalyst.net.nz wrote: Bruce A Metcalf schreef op zo 25-05-2014 om 23:16 [-0400]: Updated using packages from 3.14.6 to 3.16.0 under Squeeze. All appeared to go well using apt-get dist-upgrade, but I am now offline. You didn't actually say in what way you were offline so I don't know how well I can help. However, it might be that you're hitting this: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12312 If so, the fix is to run: sudo a2ensite instancename.conf sudo service apache2 restart That was it! Thank you muchly! Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 3.16.0 released
The Koha community is pleased to announce the release of version 3.16.0 of the Koha library automation system. Updated using packages from 3.14.6 to 3.16.0 under Squeeze. All appeared to go well using apt-get dist-upgrade, but I am now offline. I would appreciate pointers to a relevant tutorial, if not direct instructions. Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Kohacon13 Contact
Greets, I am fast approaching the deadline for planning my participation at Kohacon13. There has been no change on the web site for months, and no dates listed. I did attend a planning meeting, but did not get an email address for anyone. I have tried to volunteer to help, but am unable to log on to the wiki to add my name. Still willing if someone can assist. Sorry to trouble this list with the noise, but I know of nowhere else to ask. Bruce A. Metcalf Augustan Society Library Orlando, Florida, USA ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Install for Dummies
Koustubha Kale wrote: bruce@library:/usr/share/__koha4/bin/migration_tools$ For the error message you have pasted above, it seems your koha is located at /usr/share/__koha4 Actually, /usr/share/koha. The koha4 directories are a leftover liblime install that was abandoned when we moved to the community distro. Should probably purge it. If thats correct ( you can verify by running command ls /usr/share/__koha4 ) then your PERL5LIB should be PERL5LIB=/usr/share/__koha4/lib # ls /usr/share/koha bin doc intranet lib man misc opac # ls /usr/share/koha/lib C4 So that looks right, I think. Also make sure your zebra server is running by running command ps aux|grep zebra You should see atleast three lines of output on above command. Nope, just: # ps aux|grep zebra root 16132 0.0 0.1 3292 508 pts/0 R+ 22:10 0:00 grep zebra Does this suggest that zebra hasn't been started? How to? Thanks again for the effort, / Bruce / Bruce A Metcalf Library Director Augustan Society Library rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl -b -r -v Can't locate Koha.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at ./rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl line 5. BEGIN failed--compilation aborted at ./rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl line 5. Hope that helps, Bruce On 2012-01-19 09 tel:2012-01-19%2009:41, Bruce Metcalf wrote: Bruce Metcalf wrote: I am a new user of Koha, and have had my Linux guru (who had not seen Koha prior to this work) install version 3.6.2 under Debian Squeeze on an otherwise empty virtual server. All appears to be going exactly as it should. owever, the public OPAC shows no books in the collection. Eric Bégin wrote: Get a look at this link. It shows the most common problems when you get not result in the OPAC. http://koha-community.org/__documentation/faq/searching/ http://koha-community.org/documentation/faq/searching/ Don't hesitate to come back and ask for more info if this link doesn't solve your problem. This page seems to suggest: zebraidx -x /.../zebra-biblios.cfg drop biblios zebraidx -c /.../zebra-biblios.cfg commit rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl -b -r -v All three commands fail with a variety of messages, but all include file not found. I'm thinking that there is an important configuration or initialization that hasn't been completed? Regards, / Bruce / Bruce A. Metcalf Executive Director The Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Install for Dummies
Paul wrote: At 08:27 PM 1/21/2012 -0500, Bruce A Metcalf wrote: Paul wrote: [snip] koha@nelson:/usr/share/koha$ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -a -r -v koha@nelson:/usr/share/koha$ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x This appears to do *something*. It runs a number of lines of code, ending with CLEANING. OK - [assuming no warning messages] zebra appears to have completed the indexing ... Still no books revealed in the OPAC. In your staff interface (koha-admin), if you put the single letter a (no quotes) in the Search catalogue box, what do you get? No results found Please ensure that in Home Administration System Preferences Searching that the Nozebra preference is set to _Use_ the Zebra search engine. Check. At least I got that part right! Thanks, / Bruce / Bruce A. Metcalf Library Director Augustan Society Library At 12:17 PM 1/21/2012 -0500, Chris Nighswonger wrote: Hi Bruce, The correct paths for your installation would have been given in the notes produced at the end of running Makefile.PL (not sure where this would show up if you used the deb packages). These paths will *have* to be correct in order for Koha related cli scripts to run properly. Perhaps someone more familiar with the deb packages could help if that is, indeed, what you used. If the paths you selected are correct, then I'm out of ideas for the moment. Kind Regards, Chris On Sat, Jan 21, 2012 at 10:16 AM, Bruce A Metcalf cons...@augustansociety.org mailto:cons...@augustansociety.org wrote: Chris Nighswonger wrote: Have a read at these FAQ's: http://koha-community.org/documentation/faq/searching/ Pay careful attention to the solution for question #4. It appears you've not exported the proper env vars. It sounds like you're recommending: 1. Check that you are exporting the two environmental variables necessary to run Koha scripts from the command line. These are (modify to fit paths on your system): PERL5LIB=/path/to/koha KOHA_CONF=/path/to/koha-conf.xml Which sounds not unreasonable. I set: KOHA_CONF=/etc/koha/koha-conf.xml Which seems reasonable. I then set: PERL5LIB=/usr/share/koha/lib I chose this because the failure message for rebuild_zebra.pl http://rebuild_zebra.pl claims it can't locate C4/Context.pm in @INC, which includes /etc/perl, and where that file can be found. It would appear that these choices were incorrect, or that I've made some other important error, as these two changes make no change in the failure message when I run rebuild_zebra.pl http://rebuild_zebra.pl. I *did* warn y'all I was a newbie With thanks, / Bruce / Bruce A. Metcalf Library Director The Augustan Society Library On Fri, Jan 20, 2012 at 9:01 PM, Bruce Metcalf bruce.metc...@figzu.com mailto:bruce.metc...@figzu.com mailto:bruce.metc...@figzu.com wrote:   Eric Bégin wrote:       All three commands fail with a variety of messages, but all       include file not found.     Indeed, that doesn't look good.     Can you provide the full output of the rebuild_zebra -b -r -v   bruce@library:/usr/share/__koha4/bin/migration_tools$   rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl/ -b -r -v   Can't locate Koha.pm in @INC (@INC contains: /etc/perl   /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5   /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10   /usr/local/lib/site_perl .) at ./rebuild_zebra.pl http://rebuild_zebra.pl   http://rebuild_zebra.pl http://rebuild_zebra.pl/ line 5.   BEGIN failed--compilation aborted at ./rebuild_zebra.pl http://rebuild_zebra.pl   http://rebuild_zebra.pl http://rebuild_zebra.pl/ line 5.   Hope that helps,   Bruce     On 2012-01-19 09 tel:2012-01-19%2009 tel:2012-01-19%2009:41, Bruce Metcalf wrote:       Bruce Metcalf wrote:           I am a new user of Koha, and have had my Linux guru           (who had not           seen Koha prior to this work) install version 3.6.2           under Debian           Squeeze on an otherwise empty virtual server.           All appears to be going exactly as it should.           owever, the public OPAC shows no books in the           collection.       Eric Bégin wrote:   Ã
Re: [Koha] Install for Dummies
Paul wrote: Having experienced a few glitches ourselves, here are some extracts from our cheat sheet (nelson is the name of our Debian/Ubuntu server with Koha 3.6.1 installed and happily working): *** do mysql dump FIRST *** Only six records in the system, so I skipped this. *** do not go near link_bibs_to_authorities.pl *** Don't even know where that is. Now su to the proper user: paul@nelson:/usr/share/koha$ su koha Tried by as myself as su and as koha. koha@nelson:/usr/share/koha$ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -a -r -v koha@nelson:/usr/share/koha$ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x This appears to do *something*. It runs a number of lines of code, ending with CLEANING. Still no books revealed in the OPAC. Thanks, / Bruce / Bruce A. Metcalf Library Director Augustan Society Library At 12:17 PM 1/21/2012 -0500, Chris Nighswonger wrote: Hi Bruce, The correct paths for your installation would have been given in the notes produced at the end of running Makefile.PL (not sure where this would show up if you used the deb packages). These paths will *have* to be correct in order for Koha related cli scripts to run properly. Perhaps someone more familiar with the deb packages could help if that is, indeed, what you used. If the paths you selected are correct, then I'm out of ideas for the moment. Kind Regards, Chris On Sat, Jan 21, 2012 at 10:16 AM, Bruce A Metcalf cons...@augustansociety.org mailto:cons...@augustansociety.org wrote: Chris Nighswonger wrote: Have a read at these FAQ's: http://koha-community.org/documentation/faq/searching/ Pay careful attention to the solution for question #4. It appears you've not exported the proper env vars. It sounds like you're recommending: 1. Check that you are exporting the two environmental variables necessary to run Koha scripts from the command line. These are (modify to fit paths on your system): PERL5LIB=/path/to/koha KOHA_CONF=/path/to/koha-conf.xml Which sounds not unreasonable. I set: KOHA_CONF=/etc/koha/koha-conf.xml Which seems reasonable. I then set: PERL5LIB=/usr/share/koha/lib I chose this because the failure message for rebuild_zebra.pl http://rebuild_zebra.pl claims it can't locate C4/Context.pm in @INC, which includes /etc/perl, and where that file can be found. It would appear that these choices were incorrect, or that I've made some other important error, as these two changes make no change in the failure message when I run rebuild_zebra.pl http://rebuild_zebra.pl. I *did* warn y'all I was a newbie With thanks, / Bruce / Bruce A. Metcalf Library Director The Augustan Society Library On Fri, Jan 20, 2012 at 9:01 PM, Bruce Metcalf bruce.metc...@figzu.com mailto:bruce.metc...@figzu.com mailto:bruce.metc...@figzu.com wrote:   Eric Bégin wrote:       All three commands fail with a variety of messages, but all       include file not found.     Indeed, that doesn't look good.     Can you provide the full output of the rebuild_zebra -b -r -v   bruce@library:/usr/share/__koha4/bin/migration_tools$   rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl http://rebuild_zebra.pl/ -b -r -v   Can't locate Koha.pm in @INC (@INC contains: /etc/perl   /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5   /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10   /usr/local/lib/site_perl .) at ./rebuild_zebra.pl http://rebuild_zebra.pl   http://rebuild_zebra.pl http://rebuild_zebra.pl/ line 5.   BEGIN failed--compilation aborted at ./rebuild_zebra.pl http://rebuild_zebra.pl   http://rebuild_zebra.pl http://rebuild_zebra.pl/ line 5.   Hope that helps,   Bruce     On 2012-01-19 09 tel:2012-01-19%2009 tel:2012-01-19%2009:41, Bruce Metcalf wrote:       Bruce Metcalf wrote:           I am a new user of Koha, and have had my Linux guru           (who had not           seen Koha prior to this work) install version 3.6.2           under Debian           Squeeze on an otherwise empty virtual server.           All appears to be going exactly as it should.           owever, the public OPAC shows no books in the           collection.       Eric Bégin wrote:         Get a look at this link. It shows the most common         problems when you         get not result in the OPAC
[Koha] Install for Dummies
Greetings, I am a new user of Koha, and have had my Linux guru (who had not seen Koha prior to this work) install version 3.6.2 under Debian Squeeze on an otherwise empty virtual server. The staff client comes up fine, and using the beginners tutorials I've been able to set all of the parameters (that I understand). I have used the cataloging function to enter half a dozen bibliographic records and added holdings information for them. A shelf list creates correctly. All appears to be going exactly as it should. However, the public OPAC shows no books in the collection. Is there some step that is not covered by the tutorials that must be used to grant access? Can anyone suggest an online tutorial that covers the process? Cheers, / Bruce / Bruce A. Metcalf The Augustan Society Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
