[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

--- Comment #5 from Magnus Enger <magnus at libriotech.no> ---
I had a similar problem today and finally got round to digging a bit deeper
into RabbitMQ. Here are some of the things I found: 

$ sudo rabbitmq-diagnostics check_virtual_hosts
Checking if all vhosts are running on node rabbit at kohaswe ...
Error:
Some virtual hosts on node rabbit at kohaswe are down:
/

$ sudo rabbitmqctl list_queues --offline state name
Timeout: 60.0 seconds ...
Listing queues for vhost / ...
state   name
down    koha_mykoha-batch_authority_record_modification
down    koha_mykoha-batch_item_record_modification
down    koha_mykoha-long_tasks
...

$ sudo rabbitmqctl restart_vhost
Trying to restart vhost '/' on node 'rabbit at kohaswe' ...
Error:
Failed to start vhost '/' on node 'rabbit at kohaswe'Reason: {:shutdown,
{:failed_to_start_child, :rabbit_vhost_process, {:badmatch, {:error,
{{{:badmatch, {:error, {:not_a_dets_file,
'/var/lib/rabbitmq/mnesia/rabbit at kohaswe/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/recovery.dets'}}},
[{:rabbit_recovery_terms, :open_table, 1, [file:
'src/rabbit_recovery_terms.erl', line: 199]}, {:rabbit_recovery_terms, :init,
1, [file: 'src/rabbit_recovery_terms.erl', line: 179]}, {:gen_server, :init_it,
2, [file: 'gen_server.erl', line: 374]}, {:gen_server, :init_it, 6, [file:
'gen_server.erl', line: 342]}, {:proc_lib, :init_p_do_apply, 3, [file:
'proc_lib.erl', line: 249]}]}, {:child, :undefined, :rabbit_recovery_terms,
{:rabbit_recovery_terms, :start_link, ["/"]}, :transient, 30000, :worker,
[:rabbit_recovery_terms]}}}}}}

I found a solution to the problem here:
https://stackoverflow.com/questions/58689551/rabbitmq-vhost-is-down-for-user-xyz-even-after-user-has-all-access
and after effectively wiping all the queues, I got things running again.

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