[Koha-bugs] [Bug 34070] background_jobs_worker.pl floods logs when not connecting

[bugzilla-daemon at bugs.koha-community.org]

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

Tomás Cohen Arazi <tomascohen at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED
                 CC|                            |tomascohen at gmail.com

--- Comment #4 from Tomás Cohen Arazi <tomascohen at gmail.com> ---
I've just spotted this in production, upgraded several versions over the years,
through 22.11. The configuration seemed to be correct.

We've been searching for a stray broken message for a while in vain.

What we found in the rabbit queue logs, is that the connection to the broker
was not successful. This is the reason for filling the disk: the worker gets a
message telling the credentials are invalid or don't have enough permissions,
which is a plain string ("You must log in usin...") and it explodes when trying
to decode as JSON, and retries.

We initially thought it was about the guest user not existing, but it existed:

$ sudo rabbitmqctl add_user guest guest
Adding user "guest" ...
Error:
User "guest" already exists

Then we found a line in the rabbit logs telling the 'vhost' didn't exist
(koha_frontera in this case). It was easier to spot the login or permissions
problem so we missed it initially:

vhost koha_frontera not found
2023-07-12 09:56:31.983 [warning] <0.902.0> STOMP login failed - not_allowed
(vhost access not allowed)~n
2023-07-12 09:56:31.983 [error] <0.902.0> STOMP error frame sent:
Message: "Bad CONNECT"
Detail: "Virtual host 'koha_frontera' access denied"
Server private detail: none

We created it:

$ sudo rabbitmqctl add_vhost koha_frontera

Then it started saying (again) that there was a permissions issue, so we gave
'guest', permissions over the 'koha_frontera' vhost:

$ sudo rabbitmqctl set_permissions -p 'koha_frontera' guest ".*" ".*" ".*"

And then we restarted everything. Tried staging a file and all logs look
correct.

I'm leaving this here, and closing this bug as invalid, as it looks like a
maintenance problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.