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
