On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark@msapiro.net> wrote:
On 2/5/23 01:13, Odhiambo Washington wrote:
So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800?
In the last episode, I did set:
HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE = 3600
However, the same error has reared its head again.
It probably isn't even set in your case and defaults to 900 if it isn't set. Yes, you can set it to a larger value. If your archive search engine is woosh and your archive is even moderately large, 1800 probably isn't nearly enough. There was no indication of timing in your OP, but you should determine when that cron job started and when the error was reported.
Now that I have the error message - mail was generated at 0600hrs - what should I grep for in mailmanweb.log to ascertain when the cron job started?
The difference is the absolute minimum you should set for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin to that.
..so as to get this difference, that I need to set as the _ bsolute minimum_, with some margin?
Thanks in advance.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)