MailScanner takes a very long time to initialize

[Rick Wezenaar]

Ok, I fixed it. Thanks for the suggestion to set Debug to on. Turns out 
there was a /etc/MailScanner/conf.d/my-settings.conf which appearantly 
let ms-init start a loop of reading the configuration files, or 
something like that. When I removed that file MailScanner started 
properly within a second.

Thanks :)



On 29/08/2024 21:10, Shawn Iverson via MailScanner wrote:
> On 8/29/24 05:54, Rick Wezenaar via MailScanner wrote:
>> L.S.,
>>
>> Whenever I start MailScanner it takes a very long time to initialize. 
>> I can see it does some initial checks, like a lintlite and ms-peek to 
>> all work directories, but that takes a very long time, on average 8 
>> minutes:
>>
>> $> time systemctl start mailscanner
>> systemctl start mailscanner  0.01s user 0.02s system 0% cpu 8:47.38 total
>>
>> In my humble opinion, this is not normal. Can anyone help ?
>
> That isn't normal.  This literally should only take seconds for the 
> master process to spawn.
>
> You might try enabling debug in MailScanner and observing your 
> logs/journalctl to see if you can pinpoint the source of the lengthy 
> start.
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20240830/e52f397d/attachment.html>