Re: MailScanner takes a very long time to initialize

Rick Wezenaar via MailScanner <mailscanner-qhrM8SXbD5JTOyd/[email protected]> Fri, 30 Aug 2024 10:08:10 +0200
Newsgroups gmane.mail.virus.mailscanner
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============3809257035911828237==
Content-Type: multipart/alternative;
 boundary="------------xNxRSUFM2C0FDj4UnYEQ0RTp"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------xNxRSUFM2C0FDj4UnYEQ0RTp
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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.


--------------xNxRSUFM2C0FDj4UnYEQ0RTp
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    <div class="moz-cite-prefix">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.<br>
      <br>
      Thanks :)<br>
      <br>
      <br>
      <br>
      On 29/08/2024 21:10, Shawn Iverson via MailScanner wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:6edd379b-d4f0-437b-aefa-5c940cac604d-CHF4LgeilpSzSzjNS9e3XA@public.gmane.org">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix">On 8/29/24 05:54, Rick Wezenaar via
        MailScanner wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:5fb854e5-9724-4e27-92d2-db201397f9ec-kLaSOWnPm7Vg9hUCZPvPmw@public.gmane.org">
        <meta http-equiv="content-type"
          content="text/html; charset=UTF-8">
        L.S.,<br>
        <br>
        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:<br>
        <br>
        <font face="Courier New, Courier, monospace">$&gt; time
          systemctl start
mailscanner                                                               
          <br>
          systemctl start mailscanner  0.01s user 0.02s system 0% cpu
          8:47.38 total</font><br>
        <br>
        In my humble opinion, this is not normal. Can anyone help ?</blockquote>
      <p>That isn't normal.  This literally should only take seconds for
        the master process to spawn.</p>
      <p><span style="white-space: pre-wrap">You might try enabling debug in MailScanner and observing your logs/journalctl to see if you can pinpoint the source of the lengthy start.</span></p>
      <p><span style="white-space: pre-wrap">
</span></p>
      <br>
      -- <br>
      This message has been scanned for viruses and
      <br>
      dangerous content by
      <a href="http://www.mailscanner.info/" moz-do-not-send="true"><b>MailScanner</b></a>,
      and is
      <br>
      believed to be clean.
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">

</pre>
    </blockquote>
    <br>
  <br />-- 
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>

--------------xNxRSUFM2C0FDj4UnYEQ0RTp--

--===============3809257035911828237==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



-- 
MailScanner mailing list
mailscanner-qhrM8SXbD5JTOyd/[email protected]
http://lists.mailscanner.info/mailman/listinfo/mailscanner


--===============3809257035911828237==--