Restarting Indexing -- Maybe Reindexing Altogether
Hi, all! My library's system has stopped indexing new records. Case in point: I added Starlog to our catalog, and five ours later, it still does not appear when searched. We've also added a few more authority headings, but several hours later, they too cannot be found. So is it possible to restart the indexing? Failing that, is is possible to reindex the entire catalog? I'd like to learn this now before we upgrade to 20.05 or 20.11 this spring or summer. Many thanks. P. S. Running Koha 19.05 on Debian 9 "Buster". (When we upgrade to 20.XX, we'll also upgrade to Debian 10 or 11.) -- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk@aol.com [h] cmkelleymls@gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.
Dear Charles it seems that your zebra process is not running you need a shell see https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... section zebra check if zebra is still there
koha-zebra —status
and if not you can —restart or rebuild your zebra index
koha-rebuild-zebra nameofyourinstance
Kind regards Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG Am 10.02.2022 um 05:53 schrieb Charles Kelley <cmkelleymls@gmail.com<mailto:cmkelleymls@gmail.com>>: Hi, all! My library's system has stopped indexing new records. Case in point: I added Starlog to our catalog, and five ours later, it still does not appear when searched. We've also added a few more authority headings, but several hours later, they too cannot be found. So is it possible to restart the indexing? Failing that, is is possible to reindex the entire catalog? I'd like to learn this now before we upgrade to 20.05 or 20.11 this spring or summer. Many thanks. P. S. Running Koha 19.05 on Debian 9 "Buster". (When we upgrade to 20.XX, we'll also upgrade to Debian 10 or 11.) -- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk@aol.com<mailto:mnogojazyk@aol.com> [h] cmkelleymls@gmail.com<mailto:cmkelleymls@gmail.com> [p] linkedin.com/in/cmkelleymls<http://linkedin.com/in/cmkelleymls> <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
Hello, Rainer! Thanks for responding. I ran the command #koha-zebra -status but the shell reported nothing. In my limited understanding of Linux, this means there was nothing to run, but the executable is on the system. That said, we are running ElasticSearch instead of Zebra. Does that matter? Many thanks. In our latest exchange, on 10 Feb. 2022 at 16:49 [JST], I received the following from Rainer Stowasser: it seems that your zebra process is not running
you need a shell
see
https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... section zebra
check if zebra is still there
koha-zebra —status
and if not you can —restart
or rebuild your zebra index
koha-rebuild-zebra nameofyourinstance
Kind regards
Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG
In an earlier exchange, on 10 Feb. 2022 at 14:53 [JST], I wrote: My library's system has stopped indexing new records. Case in point: I
added Starlog to our catalog, and five ours later, it still does not appear when searched. We've also added a few more authority headings, but several hours later, they too cannot be found.
So is it possible to restart the indexing? Failing that, is is possible to reindex the entire catalog? I'd like to learn this now before we upgrade to 20.05 or 20.11 this spring or summer.
Many thanks.
P. S. Running Koha 19.05 on Debian 9 "Buster".
(When we upgrade to 20.XX, we'll also upgrade to Debian 10 or 11.)
-- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk@aol.com [h] cmkelleymls@gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.
Dear Charles yes this makes a difference then you where on of the early adopters ;-) but the principle stays the same
ps -aux | grep elasticsearch
check if the process is there koha-elasticsearch --rebuild -d -v koha you can find details for this on the wiki or here https://bywatersolutions.com/education/elastic-search-configuration Kind regards Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG
Am 10.02.2022 um 10:46 schrieb Charles Kelley <cmkelleymls@gmail.com>:
Hello, Rainer!
Thanks for responding.
I ran the command
#koha-zebra -status
but the shell reported nothing. In my limited understanding of Linux, this means there was nothing to run, but the executable is on the system. That said, we are running ElasticSearch instead of Zebra. Does that matter?
Many thanks.
In our latest exchange, on 10 Feb. 2022 at 16:49 [JST], I received the following from Rainer Stowasser:
it seems that your zebra process is not running
you need a shell
see https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... section zebra
check if zebra is still there
koha-zebra —status
and if not you can —restart
or rebuild your zebra index
koha-rebuild-zebra nameofyourinstance
Kind regards
Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG
In an earlier exchange, on 10 Feb. 2022 at 14:53 [JST], I wrote:
My library's system has stopped indexing new records. Case in point: I added Starlog to our catalog, and five ours later, it still does not appear when searched. We've also added a few more authority headings, but several hours later, they too cannot be found.
So is it possible to restart the indexing? Failing that, is is possible to reindex the entire catalog? I'd like to learn this now before we upgrade to 20.05 or 20.11 this spring or summer.
Many thanks.
P. S. Running Koha 19.05 on Debian 9 "Buster".
(When we upgrade to 20.XX, we'll also upgrade to Debian 10 or 11.)
--
よろしくお願いします。
-- Charles.
Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338
Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN
+1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell]
mnogojazyk@aol.com [h] cmkelleymls@gmail.com [p]
linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe.
Dear Rainer: Thanks for the confirmation. If it hadn't been for your mention of the ElasticSearch and Zebra executables for Koha, I would not even thought to look for them and ultimately #koha-elasticsearch --rebuild -d -v {koha instance} Yes, I found it about an hour after our correspondence last evening. (I live in Japan and it was evening here when we corresponded.) In any event, it worked perfectly. I tried it on a clone first lest we not lose our catalog. Thanks again. In our latest exchange, 10 Feb. 2022 at 1902 [JST], I received this from you: yes this makes a difference
then you where on of the early adopters ;-)
but the principle stays the same
ps -aux | grep elasticsearch
check if the process is there
koha-elasticsearch --rebuild -d -v koha
you can find details for this on the wiki
or here
https://bywatersolutions.com/education/elastic-search-configuration
Kind regards
Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG
Am 10.02.2022 um 10:46 schrieb Charles Kelley <cmkelleymls@gmail.com>:
Hello, Rainer!
Thanks for responding.
I ran the command
#koha-zebra -status
but the shell reported nothing. In my limited understanding of Linux, this means there was nothing to run, but the executable is on the system. That said, we are running ElasticSearch instead of Zebra. Does that matter?
Many thanks.
In our latest exchange, on 10 Feb. 2022 at 16:49 [JST], I received the following from Rainer Stowasser:
it seems that your zebra process is not running
you need a shell
see
section zebra
check if zebra is still there
koha-zebra —status
and if not you can —restart
or rebuild your zebra index
koha-rebuild-zebra nameofyourinstance
Kind regards
Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG
In an earlier exchange, on 10 Feb. 2022 at 14:53 [JST], I wrote:
My library's system has stopped indexing new records. Case in point: I added Starlog to our catalog, and five ours later, it still does not appear when searched. We've also added a few more authority headings, but several hours later, they too cannot be found.
So is it possible to restart the indexing? Failing that, is is
https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... possible
to reindex the entire catalog? I'd like to learn this now before we upgrade to 20.05 or 20.11 this spring or summer.
Many thanks.
P. S. Running Koha 19.05 on Debian 9 "Buster".
(When we upgrade to 20.XX, we'll also upgrade to Debian 10 or 11.)
-- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk@aol.com [h] cmkelleymls@gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.
Hello, all! In our latest exchange, on 11 Feb. 2022 at 07:28 [JST], I wrote this: Thanks for the confirmation. If it hadn't been for your mention of the
ElasticSearch and Zebra executables for Koha, I would not even thought to look for them and ultimately
#koha-elasticsearch --rebuild -d -v {koha instance}
Yes, I found it about an hour after our correspondence last evening. (I live in Japan and it was evening here when we corresponded.) In any event, it worked perfectly. I tried it on a clone first lest we not lose our catalog.
Well, my elation was ill-founded. I worked on the catalog all day last Friday and all was fine. When I began work again today, the catalog was misindexed again. I couldn't find records that I had entered last Friday and records I downloaded into Koha this morning. Reindexing the bibliographic records and the authority records with #koha-elasticsearch --rebuild -d -v {koha instance} proved fruitless. I have been able to export intact the bibliographic records and the authority records with the Tools functions. I have to create a new empty instance and import the records into the new instance unless somebody has a better solution. Does anyone? I'll have to reenter the circulation tables, item types, authorized values, etc. Does anyone know how to extract them from an instance for importation into another instance? Just the tables, etc., mind you, not the bibliographic and authority records. Those, I already have in MARC format. I don't know what I did wrong, but it must have been something. Thanks, all. P. S. My library is not going live until summer or fall. The disruption in order to rebuild by exporting the records to a new instance would cause us to lose about a week's worth in preparation to the live server, that's all. -- よろしくお願いします。 -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk@aol.com [h] cmkelleymls@gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.
hi Charles you are looking for the following 4 commands sudo koha-indexer --status mykoha sudo koha-indexer --stop mykoha sudo koha-indexer --start mykoha sudo koha-indexer --restart mykoha https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... On 10/02/22 5:53 pm, Charles Kelley wrote:
Hi, all!
My library's system has stopped indexing new records. Case in point: I added Starlog to our catalog, and five ours later, it still does not appear when searched. We've also added a few more authority headings, but several hours later, they too cannot be found.
So is it possible to restart the indexing? Failing that, is is possible to reindex the entire catalog? I'd like to learn this now before we upgrade to 20.05 or 20.11 this spring or summer.
Many thanks.
P. S. Running Koha 19.05 on Debian 9 "Buster".
(When we upgrade to 20.XX, we'll also upgrade to Debian 10 or 11.)
participants (3)
-
Charles Kelley -
Mason James -
Stowasser Rainer