MTA is reporting "Waiting for Busy listen socket to become available"

(Last modified: 24Feb2003)

This document (10055813) is provided subject to the disclaimer at the end of this document.

fact

GroupWise 5.5

GroupWise MTA

symptom

MTA is reporting "Waiting for Busy listen socket to become available"

Several administrative messages were not processing and were being reported as pending requests.  

Some messages seem to process fine.

cause

There are two MTA agents running on the server.  One for the primary domain and another for a secondary domain.  Both agents were configured to listen on port 7100 (i.e. /tcpport-7100).

fix

Reconfiguring the secondary domain's MTA to listen on a different TCP port resolved the "Waiting for Busy listen socket to become available" errors on the MTA and also allowed the pending requests to process.

document

Document Title:	MTA is reporting "Waiting for Busy listen socket to become available"
Document ID:	10055813
Solution ID:	NOVL21889
Creation Date:	09Aug2000
Modified Date:	24Feb2003
Novell Product Class:	Groupware

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.