On 11/27/22 00:35, Jan Eden via Mailman-users wrote:
– but the existing directory /opt/mailman/fulltext_index (and its contents) are readable and writeable by mailman:mailman:
drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/
-rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK*
I fail to see where haystack tries (and fails) to create the directory. FWIW, deleting threads is not a problem.
It is uwsgi trying to do this. What user is it running as? Maybe you
need to add that user to the mailman group.
Deleting threads is not an issue, apparently because it doesn't try to update the search index.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan