Re: [Koha] Background job / Staging MARC import stuck at 0%

[Cindy Murdock Ames]

Hi Anna,

Are you able to check your server for zombie processes?  (Hint: run "ps aux
|grep Z" from the command line or else run "top" and look at the end of the
Tasks line for the number of zombies.)

Since upgrading to 22.11 from 22.05 I've had an issue where the
background_jobs_worker.pl tasks would turn into zombie processes.  If all
the background job worker tasks become zombies then imports won't get
processed and it remains stuck at the "import queued" stage.  I've been
unable to identify the cause or a proper fix, but for the time being I've
made a hacky cron script that runs every minute checking for these zombies
and killing their parent process, which seems to restart the queue, but you
have to retry the upload (the original job remains in the queue with a
progress of "null").  Sorry I don't have a proper solution, I was just
curious if others were seeing this symptom.

Cindy

---
Cindy Murdock Ames
IT Services Director
Meadville Public Library | CCFLS
https://meadvillelibrary.org | https://ccfls.org




On Mon, May 29, 2023 at 11:06 PM Anna Shields  wrote:

> Michael,
>
> Did you ever have any luck resolving this?
>
> I'm having a similar issue in which my imports get stuck at 0% on the
> staging step. I, too, seem to have a functioning RabbitMQ, and none of the
> suggestions I saw in this thread seemed to make a difference.
>
> I'm now on v22.11.06-3, and updating hasn't seemed to make any difference,
> either.
>
> Anna
>
> On Tue, May 16, 2023 at 7:01 PM  wrote:
>
> > Hi Michael,
> >
> > Did you also restart some services after changing the script including
> > memcache?
> >
> > Sometimes it is necessary but not remember for this case.
> >
> > You should also look
> > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412
> >
> > Mengü Yazıcıoğlu
> > Devinim Yazılım Eğitim Danışmanlık
> > Reşit Galip Cad. No: 29/6
> > Çankaya/ANKARA
> >
> > Tel: (312) 446 86 68
> > Cep: (532) 701 90 27
> >
> > On 13.05.2023 16:21, Michael Brown wrote:
> > > I tried Mengü's suggestion of editing manage-marc-import.pl, to no
> > avail.
> > > Still hangs at enqueuement; no messages, no errors, simply hangs and
> > spins
> > > my CPU into a frenzy. Responses to George's message below:
> > >
> > > On Wed, May 10, 2023 at 8:34 AM George Veranis 
> > wrote:
> > >
> > >> Hi Michael,
> > >>
> > >> Could you check the following things:
> > >>
> > >> 1) if your rabbitmq-server is running ?
> > >>
> > > Yes.
> > >
> > >
> > >> 1.1) if yes, then check if the cluster of nodes in rabbit exist , the
> > >> command is:
> > >> rabbitmqctl cluster_status
> > >>
> > > Cluster status of node rabbit@kiko ...
> > > Basics
> > >
> > > Cluster name: rabbit@kiko
> > >
> > > Disk Nodes
> > > rabbit@kiko
> > >
> > > Running Nodes
> > > rabbit@kiko
> > >
> > > Versions
> > > rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2
> > >
> > > Maintenance status
> > >
> > > Node: rabbit@kiko, status: not under maintenance
> > >
> > > Alarms
> > >
> > > (none)
> > >
> > > Network Partitions
> > >
> > > (none)
> > >
> > > Listeners
> > >
> > > Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp,
> > purpose:
> > > STOMP
> > > Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
> > > purpose: inter-node and CLI tool communication
> > > Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp,
> purpose:
> > > AMQP 0-9-1 and AMQP 1.0
> > >
> > > Feature flags
> > >
> > > Flag: implicit_default_bindings, state: enabled
> > > Flag: maintenance_mode_status, state: enabled
> > > Flag: quorum_queue, state: enabled
> > > Flag: stream_queue, state: enabled
> > > Flag: user_limits, state: enabled
> > > Flag: virtual_host_metadata, state: enabled
> > >
> > >
> > >
> > >> 1.1.1) if not shows you something in json format you can try to start
> it
> > >> with command
> > >> rabbitmqctl start_app
> > >>
> > >> N/A, rabbitmq is already running.
> > >
> > >> 1.2 ) If no , start it and check the logs from your rabbitmq-server at
> > >> /var/log/r

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Hi Anna,

No, I still have not resolved this. I’ve tried all the suggestions everyone
has given throughout this thread and still no luck. If I do find an answer,
I’ll definitely post it.

The only requirement I have for using Koha is the ability to batch import
bib records from OCLC. Since it cannot do that one thing I require, I’ve
pretty much given up on it. I guess that’s my way of saying I’m not using
Koha anymore and so unless I end up with copious amounts of free time in
the future, I’m probably not going to futz much more with this.

Michael

On Mon, May 29, 2023 at 10:06 PM Anna Shields  wrote:

> Michael,
>
> Did you ever have any luck resolving this?
>
> I'm having a similar issue in which my imports get stuck at 0% on the
> staging step. I, too, seem to have a functioning RabbitMQ, and none of the
> suggestions I saw in this thread seemed to make a difference.
>
> I'm now on v22.11.06-3, and updating hasn't seemed to make any difference,
> either.
>
> Anna
>
> On Tue, May 16, 2023 at 7:01 PM  wrote:
>
> > Hi Michael,
> >
> > Did you also restart some services after changing the script including
> > memcache?
> >
> > Sometimes it is necessary but not remember for this case.
> >
> > You should also look
> > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412
> >
> > Mengü Yazıcıoğlu
> > Devinim Yazılım Eğitim Danışmanlık
> > Reşit Galip Cad. No: 29/6
> > Çankaya/ANKARA
> >
> > Tel: (312) 446 86 68
> > Cep: (532) 701 90 27
> >
> > On 13.05.2023 16:21, Michael Brown wrote:
> > > I tried Mengü's suggestion of editing manage-marc-import.pl, to no
> > avail.
> > > Still hangs at enqueuement; no messages, no errors, simply hangs and
> > spins
> > > my CPU into a frenzy. Responses to George's message below:
> > >
> > > On Wed, May 10, 2023 at 8:34 AM George Veranis 
> > wrote:
> > >
> > >> Hi Michael,
> > >>
> > >> Could you check the following things:
> > >>
> > >> 1) if your rabbitmq-server is running ?
> > >>
> > > Yes.
> > >
> > >
> > >> 1.1) if yes, then check if the cluster of nodes in rabbit exist , the
> > >> command is:
> > >> rabbitmqctl cluster_status
> > >>
> > > Cluster status of node rabbit@kiko ...
> > > Basics
> > >
> > > Cluster name: rabbit@kiko
> > >
> > > Disk Nodes
> > > rabbit@kiko
> > >
> > > Running Nodes
> > > rabbit@kiko
> > >
> > > Versions
> > > rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2
> > >
> > > Maintenance status
> > >
> > > Node: rabbit@kiko, status: not under maintenance
> > >
> > > Alarms
> > >
> > > (none)
> > >
> > > Network Partitions
> > >
> > > (none)
> > >
> > > Listeners
> > >
> > > Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp,
> > purpose:
> > > STOMP
> > > Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
> > > purpose: inter-node and CLI tool communication
> > > Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp,
> purpose:
> > > AMQP 0-9-1 and AMQP 1.0
> > >
> > > Feature flags
> > >
> > > Flag: implicit_default_bindings, state: enabled
> > > Flag: maintenance_mode_status, state: enabled
> > > Flag: quorum_queue, state: enabled
> > > Flag: stream_queue, state: enabled
> > > Flag: user_limits, state: enabled
> > > Flag: virtual_host_metadata, state: enabled
> > >
> > >
> > >
> > >> 1.1.1) if not shows you something in json format you can try to start
> it
> > >> with command
> > >> rabbitmqctl start_app
> > >>
> > >> N/A, rabbitmq is already running.
> > >
> > >> 1.2 ) If no , start it and check the logs from your rabbitmq-server at
> > >> /var/log/rabbitmq/ and check if the service is start it normally .
> > >>
> > >> N/A, rabbitmq is already running.
> > >
> > >> 2) check the worker-output.log on your koha if koha write there
> > something
> > >> and have koha connection with rabbit server .
> > >>
> > >> I cannot find a file called "worker-output.log" anywhere in my Alma
> > > installation.
> > >
> > >
> > >> Best Regards,
> > >> George
> > >>
> 

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Katrin Fischer]

Hi Anna,

we recently saw the import stuck at 'orange' when the background job for
processing the jobs was missing. In adminstration > jobs the import
remained with status 'new' indefinitely. In our case a restart of
koha-common fixed it.

Hope this helps,

Katrin

On 30.05.23 05:05, Anna Shields wrote:

Michael,

Did you ever have any luck resolving this?

I'm having a similar issue in which my imports get stuck at 0% on the
staging step. I, too, seem to have a functioning RabbitMQ, and none of the
suggestions I saw in this thread seemed to make a difference.

I'm now on v22.11.06-3, and updating hasn't seemed to make any difference,
either.

Anna

On Tue, May 16, 2023 at 7:01 PM  wrote:


Hi Michael,

Did you also restart some services after changing the script including
memcache?

Sometimes it is necessary but not remember for this case.

You should also look
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412

Mengü Yazıcıoğlu
Devinim Yazılım Eğitim Danışmanlık
Reşit Galip Cad. No: 29/6
Çankaya/ANKARA

Tel: (312) 446 86 68
Cep: (532) 701 90 27

On 13.05.2023 16:21, Michael Brown wrote:

I tried Mengü's suggestion of editing manage-marc-import.pl, to no

avail.

Still hangs at enqueuement; no messages, no errors, simply hangs and

spins

my CPU into a frenzy. Responses to George's message below:

On Wed, May 10, 2023 at 8:34 AM George Veranis 

wrote:

Hi Michael,

Could you check the following things:

1) if your rabbitmq-server is running ?


Yes.



1.1) if yes, then check if the cluster of nodes in rabbit exist , the
command is:
rabbitmqctl cluster_status


Cluster status of node rabbit@kiko ...
Basics

Cluster name: rabbit@kiko

Disk Nodes
rabbit@kiko

Running Nodes
rabbit@kiko

Versions
rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2

Maintenance status

Node: rabbit@kiko, status: not under maintenance

Alarms

(none)

Network Partitions

(none)

Listeners

Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp,

purpose:

STOMP
Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
purpose: inter-node and CLI tool communication
Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp, purpose:
AMQP 0-9-1 and AMQP 1.0

Feature flags

Flag: implicit_default_bindings, state: enabled
Flag: maintenance_mode_status, state: enabled
Flag: quorum_queue, state: enabled
Flag: stream_queue, state: enabled
Flag: user_limits, state: enabled
Flag: virtual_host_metadata, state: enabled




1.1.1) if not shows you something in json format you can try to start it
with command
rabbitmqctl start_app

N/A, rabbitmq is already running.
1.2 ) If no , start it and check the logs from your rabbitmq-server at
/var/log/rabbitmq/ and check if the service is start it normally .

N/A, rabbitmq is already running.
2) check the worker-output.log on your koha if koha write there

something

and have koha connection with rabbit server .

I cannot find a file called "worker-output.log" anywhere in my Alma

installation.



Best Regards,
George


-Original Message-
From: Koha  On Behalf Of Michael Brown
Sent: Wednesday, May 10, 2023 3:50 PM
To: Cindy Murdock Ames 
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%

   Hi Cindy, apologies for the double-response: I had unsubscribed from

the

koha list so my response didn't get added to the thread. I wanted to

remedy

that, and also say that, because I had unsubscribed, I missed Mengü's
suggestion of updating manage-marc-import.pl. I am eager to try that

fix

and will report back later today or tomorrow with my findings. Here's my
original response to Cindy before re-subscribing to to the koha list:

Yes, my koha-conf.xml does contain that block because I added it during
the initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in

Koha

22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my
cpu through the roof until I navigate away from that page. I've gotten

one

off-list suggestion that upgrading to the newest Koha fixes the problem.
Unfortunately for me, I don't really have time for that right now, so I
have (at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue, May 9, 2023 at 4:40 PM Michael Brown 
wrote:


Hi Cindy,

Yes, my koha-conf.xml does contain that block because I added it
during the initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in
Koha
22.11 the way I could in Koha 22.05. The enqueuement hangs and sends
my cpu through the roof until I navigate away from that page. I've
gotten one off-list suggestion that upgrading to the newest Koha fixes

the problem.

Unfortunately for me, I don't really have time for that right now, so
I have (at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Himanshu Aggarwal]

From where are you importing the files?

On Tue, May 30, 2023 at 8:36 AM Anna Shields  wrote:

> Michael,
>
> Did you ever have any luck resolving this?
>
> I'm having a similar issue in which my imports get stuck at 0% on the
> staging step. I, too, seem to have a functioning RabbitMQ, and none of the
> suggestions I saw in this thread seemed to make a difference.
>
> I'm now on v22.11.06-3, and updating hasn't seemed to make any difference,
> either.
>
> Anna
>
> On Tue, May 16, 2023 at 7:01 PM  wrote:
>
> > Hi Michael,
> >
> > Did you also restart some services after changing the script including
> > memcache?
> >
> > Sometimes it is necessary but not remember for this case.
> >
> > You should also look
> > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412
> >
> > Mengü Yazıcıoğlu
> > Devinim Yazılım Eğitim Danışmanlık
> > Reşit Galip Cad. No: 29/6
> > Çankaya/ANKARA
> >
> > Tel: (312) 446 86 68
> > Cep: (532) 701 90 27
> >
> > On 13.05.2023 16:21, Michael Brown wrote:
> > > I tried Mengü's suggestion of editing manage-marc-import.pl, to no
> > avail.
> > > Still hangs at enqueuement; no messages, no errors, simply hangs and
> > spins
> > > my CPU into a frenzy. Responses to George's message below:
> > >
> > > On Wed, May 10, 2023 at 8:34 AM George Veranis 
> > wrote:
> > >
> > >> Hi Michael,
> > >>
> > >> Could you check the following things:
> > >>
> > >> 1) if your rabbitmq-server is running ?
> > >>
> > > Yes.
> > >
> > >
> > >> 1.1) if yes, then check if the cluster of nodes in rabbit exist , the
> > >> command is:
> > >> rabbitmqctl cluster_status
> > >>
> > > Cluster status of node rabbit@kiko ...
> > > Basics
> > >
> > > Cluster name: rabbit@kiko
> > >
> > > Disk Nodes
> > > rabbit@kiko
> > >
> > > Running Nodes
> > > rabbit@kiko
> > >
> > > Versions
> > > rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2
> > >
> > > Maintenance status
> > >
> > > Node: rabbit@kiko, status: not under maintenance
> > >
> > > Alarms
> > >
> > > (none)
> > >
> > > Network Partitions
> > >
> > > (none)
> > >
> > > Listeners
> > >
> > > Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp,
> > purpose:
> > > STOMP
> > > Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
> > > purpose: inter-node and CLI tool communication
> > > Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp,
> purpose:
> > > AMQP 0-9-1 and AMQP 1.0
> > >
> > > Feature flags
> > >
> > > Flag: implicit_default_bindings, state: enabled
> > > Flag: maintenance_mode_status, state: enabled
> > > Flag: quorum_queue, state: enabled
> > > Flag: stream_queue, state: enabled
> > > Flag: user_limits, state: enabled
> > > Flag: virtual_host_metadata, state: enabled
> > >
> > >
> > >
> > >> 1.1.1) if not shows you something in json format you can try to start
> it
> > >> with command
> > >> rabbitmqctl start_app
> > >>
> > >> N/A, rabbitmq is already running.
> > >
> > >> 1.2 ) If no , start it and check the logs from your rabbitmq-server at
> > >> /var/log/rabbitmq/ and check if the service is start it normally .
> > >>
> > >> N/A, rabbitmq is already running.
> > >
> > >> 2) check the worker-output.log on your koha if koha write there
> > something
> > >> and have koha connection with rabbit server .
> > >>
> > >> I cannot find a file called "worker-output.log" anywhere in my Alma
> > > installation.
> > >
> > >
> > >> Best Regards,
> > >> George
> > >>
> > >>
> > >> -Original Message-
> > >> From: Koha  On Behalf Of Michael
> Brown
> > >> Sent: Wednesday, May 10, 2023 3:50 PM
> > >> To: Cindy Murdock Ames 
> > >> Cc: koha@lists.katipo.co.nz
> > >> Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%
> > >>
> > >>   Hi Cindy, apologies for the double-response: I had unsubscribed from
> > the
> > >> koha list s

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Anna Shields]

Michael,

Did you ever have any luck resolving this?

I'm having a similar issue in which my imports get stuck at 0% on the
staging step. I, too, seem to have a functioning RabbitMQ, and none of the
suggestions I saw in this thread seemed to make a difference.

I'm now on v22.11.06-3, and updating hasn't seemed to make any difference,
either.

Anna

On Tue, May 16, 2023 at 7:01 PM  wrote:

> Hi Michael,
>
> Did you also restart some services after changing the script including
> memcache?
>
> Sometimes it is necessary but not remember for this case.
>
> You should also look
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412
>
> Mengü Yazıcıoğlu
> Devinim Yazılım Eğitim Danışmanlık
> Reşit Galip Cad. No: 29/6
> Çankaya/ANKARA
>
> Tel: (312) 446 86 68
> Cep: (532) 701 90 27
>
> On 13.05.2023 16:21, Michael Brown wrote:
> > I tried Mengü's suggestion of editing manage-marc-import.pl, to no
> avail.
> > Still hangs at enqueuement; no messages, no errors, simply hangs and
> spins
> > my CPU into a frenzy. Responses to George's message below:
> >
> > On Wed, May 10, 2023 at 8:34 AM George Veranis 
> wrote:
> >
> >> Hi Michael,
> >>
> >> Could you check the following things:
> >>
> >> 1) if your rabbitmq-server is running ?
> >>
> > Yes.
> >
> >
> >> 1.1) if yes, then check if the cluster of nodes in rabbit exist , the
> >> command is:
> >> rabbitmqctl cluster_status
> >>
> > Cluster status of node rabbit@kiko ...
> > Basics
> >
> > Cluster name: rabbit@kiko
> >
> > Disk Nodes
> > rabbit@kiko
> >
> > Running Nodes
> > rabbit@kiko
> >
> > Versions
> > rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2
> >
> > Maintenance status
> >
> > Node: rabbit@kiko, status: not under maintenance
> >
> > Alarms
> >
> > (none)
> >
> > Network Partitions
> >
> > (none)
> >
> > Listeners
> >
> > Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp,
> purpose:
> > STOMP
> > Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
> > purpose: inter-node and CLI tool communication
> > Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp, purpose:
> > AMQP 0-9-1 and AMQP 1.0
> >
> > Feature flags
> >
> > Flag: implicit_default_bindings, state: enabled
> > Flag: maintenance_mode_status, state: enabled
> > Flag: quorum_queue, state: enabled
> > Flag: stream_queue, state: enabled
> > Flag: user_limits, state: enabled
> > Flag: virtual_host_metadata, state: enabled
> >
> >
> >
> >> 1.1.1) if not shows you something in json format you can try to start it
> >> with command
> >> rabbitmqctl start_app
> >>
> >> N/A, rabbitmq is already running.
> >
> >> 1.2 ) If no , start it and check the logs from your rabbitmq-server at
> >> /var/log/rabbitmq/ and check if the service is start it normally .
> >>
> >> N/A, rabbitmq is already running.
> >
> >> 2) check the worker-output.log on your koha if koha write there
> something
> >> and have koha connection with rabbit server .
> >>
> >> I cannot find a file called "worker-output.log" anywhere in my Alma
> > installation.
> >
> >
> >> Best Regards,
> >> George
> >>
> >>
> >> -Original Message-
> >> From: Koha  On Behalf Of Michael Brown
> >> Sent: Wednesday, May 10, 2023 3:50 PM
> >> To: Cindy Murdock Ames 
> >> Cc: koha@lists.katipo.co.nz
> >> Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%
> >>
> >>   Hi Cindy, apologies for the double-response: I had unsubscribed from
> the
> >> koha list so my response didn't get added to the thread. I wanted to
> remedy
> >> that, and also say that, because I had unsubscribed, I missed Mengü's
> >> suggestion of updating manage-marc-import.pl. I am eager to try that
> fix
> >> and will report back later today or tomorrow with my findings. Here's my
> >> original response to Cindy before re-subscribing to to the koha list:
> >>
> >> Yes, my koha-conf.xml does contain that block because I added it during
> >> the initial setup. (You're right, it wasn't there originally.)
> >>
> >> However, it doesn't help; I still cannot import batch bib records in
> Koha
> >> 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Mengu Yazicioglu]

Hi Michael,

Did you also restart some services after changing the script including 
memcache?


Sometimes it is necessary but not remember for this case.

You should also look 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412


Mengü Yazıcıoğlu
Devinim Yazılım Eğitim Danışmanlık
Reşit Galip Cad. No: 29/6
Çankaya/ANKARA

Tel: (312) 446 86 68
Cep: (532) 701 90 27

On 13.05.2023 16:21, Michael Brown wrote:

I tried Mengü's suggestion of editing manage-marc-import.pl, to no avail.
Still hangs at enqueuement; no messages, no errors, simply hangs and spins
my CPU into a frenzy. Responses to George's message below:

On Wed, May 10, 2023 at 8:34 AM George Veranis  wrote:


Hi Michael,

Could you check the following things:

1) if your rabbitmq-server is running ?


Yes.



1.1) if yes, then check if the cluster of nodes in rabbit exist , the
command is:
rabbitmqctl cluster_status


Cluster status of node rabbit@kiko ...
Basics

Cluster name: rabbit@kiko

Disk Nodes
rabbit@kiko

Running Nodes
rabbit@kiko

Versions
rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2

Maintenance status

Node: rabbit@kiko, status: not under maintenance

Alarms

(none)

Network Partitions

(none)

Listeners

Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp, purpose:
STOMP
Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
purpose: inter-node and CLI tool communication
Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp, purpose:
AMQP 0-9-1 and AMQP 1.0

Feature flags

Flag: implicit_default_bindings, state: enabled
Flag: maintenance_mode_status, state: enabled
Flag: quorum_queue, state: enabled
Flag: stream_queue, state: enabled
Flag: user_limits, state: enabled
Flag: virtual_host_metadata, state: enabled




1.1.1) if not shows you something in json format you can try to start it
with command
rabbitmqctl start_app

N/A, rabbitmq is already running.



1.2 ) If no , start it and check the logs from your rabbitmq-server at
/var/log/rabbitmq/ and check if the service is start it normally .

N/A, rabbitmq is already running.



2) check the worker-output.log on your koha if koha write there something
and have koha connection with rabbit server .

I cannot find a file called "worker-output.log" anywhere in my Alma

installation.



Best Regards,
George


-Original Message-
From: Koha  On Behalf Of Michael Brown
Sent: Wednesday, May 10, 2023 3:50 PM
To: Cindy Murdock Ames 
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%

  Hi Cindy, apologies for the double-response: I had unsubscribed from the
koha list so my response didn't get added to the thread. I wanted to remedy
that, and also say that, because I had unsubscribed, I missed Mengü's
suggestion of updating manage-marc-import.pl. I am eager to try that fix
and will report back later today or tomorrow with my findings. Here's my
original response to Cindy before re-subscribing to to the koha list:

Yes, my koha-conf.xml does contain that block because I added it during
the initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in Koha
22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my
cpu through the roof until I navigate away from that page. I've gotten one
off-list suggestion that upgrading to the newest Koha fixes the problem.
Unfortunately for me, I don't really have time for that right now, so I
have (at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue, May 9, 2023 at 4:40 PM Michael Brown 
wrote:


Hi Cindy,

Yes, my koha-conf.xml does contain that block because I added it
during the initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in
Koha
22.11 the way I could in Koha 22.05. The enqueuement hangs and sends
my cpu through the roof until I navigate away from that page. I've
gotten one off-list suggestion that upgrading to the newest Koha fixes

the problem.

Unfortunately for me, I don't really have time for that right now, so
I have (at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames 
wrote:


Hi Michael,

Can you confirm your koha-conf.xml contains a message broker section,
like this?


localhost
61613
guest
guest

  

I had the same problem after upgrading from 22.05 to 22.11; I'm
guessing
22.05 must have had some defaults set in the code that allowed the
message broker to start automatically without this section whereas

22.11 must not.

I was missing this section and added it and was able to complete
imports after restarting Koha.

I'm still having the issue with zombie background jobs (I'm afraid to
test rolling back the code on a production server) but I made a hacky
bash script to run as a cron job to chec

Re: [Koha] Background job / Staging MARC import stuck at 0%

[George Veranis]

The “worker-output.log” is normally under /var/log/koha/instance_name_of_koha/

 

From: Michael Brown  
Sent: Saturday, May 13, 2023 4:21 PM
To: George Veranis 
Cc: Cindy Murdock Ames ; koha@lists.katipo.co.nz
Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%

 

I tried Mengü's suggestion of editing manage-marc-import.pl 
<http://manage-marc-import.pl> , to no avail. Still hangs at enqueuement; no 
messages, no errors, simply hangs and spins my CPU into a frenzy. Responses to 
George's message below:

 

On Wed, May 10, 2023 at 8:34 AM George Veranis mailto:gvera...@dataly.gr> > wrote:

Hi Michael, 

Could you check the following things: 

1) if your rabbitmq-server is running ? 

 

Yes.

 

1.1) if yes, then check if the cluster of nodes in rabbit exist , the command 
is: 
rabbitmqctl cluster_status

 

Cluster status of node rabbit@kiko ...
Basics

Cluster name: rabbit@kiko

Disk Nodes
rabbit@kiko

Running Nodes
rabbit@kiko

Versions
rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2

Maintenance status

Node: rabbit@kiko, status: not under maintenance

Alarms

(none)

Network Partitions

(none)

Listeners

Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp, purpose: STOMP
Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering, purpose: 
inter-node and CLI tool communication
Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp, purpose: AMQP 
0-9-1 and AMQP 1.0

Feature flags

Flag: implicit_default_bindings, state: enabled
Flag: maintenance_mode_status, state: enabled
Flag: quorum_queue, state: enabled
Flag: stream_queue, state: enabled
Flag: user_limits, state: enabled
Flag: virtual_host_metadata, state: enabled

 

 

1.1.1) if not shows you something in json format you can try to start it with 
command 
rabbitmqctl start_app 

N/A, rabbitmq is already running.

 

1.2 ) If no , start it and check the logs from your rabbitmq-server at 
/var/log/rabbitmq/ and check if the service is start it normally . 

N/A, rabbitmq is already running.

 

2) check the worker-output.log on your koha if koha write there something and 
have koha connection with rabbit server . 

I cannot find a file called "worker-output.log" anywhere in my Alma 
installation.

 

Best Regards, 
George 


-Original Message-
From: Koha mailto:koha-boun...@lists.katipo.co.nz> > On Behalf Of Michael Brown
Sent: Wednesday, May 10, 2023 3:50 PM
To: Cindy Murdock Ames mailto:cmurd...@ccfls.org> >
Cc: koha@lists.katipo.co.nz <mailto:koha@lists.katipo.co.nz> 
Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%

 Hi Cindy, apologies for the double-response: I had unsubscribed from the koha 
list so my response didn't get added to the thread. I wanted to remedy that, 
and also say that, because I had unsubscribed, I missed Mengü's suggestion of 
updating manage-marc-import.pl <http://manage-marc-import.pl> . I am eager to 
try that fix and will report back later today or tomorrow with my findings. 
Here's my original response to Cindy before re-subscribing to to the koha list:

Yes, my koha-conf.xml does contain that block because I added it during the 
initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in Koha
22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu 
through the roof until I navigate away from that page. I've gotten one off-list 
suggestion that upgrading to the newest Koha fixes the problem.
Unfortunately for me, I don't really have time for that right now, so I have 
(at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue, May 9, 2023 at 4:40 PM Michael Brown mailto:michael8r...@gmail.com> > wrote:

> Hi Cindy,
>
> Yes, my koha-conf.xml does contain that block because I added it 
> during the initial setup. (You're right, it wasn't there originally.)
>
> However, it doesn't help; I still cannot import batch bib records in 
> Koha
> 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends 
> my cpu through the roof until I navigate away from that page. I've 
> gotten one off-list suggestion that upgrading to the newest Koha fixes the 
> problem.
> Unfortunately for me, I don't really have time for that right now, so 
> I have (at least temporarily) abandoned my efforts with Koha.
>
> Thanks for your suggestion!
>
> Bests,
> Michael
>
> On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames  <mailto:cmurd...@ccfls.org> >
> wrote:
>
>> Hi Michael,
>>
>> Can you confirm your koha-conf.xml contains a message broker section, 
>> like this?
>>
>> 
>>localhost
>>61613
>>guest
>>guest
>>
>>  
>>
>> I had the same problem after upgrading from 22.05 to 22.11; I'm 
&

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

I tried Mengü's suggestion of editing manage-marc-import.pl, to no avail.
Still hangs at enqueuement; no messages, no errors, simply hangs and spins
my CPU into a frenzy. Responses to George's message below:

On Wed, May 10, 2023 at 8:34 AM George Veranis  wrote:

> Hi Michael,
>
> Could you check the following things:
>
> 1) if your rabbitmq-server is running ?
>

Yes.


> 1.1) if yes, then check if the cluster of nodes in rabbit exist , the
> command is:
> rabbitmqctl cluster_status
>

Cluster status of node rabbit@kiko ...
Basics

Cluster name: rabbit@kiko

Disk Nodes
rabbit@kiko

Running Nodes
rabbit@kiko

Versions
rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2

Maintenance status

Node: rabbit@kiko, status: not under maintenance

Alarms

(none)

Network Partitions

(none)

Listeners

Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp, purpose:
STOMP
Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering,
purpose: inter-node and CLI tool communication
Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp, purpose:
AMQP 0-9-1 and AMQP 1.0

Feature flags

Flag: implicit_default_bindings, state: enabled
Flag: maintenance_mode_status, state: enabled
Flag: quorum_queue, state: enabled
Flag: stream_queue, state: enabled
Flag: user_limits, state: enabled
Flag: virtual_host_metadata, state: enabled



> 1.1.1) if not shows you something in json format you can try to start it
> with command
> rabbitmqctl start_app
>
> N/A, rabbitmq is already running.


> 1.2 ) If no , start it and check the logs from your rabbitmq-server at
> /var/log/rabbitmq/ and check if the service is start it normally .
>
> N/A, rabbitmq is already running.


> 2) check the worker-output.log on your koha if koha write there something
> and have koha connection with rabbit server .
>
> I cannot find a file called "worker-output.log" anywhere in my Alma
installation.


> Best Regards,
> George
>
>
> -Original Message-
> From: Koha  On Behalf Of Michael Brown
> Sent: Wednesday, May 10, 2023 3:50 PM
> To: Cindy Murdock Ames 
> Cc: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%
>
>  Hi Cindy, apologies for the double-response: I had unsubscribed from the
> koha list so my response didn't get added to the thread. I wanted to remedy
> that, and also say that, because I had unsubscribed, I missed Mengü's
> suggestion of updating manage-marc-import.pl. I am eager to try that fix
> and will report back later today or tomorrow with my findings. Here's my
> original response to Cindy before re-subscribing to to the koha list:
>
> Yes, my koha-conf.xml does contain that block because I added it during
> the initial setup. (You're right, it wasn't there originally.)
>
> However, it doesn't help; I still cannot import batch bib records in Koha
> 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my
> cpu through the roof until I navigate away from that page. I've gotten one
> off-list suggestion that upgrading to the newest Koha fixes the problem.
> Unfortunately for me, I don't really have time for that right now, so I
> have (at least temporarily) abandoned my efforts with Koha.
>
> Thanks for your suggestion!
>
> Bests,
> Michael
>
> On Tue, May 9, 2023 at 4:40 PM Michael Brown 
> wrote:
>
> > Hi Cindy,
> >
> > Yes, my koha-conf.xml does contain that block because I added it
> > during the initial setup. (You're right, it wasn't there originally.)
> >
> > However, it doesn't help; I still cannot import batch bib records in
> > Koha
> > 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends
> > my cpu through the roof until I navigate away from that page. I've
> > gotten one off-list suggestion that upgrading to the newest Koha fixes
> the problem.
> > Unfortunately for me, I don't really have time for that right now, so
> > I have (at least temporarily) abandoned my efforts with Koha.
> >
> > Thanks for your suggestion!
> >
> > Bests,
> > Michael
> >
> > On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames 
> > wrote:
> >
> >> Hi Michael,
> >>
> >> Can you confirm your koha-conf.xml contains a message broker section,
> >> like this?
> >>
> >> 
> >>localhost
> >>61613
> >>guest
> >>guest
> >>
> >>  
> >>
> >> I had the same problem after upgrading from 22.05 to 22.11; I'm
> >> guessing
> >> 22.05 must have had some defaults set in the code that allowed the
> >> message broker to start automatically without this section whereas
&

Re: [Koha] Background job / Staging MARC import stuck at 0%

[George Veranis]

Hi Michael, 

Could you check the following things: 

1) if your rabbitmq-server is running ? 
1.1) if yes, then check if the cluster of nodes in rabbit exist , the command 
is: 
rabbitmqctl cluster_status

1.1.1) if not shows you something in json format you can try to start it with 
command 
rabbitmqctl start_app 

1.2 ) If no , start it and check the logs from your rabbitmq-server at 
/var/log/rabbitmq/ and check if the service is start it normally . 

2) check the worker-output.log on your koha if koha write there something and 
have koha connection with rabbit server . 

Best Regards, 
George 


-Original Message-
From: Koha  On Behalf Of Michael Brown
Sent: Wednesday, May 10, 2023 3:50 PM
To: Cindy Murdock Ames 
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Background job / Staging MARC import stuck at 0%

 Hi Cindy, apologies for the double-response: I had unsubscribed from the koha 
list so my response didn't get added to the thread. I wanted to remedy that, 
and also say that, because I had unsubscribed, I missed Mengü's suggestion of 
updating manage-marc-import.pl. I am eager to try that fix and will report back 
later today or tomorrow with my findings. Here's my original response to Cindy 
before re-subscribing to to the koha list:

Yes, my koha-conf.xml does contain that block because I added it during the 
initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in Koha
22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu 
through the roof until I navigate away from that page. I've gotten one off-list 
suggestion that upgrading to the newest Koha fixes the problem.
Unfortunately for me, I don't really have time for that right now, so I have 
(at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue, May 9, 2023 at 4:40 PM Michael Brown  wrote:

> Hi Cindy,
>
> Yes, my koha-conf.xml does contain that block because I added it 
> during the initial setup. (You're right, it wasn't there originally.)
>
> However, it doesn't help; I still cannot import batch bib records in 
> Koha
> 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends 
> my cpu through the roof until I navigate away from that page. I've 
> gotten one off-list suggestion that upgrading to the newest Koha fixes the 
> problem.
> Unfortunately for me, I don't really have time for that right now, so 
> I have (at least temporarily) abandoned my efforts with Koha.
>
> Thanks for your suggestion!
>
> Bests,
> Michael
>
> On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames 
> wrote:
>
>> Hi Michael,
>>
>> Can you confirm your koha-conf.xml contains a message broker section, 
>> like this?
>>
>> 
>>localhost
>>61613
>>guest
>>guest
>>
>>  
>>
>> I had the same problem after upgrading from 22.05 to 22.11; I'm 
>> guessing
>> 22.05 must have had some defaults set in the code that allowed the 
>> message broker to start automatically without this section whereas 22.11 
>> must not.
>> I was missing this section and added it and was able to complete 
>> imports after restarting Koha.
>>
>> I'm still having the issue with zombie background jobs (I'm afraid to 
>> test rolling back the code on a production server) but I made a hacky 
>> bash script to run as a cron job to check for them and kill them off 
>> so at least our staff can do batch imports without issue, but that's another 
>> matter.
>>
>> HTH!
>> Cindy
>>
>>
>> ---
>> Cindy Murdock Ames
>> IT Services Director
>> Meadville Public Library | CCFLS
>> https://meadvillelibrary.org | https://ccfls.org
>>
>> Please report tech support issues in Mantis:  
>> https://mantis.ccfls.org
>>
>>
>> On Thu, Mar 2, 2023 at 8:51 AM Michael Brown 
>> wrote:
>>
>>> Greetings:
>>>
>>> My name is Michael Brown and I am a professional cataloger and 
>>> SirsiDynix System Admin at the Texas State Library & Archives in 
>>> Austin (20+ years now). I have been using Koha on Arch Linux in my 
>>> home library for about a year now. I am migrating my home server to 
>>> AlmaLinux and I'm having a problem.
>>>
>>> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a 
>>> MARC file for import gets stuck at 0%. On screen, I am able to 
>>> select the file for import (bib.mrc), review the profile options 
>>> (but I don't change any defaults), and then click on "Stage for 
>>> import" at the bottom. Next scr

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

 Hi Cindy, apologies for the double-response: I had unsubscribed from the
koha list so my response didn't get added to the thread. I wanted to remedy
that, and also say that, because I had unsubscribed, I missed Mengü's
suggestion of updating manage-marc-import.pl. I am eager to try that fix
and will report back later today or tomorrow with my findings. Here's my
original response to Cindy before re-subscribing to to the koha list:

Yes, my koha-conf.xml does contain that block because I added it during the
initial setup. (You're right, it wasn't there originally.)

However, it doesn't help; I still cannot import batch bib records in Koha
22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu
through the roof until I navigate away from that page. I've gotten one
off-list suggestion that upgrading to the newest Koha fixes the problem.
Unfortunately for me, I don't really have time for that right now, so I
have (at least temporarily) abandoned my efforts with Koha.

Thanks for your suggestion!

Bests,
Michael

On Tue, May 9, 2023 at 4:40 PM Michael Brown  wrote:

> Hi Cindy,
>
> Yes, my koha-conf.xml does contain that block because I added it during
> the initial setup. (You're right, it wasn't there originally.)
>
> However, it doesn't help; I still cannot import batch bib records in Koha
> 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu
> through the roof until I navigate away from that page. I've gotten one
> off-list suggestion that upgrading to the newest Koha fixes the problem.
> Unfortunately for me, I don't really have time for that right now, so I
> have (at least temporarily) abandoned my efforts with Koha.
>
> Thanks for your suggestion!
>
> Bests,
> Michael
>
> On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames 
> wrote:
>
>> Hi Michael,
>>
>> Can you confirm your koha-conf.xml contains a message broker section,
>> like this?
>>
>> 
>>localhost
>>61613
>>guest
>>guest
>>
>>  
>>
>> I had the same problem after upgrading from 22.05 to 22.11; I'm guessing
>> 22.05 must have had some defaults set in the code that allowed the message
>> broker to start automatically without this section whereas 22.11 must not.
>> I was missing this section and added it and was able to complete imports
>> after restarting Koha.
>>
>> I'm still having the issue with zombie background jobs (I'm afraid to
>> test rolling back the code on a production server) but I made a hacky bash
>> script to run as a cron job to check for them and kill them off so at least
>> our staff can do batch imports without issue, but that's another matter.
>>
>> HTH!
>> Cindy
>>
>>
>> ---
>> Cindy Murdock Ames
>> IT Services Director
>> Meadville Public Library | CCFLS
>> https://meadvillelibrary.org | https://ccfls.org
>>
>> Please report tech support issues in Mantis:  https://mantis.ccfls.org
>>
>>
>> On Thu, Mar 2, 2023 at 8:51 AM Michael Brown 
>> wrote:
>>
>>> Greetings:
>>>
>>> My name is Michael Brown and I am a professional cataloger and SirsiDynix
>>> System Admin at the Texas State Library & Archives in Austin (20+ years
>>> now). I have been using Koha on Arch Linux in my home library for about a
>>> year now. I am migrating my home server to AlmaLinux and I'm having a
>>> problem.
>>>
>>> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
>>> file for import gets stuck at 0%. On screen, I am able to select the file
>>> for import (bib.mrc), review the profile options (but I don't change any
>>> defaults), and then click on "Stage for import" at the bottom. Next
>>> screen
>>> reads:
>>>
>>> The job has been enqueued! It will be processed as soon as possible.
>>> 0%
>>> View detail of the enqueued job
>>>
>>> After a few seconds, it changes to (and then hangs at):
>>>
>>> The job has been enqueued! It will be processed as soon as possible.
>>> 0% Not started
>>> View detail of the enqueued job
>>>
>>> Clicking on "View detail of the enqueued job" I see:
>>>
>>> Details of job #22
>>>
>>> Job ID: 22
>>> Status:New
>>> Progress:0 / 0
>>> Type:Staged MARC records for import
>>> Queued:03/02/2023 05:42
>>> Started:
>>> Ended:
>>>
>>> Report
>>> Detailed messages
>>> Return to the job list
>>>
>>> The corresponding entry in mariadb is:
>>>
>>> id 22
>>> status new
>>> progress NULL
>>> size 0
>>> borrowernumber 1
>>> type stage_marc_for_import
>>> queue Name of the queue the job is sent to long_tasks
>>> data {"encoding":"UTF-8","comments":"","basket_id":null...
>>> context JSON-serialized context information for the job
>>> {"flags":1,"branch":"ALMA","interface":"intranet",...
>>> enqueued_on 2023-03-02 05:42:33
>>> started_on NULL
>>> ended_on NULL
>>>
>>> (If you need to see the full entries for "data" and "context", please let
>>> me know.)
>>>
>>> tmp, koha_upload, and lock directories have been tweaked and fine tuned.

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Cindy Murdock Ames]

Hi Michael,

Can you confirm your koha-conf.xml contains a message broker section, like
this?


   localhost
   61613
   guest
   guest
   
 

I had the same problem after upgrading from 22.05 to 22.11; I'm guessing
22.05 must have had some defaults set in the code that allowed the message
broker to start automatically without this section whereas 22.11 must not.
I was missing this section and added it and was able to complete imports
after restarting Koha.

I'm still having the issue with zombie background jobs (I'm afraid to test
rolling back the code on a production server) but I made a hacky bash
script to run as a cron job to check for them and kill them off so at least
our staff can do batch imports without issue, but that's another matter.

HTH!
Cindy


---
Cindy Murdock Ames
IT Services Director
Meadville Public Library | CCFLS
https://meadvillelibrary.org | https://ccfls.org

Please report tech support issues in Mantis:  https://mantis.ccfls.org


On Thu, Mar 2, 2023 at 8:51 AM Michael Brown  wrote:

> Greetings:
>
> My name is Michael Brown and I am a professional cataloger and SirsiDynix
> System Admin at the Texas State Library & Archives in Austin (20+ years
> now). I have been using Koha on Arch Linux in my home library for about a
> year now. I am migrating my home server to AlmaLinux and I'm having a
> problem.
>
> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
> file for import gets stuck at 0%. On screen, I am able to select the file
> for import (bib.mrc), review the profile options (but I don't change any
> defaults), and then click on "Stage for import" at the bottom. Next screen
> reads:
>
> The job has been enqueued! It will be processed as soon as possible.
> 0%
> View detail of the enqueued job
>
> After a few seconds, it changes to (and then hangs at):
>
> The job has been enqueued! It will be processed as soon as possible.
> 0% Not started
> View detail of the enqueued job
>
> Clicking on "View detail of the enqueued job" I see:
>
> Details of job #22
>
> Job ID: 22
> Status:New
> Progress:0 / 0
> Type:Staged MARC records for import
> Queued:03/02/2023 05:42
> Started:
> Ended:
>
> Report
> Detailed messages
> Return to the job list
>
> The corresponding entry in mariadb is:
>
> id 22
> status new
> progress NULL
> size 0
> borrowernumber 1
> type stage_marc_for_import
> queue Name of the queue the job is sent to long_tasks
> data {"encoding":"UTF-8","comments":"","basket_id":null...
> context JSON-serialized context information for the job
> {"flags":1,"branch":"ALMA","interface":"intranet",...
> enqueued_on 2023-03-02 05:42:33
> started_on NULL
> ended_on NULL
>
> (If you need to see the full entries for "data" and "context", please let
> me know.)
>
> tmp, koha_upload, and lock directories have been tweaked and fine tuned. I
> was getting early warnings about them not being set in koha-conf.xml so I
> created them (and set correct permissions) and I can see the uploaded file
> (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
> actual upload function appears to be working.
>
> I am getting no apache errors and no other on-screen diagnostics.
>
> I have Koha 22.05.02.000 running on Arch Linux that imports this file just
> fine. Similarly, I have Koha latest running on a Debian VM that can import
> this file just fine, too.
>
> What am I missing?
>
> Details of my system:
>
> Koha version: 22.11.03.000 Rosalie
> OS version ('uname -a'): Linux alma 5.14.0-162.12.1.el9_1.x86_64 #1 SMP
> PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 x86_64
> Perl interpreter: /usr/bin/perl
> Perl version: 5.032001
> Perl @INC: /usr/share/koha/lib
> /usr/local/lib64/perl5/5.32
> /usr/local/share/perl5/5.32
> /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl
> /usr/lib64/perl5
> /usr/share/perl5
> /var/lib/koha/plugins
> MySQL version: mysql Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64)
> using EditLine wrapper
> Apache version: Server version: Apache/2.4.53 (AlmaLinux) Server built: Jul
> 20 2022 00:00:00
> Memcached: Servers: 127.0.0.1:11211 | Namespace: KOHA | Status: running. |
> Config read from: koha-conf.xml
> Zebra version: Zebra 2.2.7 (C) 1994-2023, Index Data 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:
> ac40f289672405a299436d73c1532f9906774cc6 Using ICU
> Zebra status: Running
> Message broker: Using RabbitMQ
> Date and time: 03/01/2023 16:20
> Time zone: Used: America/Chicago | Config: Undefined | Environment (TZ):
> Undefined
>
> Thanks,
> Michael
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Mengu Yazicioglu]

Correction

File will be manage-marc-import.pl

Mengü Yazıcıoğlu
Devinim Yazılım Eğitim Danışmanlık
Reşit Galip Cad. No: 29/6
Çankaya/ANKARA

Tel: (312) 446 86 68
Cep: (532) 701 90 27

On 5.05.2023 23:14, Mengu Yazicioglu wrote:

Hi,

This is related with stage-marc-import.pl line 93

Changing line 93 to $overlay_framework = undef if ($overlay_framework 
== '_USE_ORIG');


will solve the issue

I opened a bug for this.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33692

Mengü Yazıcıoğlu
Devinim

On 4.03.2023 19:09, Michael Brown wrote:

Thanks, Mason. Still no luck. First pass of

   $ curl -s http://192.168.1.254:8080/api/v1/ |  jq 
.info.title,.swagger


did not give me the described results. Unfortunately I didn't 
document what
the original output was (it was too early in the morning!), but I 
think it

was nothing, meaning output stalled until I hit CTRL-c.

 From the debug page you linked to:

The versions required for 22.05 are...

  $ pmvers Mojolicious JSON::Validator Mojolicious::Plugin::OpenAPI
  Mojolicious: 9.22   (needs to be 9.22 or higher)
  JSON::Validator: 5.08   (needs to be 5.08 or higher)
  Mojolicious::Plugin::OpenAPI: 5.05  (needs to be 5.05)

However, I originally installed Mojolicious 8.12 ibecause 
koha_perl_deps.pl

shows:

  Required
Module Name  Version
-
Mojolicious  8.12
-

Just an FYI in case anyone else comes across this. Fortunately,
perl-Mojolicious package is 9.22 in my repos so I installed from there.

The debug wiki suggests that Debian expects to find the files in
/usr/share/perl5, so I did

$ sudo ln -s /usr/local/share/perl5/5.32/JSON /usr/share/perl5/JSON
$ sudo ln -s /usr/local/share/perl5/5.32/Mojolicious
/usr/share/perl5/Mojolicious

Now I get the expected results from step 1.1 that you recommended:

$ curl -s http://192.168.1.254:8080/api/v1/ |  jq .info.title,.swagger
"Koha REST API"
"2.0"

But no change in staging outcome; staging does not complete, and app.pl
still runs continuously until aborted.

The only step from the debug page I have not completed yet is verifying
koha-common (I can't run any of the dkpg commands on alma). So I need to
dig into the package contents to find out what it includes. I imagine 
that

will take some time.

In the meantime, one thing I will mention in case it matters: I don't 
get

any messages in any of the following /var/log/koha files:

  api-error.log
  intranet-error.log
  opac-error.log
  plack-api-error.log
  plack-intranet-error.log
  plack-opac-error.log
  sip.log
  z3950-error.log

They are all empty. But I do get messages in

  koha-error_log
  koha-opac-error_log
  zebrasrv.log

When I first installed Koha, I couldn't access mainpage.pl because of
permissions errors on those files. They were originally owned by koha. I
changed ownership to apache and was able to open mainpage.pl. Again, 
just

FYI in case it matters.

Michael

On Sat, Mar 4, 2023 at 5:04 AM Mason James  wrote:


hi Michael

here is some debugging info, section 1.1
   https://wiki.koha-community.org/wiki/REST_API_Debug

On 4/03/23 12:14 pm, Michael Brown wrote:


Could this possibly be a similar problem? Should I try

force-downgrading
JSON::Validator and/or Mojolicious? Is there any debugging I can 
do of

the Koha::REST::V1 module?




___

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

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Mengu Yazicioglu]

Hi,

This is related with stage-marc-import.pl line 93

Changing line 93 to $overlay_framework = undef if ($overlay_framework == 
'_USE_ORIG');


will solve the issue

I opened a bug for this.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33692

Mengü Yazıcıoğlu
Devinim

On 4.03.2023 19:09, Michael Brown wrote:

Thanks, Mason. Still no luck. First pass of

   $ curl -s http://192.168.1.254:8080/api/v1/ |  jq .info.title,.swagger

did not give me the described results. Unfortunately I didn't document what
the original output was (it was too early in the morning!), but I think it
was nothing, meaning output stalled until I hit CTRL-c.

 From the debug page you linked to:

The versions required for 22.05 are...

  $ pmvers Mojolicious JSON::Validator Mojolicious::Plugin::OpenAPI
  Mojolicious: 9.22   (needs to be 9.22 or higher)
  JSON::Validator: 5.08   (needs to be 5.08 or higher)
  Mojolicious::Plugin::OpenAPI: 5.05  (needs to be 5.05)

However, I originally installed Mojolicious 8.12 ibecause koha_perl_deps.pl
shows:

  Required
Module Name  Version
-
Mojolicious  8.12
-

Just an FYI in case anyone else comes across this. Fortunately,
perl-Mojolicious package is 9.22 in my repos so I installed from there.

The debug wiki suggests that Debian expects to find the files in
/usr/share/perl5, so I did

$ sudo ln -s /usr/local/share/perl5/5.32/JSON /usr/share/perl5/JSON
$ sudo ln -s /usr/local/share/perl5/5.32/Mojolicious
/usr/share/perl5/Mojolicious

Now I get the expected results from step 1.1 that you recommended:

$ curl -s http://192.168.1.254:8080/api/v1/ |  jq .info.title,.swagger
"Koha REST API"
"2.0"

But no change in staging outcome; staging does not complete, and app.pl
still runs continuously until aborted.

The only step from the debug page I have not completed yet is verifying
koha-common (I can't run any of the dkpg commands on alma). So I need to
dig into the package contents to find out what it includes. I imagine that
will take some time.

In the meantime, one thing I will mention in case it matters: I don't get
any messages in any of the following /var/log/koha files:

  api-error.log
  intranet-error.log
  opac-error.log
  plack-api-error.log
  plack-intranet-error.log
  plack-opac-error.log
  sip.log
  z3950-error.log

They are all empty. But I do get messages in

  koha-error_log
  koha-opac-error_log
  zebrasrv.log

When I first installed Koha, I couldn't access mainpage.pl because of
permissions errors on those files. They were originally owned by koha. I
changed ownership to apache and was able to open mainpage.pl. Again, just
FYI in case it matters.

Michael

On Sat, Mar 4, 2023 at 5:04 AM Mason James  wrote:


hi Michael

here is some debugging info, section 1.1
   https://wiki.koha-community.org/wiki/REST_API_Debug

On 4/03/23 12:14 pm, Michael Brown wrote:


Could this possibly be a similar problem? Should I try

force-downgrading

JSON::Validator and/or Mojolicious? Is there any debugging I can do of
the Koha::REST::V1 module?




___

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] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Thanks, Mason. Still no luck. First pass of

  $ curl -s http://192.168.1.254:8080/api/v1/ |  jq .info.title,.swagger

did not give me the described results. Unfortunately I didn't document what
the original output was (it was too early in the morning!), but I think it
was nothing, meaning output stalled until I hit CTRL-c.

From the debug page you linked to:

The versions required for 22.05 are...

 $ pmvers Mojolicious JSON::Validator Mojolicious::Plugin::OpenAPI
 Mojolicious: 9.22   (needs to be 9.22 or higher)
 JSON::Validator: 5.08   (needs to be 5.08 or higher)
 Mojolicious::Plugin::OpenAPI: 5.05  (needs to be 5.05)

However, I originally installed Mojolicious 8.12 ibecause koha_perl_deps.pl
shows:

 Required
Module Name  Version
-
Mojolicious  8.12
-

Just an FYI in case anyone else comes across this. Fortunately,
perl-Mojolicious package is 9.22 in my repos so I installed from there.

The debug wiki suggests that Debian expects to find the files in
/usr/share/perl5, so I did

$ sudo ln -s /usr/local/share/perl5/5.32/JSON /usr/share/perl5/JSON
$ sudo ln -s /usr/local/share/perl5/5.32/Mojolicious
/usr/share/perl5/Mojolicious

Now I get the expected results from step 1.1 that you recommended:

$ curl -s http://192.168.1.254:8080/api/v1/ |  jq .info.title,.swagger
"Koha REST API"
"2.0"

But no change in staging outcome; staging does not complete, and app.pl
still runs continuously until aborted.

The only step from the debug page I have not completed yet is verifying
koha-common (I can't run any of the dkpg commands on alma). So I need to
dig into the package contents to find out what it includes. I imagine that
will take some time.

In the meantime, one thing I will mention in case it matters: I don't get
any messages in any of the following /var/log/koha files:

 api-error.log
 intranet-error.log
 opac-error.log
 plack-api-error.log
 plack-intranet-error.log
 plack-opac-error.log
 sip.log
 z3950-error.log

They are all empty. But I do get messages in

 koha-error_log
 koha-opac-error_log
 zebrasrv.log

When I first installed Koha, I couldn't access mainpage.pl because of
permissions errors on those files. They were originally owned by koha. I
changed ownership to apache and was able to open mainpage.pl. Again, just
FYI in case it matters.

Michael

On Sat, Mar 4, 2023 at 5:04 AM Mason James  wrote:

> hi Michael
>
> here is some debugging info, section 1.1
>   https://wiki.koha-community.org/wiki/REST_API_Debug
>
> On 4/03/23 12:14 pm, Michael Brown wrote:
>
>  Could this possibly be a similar problem? Should I try
> force-downgrading
>  JSON::Validator and/or Mojolicious? Is there any debugging I can do of
>  the Koha::REST::V1 module?
>
>
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Mason James]

hi Michael

here is some debugging info, section 1.1
 https://wiki.koha-community.org/wiki/REST_API_Debug

On 4/03/23 12:14 pm, Michael Brown wrote:


Could this possibly be a similar problem? Should I try force-downgrading
JSON::Validator and/or Mojolicious? Is there any debugging I can do of
the Koha::REST::V1 module?



___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Sorry, one more quick detail: the koha-conf.xml file that was generated
during installation set the following  parameter:

 __LOCK_DIR__

This threw a warning that read:

 The configured  entry in
 your koha-conf.xml file points
 to a non-writable directory (__LOCK_DIR__).

I took a wild guess and created a lockdir in the same folder with the
zebradb lockdir and with the same permissions:

 /var/lock/koha/alma

The warning is gone now, but I don't see any activity in that directory.
Maybe it's used for other purposes, but in the event that I have
misconfigured the lockdir setting, I wanted to mention it.

On Fri, Mar 3, 2023 at 4:48 PM Michael Brown  wrote:

> Thanks, Eric. Still no luck even though I downgraded several packages to
> the Koha required versions:
>
>  JSON::Validator => 5.08
>  Mojolicious => 8.12
>  Mojolicious::Plugin::OAuth2 => 2.02
>  Mojolicious::Plugin::OpenAPI => 5.05
>  Mojolicious::Plugin::RenderFile => 0.12
>
> background_jobs.data =
>
> {"parse_items":"1","marc_modification_template":null,"nomatch_action":"create_new","encoding":"UTF-8","record_type":"biblio","matcher_id":"","vendor_id":null,"basket_id":null,"filepath":"/var/lib/koha/alma/tmp/koha_upload/b63453b06ba1fa2ca63a76e64e4909bb_l.mrc","comments":"","filename":"l.mrc","item_action":"always_add","format":"ISO2709","overlay_action":"replace"}
>
> Still nothing being logged, but app.pl is really lighting up the CPU:
>
> top - 16:38:47 up 5 min,  1 user,  load average: 1.32, 1.04, 0.50
> Tasks: 237 total,   2 running, 235 sleeping,   0 stopped,   0 zombie
> %Cpu(s): 26.3 us,  1.9 sy,  0.0 ni, 71.5 id,  0.0 wa,  0.2 hi,  0.1 si,
>  0.0 st
> MiB Mem :   5827.8 total,   2597.2 free,   2334.9 used,   1492.9 buff/cache
> MiB Swap:   1331.0 total,   1331.0 free,  0.0 used.   3492.9 avail Mem
>
> PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+
> COMMAND
>3936 apache20   0  127888 121296  19480 R  99.3   2.0   0:04.01
> app.pl
>1592 michael   20   0 4325576 206032 112492 S   3.3   3.5   0:15.64
> gnome-shell
>1179 michael   20   0  521988  92176  57912 S   3.0   1.5   0:13.63
> Xorg
>2217 michael   20   0  691664  50664  38408 S   1.3   0.8   0:03.49
> gnome-terminal-
>3599 michael   20   0  226528   4204   3332 R   0.7   0.1   0:00.48 top
>
> 783 memcach+  20   0  418036  11400   4360 S   0.3   0.2   0:00.12
> memcached
> 786 rabbitmq  20   0 2848520 127696  65352 S   0.3   2.1   0:09.08
> beam.smp
>
> It will remain at about that level until I close the window.
>
> Michael
>
> On Fri, Mar 3, 2023 at 12:56 PM Eric Phetteplace 
> wrote:
>
>> I would absolutely think that the wrong version of JSON::Validator could
>> cause a problem here. Try to match Koha's versions in the cpanfile,
>> probably `cpanm --installdeps .` from the root but maybe that's not wise
>> with a package installation.
>>
>> Best,
>>
>> ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)
>>
>> ephettepl...@cca.edu
>>
>>
>> *CCA is situated on the traditional unceded lands of the **Chochenyo and
>> Ramaytush Ohlone** peoples.*
>>
>> Black-owned bookstores in Oakland: Ashay by the Bay
>> , Marcus Books
>> 
>>
>> :(){ :|: & };:
>>
>>
>> On Fri, Mar 3, 2023 at 5:58 AM Michael Brown 
>> wrote:
>>
>>> Hi Jonathan,
>>>
>>> Thanks for the suggestion; nothing much to report, though.
>>>
>>> tail -f /var/log/koha/*log
>>>
>>> showed nothing at all when I staged "l.mrc" this morning.
>>>
>>> As for the background_job.data suggestion, it took me a minute to
>>> understand what you were referring to and by the time I figured it out I
>>> had already left home, so I cannot access my server right now. However, I
>>> did copy the background_job.data entry for one of the uploads I had
>>> performed yesterday. Here it is:
>>>
>>>
>>> {"encoding":"UTF-8","comments":"","basket_id":null,"record_type":"biblio","vendor_id":null,"matcher_id":"","parse_items":"1","item_action":"always_add","format":"ISO2709","marc_modification_template":null,"filepath":"/var/lib/koha/alma/tmp/koha_upload/2287629673fb980ad4102f62ebeaa1b9_bib.mrc","nomatch_action":"create_new","filename":"bib.mrc","overlay_action":"replace"}
>>>
>>> Is that helpful? If not, I will pull the entry from the test I made this
>>> morning while watching the logs.
>>>
>>> When I was first starting out with Koha (on Arch Linux about a year ago)
>>> I
>>> was having issues that I eventually traced to JSON Validator and
>>> Mojolicious perl modules. They were both much newer than those required
>>> by
>>> Koha, and when I downgraded those two modules, things started working.
>>> But
>>> my problem back then was not with uploads; it was with the display of
>>> borrowers. Patrons were not loading on-screen and an Inspect > Console
>>> message gave me the idea to downgrade. It worked after that.
>>>
>>> Could this possibly be a similar problem? Should I try 

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Thanks, Eric. Still no luck even though I downgraded several packages to
the Koha required versions:

 JSON::Validator => 5.08
 Mojolicious => 8.12
 Mojolicious::Plugin::OAuth2 => 2.02
 Mojolicious::Plugin::OpenAPI => 5.05
 Mojolicious::Plugin::RenderFile => 0.12

background_jobs.data =
{"parse_items":"1","marc_modification_template":null,"nomatch_action":"create_new","encoding":"UTF-8","record_type":"biblio","matcher_id":"","vendor_id":null,"basket_id":null,"filepath":"/var/lib/koha/alma/tmp/koha_upload/b63453b06ba1fa2ca63a76e64e4909bb_l.mrc","comments":"","filename":"l.mrc","item_action":"always_add","format":"ISO2709","overlay_action":"replace"}

Still nothing being logged, but app.pl is really lighting up the CPU:

top - 16:38:47 up 5 min,  1 user,  load average: 1.32, 1.04, 0.50
Tasks: 237 total,   2 running, 235 sleeping,   0 stopped,   0 zombie
%Cpu(s): 26.3 us,  1.9 sy,  0.0 ni, 71.5 id,  0.0 wa,  0.2 hi,  0.1 si,
 0.0 st
MiB Mem :   5827.8 total,   2597.2 free,   2334.9 used,   1492.9 buff/cache
MiB Swap:   1331.0 total,   1331.0 free,  0.0 used.   3492.9 avail Mem

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+
COMMAND
   3936 apache20   0  127888 121296  19480 R  99.3   2.0   0:04.01
app.pl
   1592 michael   20   0 4325576 206032 112492 S   3.3   3.5   0:15.64
gnome-shell
   1179 michael   20   0  521988  92176  57912 S   3.0   1.5   0:13.63 Xorg

   2217 michael   20   0  691664  50664  38408 S   1.3   0.8   0:03.49
gnome-terminal-
   3599 michael   20   0  226528   4204   3332 R   0.7   0.1   0:00.48 top

783 memcach+  20   0  418036  11400   4360 S   0.3   0.2   0:00.12
memcached
786 rabbitmq  20   0 2848520 127696  65352 S   0.3   2.1   0:09.08
beam.smp

It will remain at about that level until I close the window.

Michael

On Fri, Mar 3, 2023 at 12:56 PM Eric Phetteplace 
wrote:

> I would absolutely think that the wrong version of JSON::Validator could
> cause a problem here. Try to match Koha's versions in the cpanfile,
> probably `cpanm --installdeps .` from the root but maybe that's not wise
> with a package installation.
>
> Best,
>
> ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)
>
> ephettepl...@cca.edu
>
>
> *CCA is situated on the traditional unceded lands of the **Chochenyo and
> Ramaytush Ohlone** peoples.*
>
> Black-owned bookstores in Oakland: Ashay by the Bay
> , Marcus Books
> 
>
> :(){ :|: & };:
>
>
> On Fri, Mar 3, 2023 at 5:58 AM Michael Brown 
> wrote:
>
>> Hi Jonathan,
>>
>> Thanks for the suggestion; nothing much to report, though.
>>
>> tail -f /var/log/koha/*log
>>
>> showed nothing at all when I staged "l.mrc" this morning.
>>
>> As for the background_job.data suggestion, it took me a minute to
>> understand what you were referring to and by the time I figured it out I
>> had already left home, so I cannot access my server right now. However, I
>> did copy the background_job.data entry for one of the uploads I had
>> performed yesterday. Here it is:
>>
>>
>> {"encoding":"UTF-8","comments":"","basket_id":null,"record_type":"biblio","vendor_id":null,"matcher_id":"","parse_items":"1","item_action":"always_add","format":"ISO2709","marc_modification_template":null,"filepath":"/var/lib/koha/alma/tmp/koha_upload/2287629673fb980ad4102f62ebeaa1b9_bib.mrc","nomatch_action":"create_new","filename":"bib.mrc","overlay_action":"replace"}
>>
>> Is that helpful? If not, I will pull the entry from the test I made this
>> morning while watching the logs.
>>
>> When I was first starting out with Koha (on Arch Linux about a year ago) I
>> was having issues that I eventually traced to JSON Validator and
>> Mojolicious perl modules. They were both much newer than those required by
>> Koha, and when I downgraded those two modules, things started working. But
>> my problem back then was not with uploads; it was with the display of
>> borrowers. Patrons were not loading on-screen and an Inspect > Console
>> message gave me the idea to downgrade. It worked after that.
>>
>> Could this possibly be a similar problem? Should I try force-downgrading
>> JSON::Validator and/or Mojolicious? Is there any debugging I can do of the
>> Koha::REST::V1 module? As I reported yesterday, app.pl shows
>> continual-constant CPU usage as long as that enqueuement page is open.
>> Once
>> I navigate away from that enqueuement page, the app.pl process quits, CPU
>> usage returns to normal.
>>
>> Michael
>>
>> On Fri, Mar 3, 2023 at 12:55 AM Jonathan Druart <
>> jonathan.dru...@bugs.koha-community.org> wrote:
>>
>> > Hello Michael,
>> > I have just tried on 22.11.03 and it seems to work for me.
>> > Can you try to open a console, watch the logs: tail -f
>> > /var/log/koha/$KOHA_INSTANCE/*.log
>> > Import a file.
>> > Do you see something in the logs?
>> >
>> > Otherwise look at the background_jobs.data JSON, you may see an error in
>> > it. But if the status is still "new" I 

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Eric Phetteplace]

I would absolutely think that the wrong version of JSON::Validator could
cause a problem here. Try to match Koha's versions in the cpanfile,
probably `cpanm --installdeps .` from the root but maybe that's not wise
with a package installation.

Best,

ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)

ephettepl...@cca.edu


*CCA is situated on the traditional unceded lands of the **Chochenyo and
Ramaytush Ohlone** peoples.*

Black-owned bookstores in Oakland: Ashay by the Bay
, Marcus Books


:(){ :|: & };:


On Fri, Mar 3, 2023 at 5:58 AM Michael Brown  wrote:

> Hi Jonathan,
>
> Thanks for the suggestion; nothing much to report, though.
>
> tail -f /var/log/koha/*log
>
> showed nothing at all when I staged "l.mrc" this morning.
>
> As for the background_job.data suggestion, it took me a minute to
> understand what you were referring to and by the time I figured it out I
> had already left home, so I cannot access my server right now. However, I
> did copy the background_job.data entry for one of the uploads I had
> performed yesterday. Here it is:
>
>
> {"encoding":"UTF-8","comments":"","basket_id":null,"record_type":"biblio","vendor_id":null,"matcher_id":"","parse_items":"1","item_action":"always_add","format":"ISO2709","marc_modification_template":null,"filepath":"/var/lib/koha/alma/tmp/koha_upload/2287629673fb980ad4102f62ebeaa1b9_bib.mrc","nomatch_action":"create_new","filename":"bib.mrc","overlay_action":"replace"}
>
> Is that helpful? If not, I will pull the entry from the test I made this
> morning while watching the logs.
>
> When I was first starting out with Koha (on Arch Linux about a year ago) I
> was having issues that I eventually traced to JSON Validator and
> Mojolicious perl modules. They were both much newer than those required by
> Koha, and when I downgraded those two modules, things started working. But
> my problem back then was not with uploads; it was with the display of
> borrowers. Patrons were not loading on-screen and an Inspect > Console
> message gave me the idea to downgrade. It worked after that.
>
> Could this possibly be a similar problem? Should I try force-downgrading
> JSON::Validator and/or Mojolicious? Is there any debugging I can do of the
> Koha::REST::V1 module? As I reported yesterday, app.pl shows
> continual-constant CPU usage as long as that enqueuement page is open. Once
> I navigate away from that enqueuement page, the app.pl process quits, CPU
> usage returns to normal.
>
> Michael
>
> On Fri, Mar 3, 2023 at 12:55 AM Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
> > Hello Michael,
> > I have just tried on 22.11.03 and it seems to work for me.
> > Can you try to open a console, watch the logs: tail -f
> > /var/log/koha/$KOHA_INSTANCE/*.log
> > Import a file.
> > Do you see something in the logs?
> >
> > Otherwise look at the background_jobs.data JSON, you may see an error in
> > it. But if the status is still "new" I am not expecting an error there.
> >
> >
> > Le jeu. 2 mars 2023 à 14:50, Michael Brown  a
> > écrit :
> >
> > > Greetings:
> > >
> > > My name is Michael Brown and I am a professional cataloger and
> SirsiDynix
> > > System Admin at the Texas State Library & Archives in Austin (20+ years
> > > now). I have been using Koha on Arch Linux in my home library for
> about a
> > > year now. I am migrating my home server to AlmaLinux and I'm having a
> > > problem.
> > >
> > > I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
> > > file for import gets stuck at 0%. On screen, I am able to select the
> file
> > > for import (bib.mrc), review the profile options (but I don't change
> any
> > > defaults), and then click on "Stage for import" at the bottom. Next
> > screen
> > > reads:
> > >
> > > The job has been enqueued! It will be processed as soon as
> possible.
> > > 0%
> > > View detail of the enqueued job
> > >
> > > After a few seconds, it changes to (and then hangs at):
> > >
> > > The job has been enqueued! It will be processed as soon as
> possible.
> > > 0% Not started
> > > View detail of the enqueued job
> > >
> > > Clicking on "View detail of the enqueued job" I see:
> > >
> > > Details of job #22
> > >
> > > Job ID: 22
> > > Status:New
> > > Progress:0 / 0
> > > Type:Staged MARC records for import
> > > Queued:03/02/2023 05:42
> > > Started:
> > > Ended:
> > >
> > > Report
> > > Detailed messages
> > > Return to the job list
> > >
> > > The corresponding entry in mariadb is:
> > >
> > > id 22
> > > status new
> > > progress NULL
> > > size 0
> > > borrowernumber 1
> > > type stage_marc_for_import
> > > queue Name of the queue the job is sent to long_tasks
> > > data {"encoding":"UTF-8","comments":"","basket_id":null...
> > > context JSON-serialized context information for the job
> > > {"flags":1,"branch":"ALMA","interface":"intranet",...
> > > 

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Hi Jonathan,

Thanks for the suggestion; nothing much to report, though.

tail -f /var/log/koha/*log

showed nothing at all when I staged "l.mrc" this morning.

As for the background_job.data suggestion, it took me a minute to
understand what you were referring to and by the time I figured it out I
had already left home, so I cannot access my server right now. However, I
did copy the background_job.data entry for one of the uploads I had
performed yesterday. Here it is:

{"encoding":"UTF-8","comments":"","basket_id":null,"record_type":"biblio","vendor_id":null,"matcher_id":"","parse_items":"1","item_action":"always_add","format":"ISO2709","marc_modification_template":null,"filepath":"/var/lib/koha/alma/tmp/koha_upload/2287629673fb980ad4102f62ebeaa1b9_bib.mrc","nomatch_action":"create_new","filename":"bib.mrc","overlay_action":"replace"}

Is that helpful? If not, I will pull the entry from the test I made this
morning while watching the logs.

When I was first starting out with Koha (on Arch Linux about a year ago) I
was having issues that I eventually traced to JSON Validator and
Mojolicious perl modules. They were both much newer than those required by
Koha, and when I downgraded those two modules, things started working. But
my problem back then was not with uploads; it was with the display of
borrowers. Patrons were not loading on-screen and an Inspect > Console
message gave me the idea to downgrade. It worked after that.

Could this possibly be a similar problem? Should I try force-downgrading
JSON::Validator and/or Mojolicious? Is there any debugging I can do of the
Koha::REST::V1 module? As I reported yesterday, app.pl shows
continual-constant CPU usage as long as that enqueuement page is open. Once
I navigate away from that enqueuement page, the app.pl process quits, CPU
usage returns to normal.

Michael

On Fri, Mar 3, 2023 at 12:55 AM Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hello Michael,
> I have just tried on 22.11.03 and it seems to work for me.
> Can you try to open a console, watch the logs: tail -f
> /var/log/koha/$KOHA_INSTANCE/*.log
> Import a file.
> Do you see something in the logs?
>
> Otherwise look at the background_jobs.data JSON, you may see an error in
> it. But if the status is still "new" I am not expecting an error there.
>
>
> Le jeu. 2 mars 2023 à 14:50, Michael Brown  a
> écrit :
>
> > Greetings:
> >
> > My name is Michael Brown and I am a professional cataloger and SirsiDynix
> > System Admin at the Texas State Library & Archives in Austin (20+ years
> > now). I have been using Koha on Arch Linux in my home library for about a
> > year now. I am migrating my home server to AlmaLinux and I'm having a
> > problem.
> >
> > I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
> > file for import gets stuck at 0%. On screen, I am able to select the file
> > for import (bib.mrc), review the profile options (but I don't change any
> > defaults), and then click on "Stage for import" at the bottom. Next
> screen
> > reads:
> >
> > The job has been enqueued! It will be processed as soon as possible.
> > 0%
> > View detail of the enqueued job
> >
> > After a few seconds, it changes to (and then hangs at):
> >
> > The job has been enqueued! It will be processed as soon as possible.
> > 0% Not started
> > View detail of the enqueued job
> >
> > Clicking on "View detail of the enqueued job" I see:
> >
> > Details of job #22
> >
> > Job ID: 22
> > Status:New
> > Progress:0 / 0
> > Type:Staged MARC records for import
> > Queued:03/02/2023 05:42
> > Started:
> > Ended:
> >
> > Report
> > Detailed messages
> > Return to the job list
> >
> > The corresponding entry in mariadb is:
> >
> > id 22
> > status new
> > progress NULL
> > size 0
> > borrowernumber 1
> > type stage_marc_for_import
> > queue Name of the queue the job is sent to long_tasks
> > data {"encoding":"UTF-8","comments":"","basket_id":null...
> > context JSON-serialized context information for the job
> > {"flags":1,"branch":"ALMA","interface":"intranet",...
> > enqueued_on 2023-03-02 05:42:33
> > started_on NULL
> > ended_on NULL
> >
> > (If you need to see the full entries for "data" and "context", please let
> > me know.)
> >
> > tmp, koha_upload, and lock directories have been tweaked and fine tuned.
> I
> > was getting early warnings about them not being set in koha-conf.xml so I
> > created them (and set correct permissions) and I can see the uploaded
> file
> > (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
> > actual upload function appears to be working.
> >
> > I am getting no apache errors and no other on-screen diagnostics.
> >
> > I have Koha 22.05.02.000 running on Arch Linux that imports this file
> just
> > fine. Similarly, I have Koha latest running on a Debian VM that can
> import
> > this file just fine, too.
> >
> > What am I missing?
> >
> > Details of my system:

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Jonathan Druart]

Hello Michael,
I have just tried on 22.11.03 and it seems to work for me.
Can you try to open a console, watch the logs: tail -f
/var/log/koha/$KOHA_INSTANCE/*.log
Import a file.
Do you see something in the logs?

Otherwise look at the background_jobs.data JSON, you may see an error in
it. But if the status is still "new" I am not expecting an error there.


Le jeu. 2 mars 2023 à 14:50, Michael Brown  a
écrit :

> Greetings:
>
> My name is Michael Brown and I am a professional cataloger and SirsiDynix
> System Admin at the Texas State Library & Archives in Austin (20+ years
> now). I have been using Koha on Arch Linux in my home library for about a
> year now. I am migrating my home server to AlmaLinux and I'm having a
> problem.
>
> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
> file for import gets stuck at 0%. On screen, I am able to select the file
> for import (bib.mrc), review the profile options (but I don't change any
> defaults), and then click on "Stage for import" at the bottom. Next screen
> reads:
>
> The job has been enqueued! It will be processed as soon as possible.
> 0%
> View detail of the enqueued job
>
> After a few seconds, it changes to (and then hangs at):
>
> The job has been enqueued! It will be processed as soon as possible.
> 0% Not started
> View detail of the enqueued job
>
> Clicking on "View detail of the enqueued job" I see:
>
> Details of job #22
>
> Job ID: 22
> Status:New
> Progress:0 / 0
> Type:Staged MARC records for import
> Queued:03/02/2023 05:42
> Started:
> Ended:
>
> Report
> Detailed messages
> Return to the job list
>
> The corresponding entry in mariadb is:
>
> id 22
> status new
> progress NULL
> size 0
> borrowernumber 1
> type stage_marc_for_import
> queue Name of the queue the job is sent to long_tasks
> data {"encoding":"UTF-8","comments":"","basket_id":null...
> context JSON-serialized context information for the job
> {"flags":1,"branch":"ALMA","interface":"intranet",...
> enqueued_on 2023-03-02 05:42:33
> started_on NULL
> ended_on NULL
>
> (If you need to see the full entries for "data" and "context", please let
> me know.)
>
> tmp, koha_upload, and lock directories have been tweaked and fine tuned. I
> was getting early warnings about them not being set in koha-conf.xml so I
> created them (and set correct permissions) and I can see the uploaded file
> (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
> actual upload function appears to be working.
>
> I am getting no apache errors and no other on-screen diagnostics.
>
> I have Koha 22.05.02.000 running on Arch Linux that imports this file just
> fine. Similarly, I have Koha latest running on a Debian VM that can import
> this file just fine, too.
>
> What am I missing?
>
> Details of my system:
>
> Koha version: 22.11.03.000 Rosalie
> OS version ('uname -a'): Linux alma 5.14.0-162.12.1.el9_1.x86_64 #1 SMP
> PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 x86_64
> Perl interpreter: /usr/bin/perl
> Perl version: 5.032001
> Perl @INC: /usr/share/koha/lib
> /usr/local/lib64/perl5/5.32
> /usr/local/share/perl5/5.32
> /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl
> /usr/lib64/perl5
> /usr/share/perl5
> /var/lib/koha/plugins
> MySQL version: mysql Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64)
> using EditLine wrapper
> Apache version: Server version: Apache/2.4.53 (AlmaLinux) Server built: Jul
> 20 2022 00:00:00
> Memcached: Servers: 127.0.0.1:11211 | Namespace: KOHA | Status: running. |
> Config read from: koha-conf.xml
> Zebra version: Zebra 2.2.7 (C) 1994-2023, Index Data 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:
> ac40f289672405a299436d73c1532f9906774cc6 Using ICU
> Zebra status: Running
> Message broker: Using RabbitMQ
> Date and time: 03/01/2023 16:20
> Time zone: Used: America/Chicago | Config: Undefined | Environment (TZ):
> Undefined
>
> Thanks,
> Michael
> ___
>
> 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] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Thanks, Eric. I appreciate that suggestion, but that didn't work. What
happens now is I click on "Stage for import" at the bottom and I'm thrown
right back to the spot where I'm supposed to upload a file for import,
bypassing the "enqueuement" altogether. However,
/var/log/koha/koha-error_log shows a new error:

Failed to connect: Error connecting to localhost:61613:
Connection refused at /usr/local/share/perl5/5.32/Net/Stomp.pm
line 27.; giving up at /usr/local/share/perl5/5.32/Net/Stomp.pm
line 27.: /usr/share/koha/intranet/cgi-bin/about.pl, referer:
http://192.168.1.254:8080/cgi-bin/koha/mainpage.pl

I added port 61613/tcp to my firewall rules, but lsof doesn't show anything
listening on that port. But that got me thinking that maybe 61613 might
need to be open for rabbitmq to begin with, so I re-enabled rabbitmq and
rebooted with port 61613 open. Now I'm back to hanging at the "0% Not
Started" enqueuement.

Just for grins, I tried completely disabling the firewall. Still no luck.

Another thing I noticed: if I leave the "enqueuement" page open (hanging at
0%...), /usr/share/koha/api/v1/app.pl will keep running, consuming a lot of
my cpu power until I finally navigate away from that page.

I'm going to keep digging, but if you have any other suggestions, I'm all
ears.

Michael

On Thu, Mar 2, 2023 at 11:01 AM Eric Phetteplace 
wrote:

> Hi Michael,
>
> This is not going to be a very informed response, because I don't know
> much about this part of Koha, but based on what you wrote it sounds like it
> might be an error with the messaging queue. The file uploads OK, so that's
> not it, and the version of a package dependency (like RabbitMQ) is the sort
> of thing that's affected by an OS change. You could try changing your
> message broker to SQL polling (I think that involves just removing the
> message_broker setting in koha-conf.xml and restarting) to see if that
> fixes the problem, then investigate RabbitMQ itself e.g. if it has its own
> logs, a debug mode, or use its web UI (on port 15672).
>
> Best,
>
> ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)
>
> ephettepl...@cca.edu
>
>
> *CCA is situated on the traditional unceded lands of the **Chochenyo and
> Ramaytush Ohlone** peoples.*
>
> Black-owned bookstores in Oakland: Ashay by the Bay
> , Marcus Books
> 
>
> :(){ :|: & };:
>
>
> On Thu, Mar 2, 2023 at 5:51 AM Michael Brown 
> wrote:
>
>> Greetings:
>>
>> My name is Michael Brown and I am a professional cataloger and SirsiDynix
>> System Admin at the Texas State Library & Archives in Austin (20+ years
>> now). I have been using Koha on Arch Linux in my home library for about a
>> year now. I am migrating my home server to AlmaLinux and I'm having a
>> problem.
>>
>> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
>> file for import gets stuck at 0%. On screen, I am able to select the file
>> for import (bib.mrc), review the profile options (but I don't change any
>> defaults), and then click on "Stage for import" at the bottom. Next screen
>> reads:
>>
>> The job has been enqueued! It will be processed as soon as possible.
>> 0%
>> View detail of the enqueued job
>>
>> After a few seconds, it changes to (and then hangs at):
>>
>> The job has been enqueued! It will be processed as soon as possible.
>> 0% Not started
>> View detail of the enqueued job
>>
>> Clicking on "View detail of the enqueued job" I see:
>>
>> Details of job #22
>>
>> Job ID: 22
>> Status:New
>> Progress:0 / 0
>> Type:Staged MARC records for import
>> Queued:03/02/2023 05:42
>> Started:
>> Ended:
>>
>> Report
>> Detailed messages
>> Return to the job list
>>
>> The corresponding entry in mariadb is:
>>
>> id 22
>> status new
>> progress NULL
>> size 0
>> borrowernumber 1
>> type stage_marc_for_import
>> queue Name of the queue the job is sent to long_tasks
>> data {"encoding":"UTF-8","comments":"","basket_id":null...
>> context JSON-serialized context information for the job
>> {"flags":1,"branch":"ALMA","interface":"intranet",...
>> enqueued_on 2023-03-02 05:42:33
>> started_on NULL
>> ended_on NULL
>>
>> (If you need to see the full entries for "data" and "context", please let
>> me know.)
>>
>> tmp, koha_upload, and lock directories have been tweaked and fine tuned. I
>> was getting early warnings about them not being set in koha-conf.xml so I
>> created them (and set correct permissions) and I can see the uploaded file
>> (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
>> actual upload function appears to be working.
>>
>> I am getting no apache errors and no other on-screen diagnostics.
>>
>> I have Koha 22.05.02.000 running on Arch Linux that imports this file just
>> fine. Similarly, I have Koha latest running on a Debian VM that can import
>> this file just fine, too.
>>
>> What am I missing?
>>
>> Details 

Re: [Koha] Background job / Staging MARC import stuck at 0%

[Eric Phetteplace]

Hi Michael,

This is not going to be a very informed response, because I don't know much
about this part of Koha, but based on what you wrote it sounds like it
might be an error with the messaging queue. The file uploads OK, so that's
not it, and the version of a package dependency (like RabbitMQ) is the sort
of thing that's affected by an OS change. You could try changing your
message broker to SQL polling (I think that involves just removing the
message_broker setting in koha-conf.xml and restarting) to see if that
fixes the problem, then investigate RabbitMQ itself e.g. if it has its own
logs, a debug mode, or use its web UI (on port 15672).

Best,

ERIC PHETTEPLACE Systems Librarian, Libraries (he/him)

ephettepl...@cca.edu


*CCA is situated on the traditional unceded lands of the **Chochenyo and
Ramaytush Ohlone** peoples.*

Black-owned bookstores in Oakland: Ashay by the Bay
, Marcus Books


:(){ :|: & };:


On Thu, Mar 2, 2023 at 5:51 AM Michael Brown  wrote:

> Greetings:
>
> My name is Michael Brown and I am a professional cataloger and SirsiDynix
> System Admin at the Texas State Library & Archives in Austin (20+ years
> now). I have been using Koha on Arch Linux in my home library for about a
> year now. I am migrating my home server to AlmaLinux and I'm having a
> problem.
>
> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
> file for import gets stuck at 0%. On screen, I am able to select the file
> for import (bib.mrc), review the profile options (but I don't change any
> defaults), and then click on "Stage for import" at the bottom. Next screen
> reads:
>
> The job has been enqueued! It will be processed as soon as possible.
> 0%
> View detail of the enqueued job
>
> After a few seconds, it changes to (and then hangs at):
>
> The job has been enqueued! It will be processed as soon as possible.
> 0% Not started
> View detail of the enqueued job
>
> Clicking on "View detail of the enqueued job" I see:
>
> Details of job #22
>
> Job ID: 22
> Status:New
> Progress:0 / 0
> Type:Staged MARC records for import
> Queued:03/02/2023 05:42
> Started:
> Ended:
>
> Report
> Detailed messages
> Return to the job list
>
> The corresponding entry in mariadb is:
>
> id 22
> status new
> progress NULL
> size 0
> borrowernumber 1
> type stage_marc_for_import
> queue Name of the queue the job is sent to long_tasks
> data {"encoding":"UTF-8","comments":"","basket_id":null...
> context JSON-serialized context information for the job
> {"flags":1,"branch":"ALMA","interface":"intranet",...
> enqueued_on 2023-03-02 05:42:33
> started_on NULL
> ended_on NULL
>
> (If you need to see the full entries for "data" and "context", please let
> me know.)
>
> tmp, koha_upload, and lock directories have been tweaked and fine tuned. I
> was getting early warnings about them not being set in koha-conf.xml so I
> created them (and set correct permissions) and I can see the uploaded file
> (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
> actual upload function appears to be working.
>
> I am getting no apache errors and no other on-screen diagnostics.
>
> I have Koha 22.05.02.000 running on Arch Linux that imports this file just
> fine. Similarly, I have Koha latest running on a Debian VM that can import
> this file just fine, too.
>
> What am I missing?
>
> Details of my system:
>
> Koha version: 22.11.03.000 Rosalie
> OS version ('uname -a'): Linux alma 5.14.0-162.12.1.el9_1.x86_64 #1 SMP
> PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 x86_64
> Perl interpreter: /usr/bin/perl
> Perl version: 5.032001
> Perl @INC: /usr/share/koha/lib
> /usr/local/lib64/perl5/5.32
> /usr/local/share/perl5/5.32
> /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl
> /usr/lib64/perl5
> /usr/share/perl5
> /var/lib/koha/plugins
> MySQL version: mysql Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64)
> using EditLine wrapper
> Apache version: Server version: Apache/2.4.53 (AlmaLinux) Server built: Jul
> 20 2022 00:00:00
> Memcached: Servers: 127.0.0.1:11211 | Namespace: KOHA | Status: running. |
> Config read from: koha-conf.xml
> Zebra version: Zebra 2.2.7 (C) 1994-2023, Index Data 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:
> ac40f289672405a299436d73c1532f9906774cc6 Using ICU
> Zebra status: Running
> Message broker: Using RabbitMQ
> Date and time: 03/01/2023 16:20
> Time zone: Used: America/Chicago | Config: Undefined | Environment (TZ):
> Undefined
>
> Thanks,
> Michael
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  

[Koha] Background job / Staging MARC import stuck at 0%

[Michael Brown]

Greetings:

My name is Michael Brown and I am a professional cataloger and SirsiDynix
System Admin at the Texas State Library & Archives in Austin (20+ years
now). I have been using Koha on Arch Linux in my home library for about a
year now. I am migrating my home server to AlmaLinux and I'm having a
problem.

I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC
file for import gets stuck at 0%. On screen, I am able to select the file
for import (bib.mrc), review the profile options (but I don't change any
defaults), and then click on "Stage for import" at the bottom. Next screen
reads:

The job has been enqueued! It will be processed as soon as possible.
0%
View detail of the enqueued job

After a few seconds, it changes to (and then hangs at):

The job has been enqueued! It will be processed as soon as possible.
0% Not started
View detail of the enqueued job

Clicking on "View detail of the enqueued job" I see:

Details of job #22

Job ID: 22
Status:New
Progress:0 / 0
Type:Staged MARC records for import
Queued:03/02/2023 05:42
Started:
Ended:

Report
Detailed messages
Return to the job list

The corresponding entry in mariadb is:

id 22
status new
progress NULL
size 0
borrowernumber 1
type stage_marc_for_import
queue Name of the queue the job is sent to long_tasks
data {"encoding":"UTF-8","comments":"","basket_id":null...
context JSON-serialized context information for the job
{"flags":1,"branch":"ALMA","interface":"intranet",...
enqueued_on 2023-03-02 05:42:33
started_on NULL
ended_on NULL

(If you need to see the full entries for "data" and "context", please let
me know.)

tmp, koha_upload, and lock directories have been tweaked and fine tuned. I
was getting early warnings about them not being set in koha-conf.xml so I
created them (and set correct permissions) and I can see the uploaded file
(for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the
actual upload function appears to be working.

I am getting no apache errors and no other on-screen diagnostics.

I have Koha 22.05.02.000 running on Arch Linux that imports this file just
fine. Similarly, I have Koha latest running on a Debian VM that can import
this file just fine, too.

What am I missing?

Details of my system:

Koha version: 22.11.03.000 Rosalie
OS version ('uname -a'): Linux alma 5.14.0-162.12.1.el9_1.x86_64 #1 SMP
PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 x86_64
Perl interpreter: /usr/bin/perl
Perl version: 5.032001
Perl @INC: /usr/share/koha/lib
/usr/local/lib64/perl5/5.32
/usr/local/share/perl5/5.32
/usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl
/usr/lib64/perl5
/usr/share/perl5
/var/lib/koha/plugins
MySQL version: mysql Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64)
using EditLine wrapper
Apache version: Server version: Apache/2.4.53 (AlmaLinux) Server built: Jul
20 2022 00:00:00
Memcached: Servers: 127.0.0.1:11211 | Namespace: KOHA | Status: running. |
Config read from: koha-conf.xml
Zebra version: Zebra 2.2.7 (C) 1994-2023, Index Data 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:
ac40f289672405a299436d73c1532f9906774cc6 Using ICU
Zebra status: Running
Message broker: Using RabbitMQ
Date and time: 03/01/2023 16:20
Time zone: Used: America/Chicago | Config: Undefined | Environment (TZ):
Undefined

Thanks,
Michael
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha