Re: [courier-users] Sometimes MTA crashs and is not reachable

Hi Sam,

OK, to sort out what will cause the problem, I've done the following:
--> I've pumped up the memory to 512MB.
--> Stand-Alone. Only Courier is running on it with
IMAP,IMAP-SSL,MTA,MTA-SSL,AUTHDAEMON

Let's see what is happening.
Sam, is there anything else what I can provide you, or what I should
configure.
Please let me know what I can do else, because it is very important for
me to get rid of this issue.
I want avoid to set up a new MTA (ex. EXIM, sendmail, etc), because I
like the Courier product.

So give me some hints, if I should trace something, tell me. I can setup
an separate instance where you can have
access to help me to fix that. Because I want support you to get that
product stable and that this will help
other customers as well to be satisfied with Courier ;-)

Many Thanks.

Cheers,
Maik

Sam Varshavchik wrote:
> Maik Brauer writes:
>
>> After some tests I've observed the following. I tried it with telnet on
>> that port to see if the MTA is responding, with the
>> command (telnet mx01.xxxxxx.com 25) and I can see directly a connection
>> refused.
>> In a Trace file whih a made with TCPDUMP, you can see that after a SYN
>> (Syncronise) Message a RST (Reset) Message will follow.
>> As I said, after a restart, the system is up and running again.
>> This Problem occurs after some hours or maybe 1 or 2 days. So it will
>> take a while if this happens again after a restart.
>> I've installed 2 times as well a complete fresh system, to ensure that I
>> messed up something in the operating system or TCP-Stack.
>> But this has not changed the situtation. So my question, is there a bug
>
> There are no known bugs. It would be rather difficult for any bug to
> be there in the first place, since the process that listens for an
> opens new connections is couriertcpd, which does nothing else except
> that.
>
>> in the actuall MTA Software or has someone the
>> same problems,
>
> I don't remember anyone reporting the same problem in the last ten years.
>
> The only thing that I can think of is that you're low on memory. When
> available memory runs out, some versions of the Linux kernel use the
> OOM killer to terminate random processes, to free up memory.
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> courier-users mailing list
> courier-users@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users