[Citadel Development] Re: citadel-1620778956-x86_64.appimage -- looks like it's working?

2021-05-19 Thread s3cr3to
OK, I'll try with this values. The *first 3* are from my server in production. And I will try with the *double* in "set_cachesize" of what is suggested in the document. # cat /usr/local/citadel/data/DB_CONFIG *set_lk_max_locks 4000** **set_lk_max_lockers 4000** **set_lk_max_object

[Citadel Development] [SCM] Citadel Server, WebCit, utilities branch master updated. Release_902-640-gde8a29ba5

2021-05-19 Thread noreply
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Citadel Server, WebCit, utilities". The branch, master has been updated via de8a29ba5870a337d54c2ca012ae8be75437b721 (commit)

[Citadel Development] Re: citadel-1620778956-x86_64.appimage -- looks like it's working?

2021-05-19 Thread IGnatius T Foobar
>*May 17 14:21:06 em2 citserver[25444]: db: BDB3017 unable to >allocate space from the buffer cache* >*May 17 14:21:06 em2 citserver[25444]: db: compact: Cannot allocate >memory* You didn't recover any disk space because it crashed. This means we have to put some li

[Citadel Development] Re: citadel-1620778956-x86_64.appimage -- looks like it's working?

2021-05-19 Thread s3cr3to
The process is finished, but I don't see any improvement in space. Sorry for the storm of messages I send; where I write the results that showed the progress. In the last messages, I document how it marks a memory error: May 17 13:28:38 em2 citserver[25444]: db: compacting database 7 *Ma

[Citadel Development] Re: citadel-1620778956-x86_64.appimage -- looks like it's working?

2021-05-19 Thread IGnatius T Foobar
>I'll let it run another +4 hours, which is about how long it took to do >the cleanup process. Did it finish? The warning about the housekeeping loop is normal if you're doing a big purge, because the purge runs inside the housekeeping loop so it won't start another one.