Tried with both Tools → Reindex search backend and
sudo docker compose run frontend run_command search_initialize
sudo docker compose run frontend run_command search_reindex
2.5 GB RAM used, 5.5 GB RAM remain free. 4 CPU cores, with the CPU load near zero the entire time.
RabbitMQ logs show no relevant errors, neither do the app container logs. The “search” queue remains idle most of the time:
The reindexing happens at an ultra-slow pace, eventually petering out with the “search” queue becoming empty. At the same time, the number of indexed document pages is vanishingly small, i.e., I’m experiencing the same problem as the guy from
https://forum.mayan-edms.com/t/search-not-working-anymore/
This appears to be a related problem:
https://forum.mayan-edms.com/t/documents-dont-get-send-to-tesseract/
PS RabbitMQ logs do show errors occasionally, not sure if related:
2023-05-14 11:05:56.376991+00:00 [warning] <0.2874.0> closing AMQP connection <0.2874.0> (172.30.0.5:55202 -> 172.30.0.4:5672, vhost: 'mayan', user: 'mayan'):
2023-05-14 11:05:56.376991+00:00 [warning] <0.2874.0> client unexpectedly closed TCP connection
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> supervisor: {<0.2878.0>,rabbit_channel_sup}
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> errorContext: shutdown_error
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> reason: noproc
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> offender: [{pid,<0.2881.0>},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {id,channel},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {mfargs,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {rabbit_channel,start_link,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> [1,<0.2874.0>,<0.2879.0>,<0.2874.0>,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> <<"172.30.0.5:55202 -> 172.30.0.4:5672">>,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> rabbit_framing_amqp_0_9_1,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {user,<<"mayan">>,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> [administrator],
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> [{rabbit_auth_backend_internal,none}]},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> <<"mayan">>,
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> [{<<"consumer_cancel_notify">>,bool,true},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {<<"connection.blocked">>,bool,true},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {<<"authentication_failure_close">>,bool,true}],
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> <0.2875.0>,<0.2880.0>]}},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {restart_type,intrinsic},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {shutdown,70000},
2023-05-14 11:05:56.377652+00:00 [error] <0.2878.0> {child_type,worker}]
The same warning pops up quite often:
2023-05-14 11:09:02.178962+00:00 [warning] <0.3372.0> closing AMQP connection <0.3372.0> (172.30.0.5:58246 -> 172.30.0.4:5672, vhost: 'mayan', user: 'mayan'):
2023-05-14 11:09:02.178962+00:00 [warning] <0.3372.0> client unexpectedly closed TCP connection