New added items and biblio records not searchable on two-tier setup
Hi All I am running an instance of Koha 18.11.03.000 on Debian 8.11 where both the application server and the Koha database where running on one server. My server was becoming overwhelmed so I decided to have a two-tier setup with the database running on another separate server by changing the <hostname>localhost</hostname in /etc/koha/sites/library/koha-conf.xml to the IP address of the database server and granting the relevant privileges. Everything seems to be going on well. However, newly added items and biblio records are not searchable on the catalogue pointing to a browse index-related issue. What should I do on a two-tier setup to ensure that newly added items are added to the browse index and are searchable? Any pointers are most welcome. Kind Regards, Admire Mutsikiwa ICT Projects Manager Libraries University of Zimbabwe Tel:+263-4-303276 *“It is easy to dodge our responsibilities, but we cannot dodge the consequences of dodging our responsibilities.” Josiah Charles Stamp, 1880-1941, former director of the Bank of England *
On 2019-05-02 12:15 p.m., Admire Mutsikiwa wrote:
Hi All
I am running an instance of Koha 18.11.03.000 on Debian 8.11 where both the application server and the Koha database where running on one server. My server was becoming overwhelmed so I decided to have a two-tier setup with the database running on another separate server by changing the <hostname>localhost</hostname in /etc/koha/sites/library/koha-conf.xml to the IP address of the database server and granting the relevant privileges. Everything seems to be going on well. However, newly added items and biblio records are not searchable on the catalogue pointing to a browse index-related issue. What should I do on a two-tier setup to ensure that newly added items are added to the browse index and are searchable? Any pointers are most welcome.
Have you set up the cron job on the db server to update Zebra? Best -- Paul
Hi On the database server, I did not have zebra. My database server is a bare metal installation on operating system and MySQL and has no zebra instance running on it. Thought the zebra should be running on the Koha application server. Regards, Admire On Thu, May 2, 2019 at 6:27 PM Paul A <paul.a@navalmarinearchive.com> wrote:
Hi All
I am running an instance of Koha 18.11.03.000 on Debian 8.11 where both the application server and the Koha database where running on one server. My server was becoming overwhelmed so I decided to have a two-tier setup with the database running on another separate server by changing the <hostname>localhost</hostname in /etc/koha/sites/library/koha-conf.xml to the IP address of the database server and granting the relevant
On 2019-05-02 12:15 p.m., Admire Mutsikiwa wrote: privileges.
Everything seems to be going on well. However, newly added items and biblio records are not searchable on the catalogue pointing to a browse index-related issue. What should I do on a two-tier setup to ensure that newly added items are added to the browse index and are searchable? Any pointers are most welcome.
Have you set up the cron job on the db server to update Zebra?
Best -- Paul _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
On 2019-05-02 12:37 p.m., Admire Mutsikiwa wrote:
Hi On the database server, I did not have zebra. My database server is a bare metal installation on operating system and MySQL and has no zebra instance running on it. Thought the zebra should be running on the Koha application server.
You do say that you modded "koha-conf.xml to the IP address of the database server and granting the relevant privileges" and it sounds as though new db entries are being written. Perhaps it doesn't matter where Zebra is running (your setup, your choice), but it still sounds as though Zebra, through the "rebuild-zebra" script with the -z option (cron job, incremental / process_zebraqueue) is not fully functional. Have you changed the env vars to tell it where the db is located? Have you got any logged error entries? Can you do a full re-index? What happens, any errors?, when you run ./rebuild_zebra.pl -a -b -z -v &> /dev/null P.
Regards,
Admire
On Thu, May 2, 2019 at 6:27 PM Paul A <paul.a@navalmarinearchive.com <mailto:paul.a@navalmarinearchive.com>> wrote:
On 2019-05-02 12:15 p.m., Admire Mutsikiwa wrote: > Hi All > > I am running an instance of Koha 18.11.03.000 on Debian 8.11 where both > the application server and the Koha database where running on one server. > My server was becoming overwhelmed so I decided to have a two-tier setup > with the database running on another separate server by changing the > <hostname>localhost</hostname in /etc/koha/sites/library/koha-conf.xml to > the IP address of the database server and granting the relevant privileges. > Everything seems to be going on well. However, newly added items and > biblio records are not searchable on the catalogue pointing to a browse > index-related issue. What should I do on a two-tier setup to ensure that > newly added items are added to the browse index and are searchable? Any > pointers are most welcome.
Have you set up the cron job on the db server to update Zebra?
Best -- Paul _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha
participants (2)
-
Admire Mutsikiwa -
Paul A