A new request with request id 7253 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :

Title : Koha-devel Digest, Vol 202, Issue 20
Category :
Description :
Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Re: Elasticsearch not auto-updating after cataloguing
(Philippe Blouin)


----------------------------------------------------------------------

Message: 1
Date: Fri, 16 Sep 2022 16:01:02 -0400
From: Philippe Blouin <philippe.blouin@inlibro.com>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Elasticsearch not auto-updating after
    cataloguing
Message-ID: <d4356a29-e744-a85e-effc-7c43e3e8d9ae@inlibro.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello Thomas,

I followed your tip the last few days.  At this point I've spotted which
commit between 21 and 22 moved the reindexing to BackgroundJobs, and
when set up correctly (the worker), it does reindex indeed.

But if rabbitmq runs, then it fails.   The background_jobs service gets
the clue to look for job X: if connecte to MQ, it goes to the database
with a ->find()... and gets nothing.  If MQ is not running, it goes to
the database with a ->search() and process the jobs there with success.

*sigh*

So it is not a matter of Ubuntu version or remote vs local, but of a
combination of Koha version, worker and rabbitmq.

NOW, if I put a "sleep 2" in background_jobs_worker.pl, just before the
->find(), then it works.

Like if the Queue is faster than the Database ??!?!  Seems to me nothing
is put onto the queue, especially not an ID, without the database entry
being completed.


I have a feeling I'm deep into a rabbit (mq) hole, and I'm not seeing
straight.


Thanks a lot,


Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blouin@inLibro.com

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
On 2022-09-13 16:33, Thomas Klausner wrote:
> Hi!
>
> On Tue, Sep 13, 2022 at 02:58:49PM -0400, Philippe Blouin wrote:
>
>> Depends on the installation, but where background_jobs_worker.pl runs or not
>> makes not difference in where the cataloguing->indexing path works.
>>
>> It seems to always work when Koha runs on the same machine as ES, and not
>> otherwise.
> Is the remote ES exposed via https? Maybe you have slightly different
> Perls orMozilla::CA installation? Any errors in the logs?
>
> Which Koha Verion are you running? Are you sure both latpop and server
> run the same version?
>
> In the source code there is a param 'skip_record_index', which will
> prevent the immediate indexing after an edit (if I've skimmed the code
> correctly). Maybe that is set? Though I don't know when it would be set
> (by whom..)
>
> Greetings,
> domm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220916/b9c705eb/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


------------------------------

End of Koha-devel Digest, Vol 202, Issue 20
*******************************************


NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.