Messaging Server: When an Error is Not an Error
By joesciallo on Jan 03, 2008
The throw-weight of the Messaging Server documentation is quite impressive. I've been able to adjust the height of my monitor to correct ergonomic proportions with the Messaging Server Administration Guide for years now.
One thing we're missing is a comprehensive Error Guide. Such a guide would have been helpful for the following query:
Why does the ImapProxy_\* log files for Messaging Server front end hosts show the following errors:
/opt/sun/messaging/config/ImapProxyAService.cfg (sid 0x39a8bd8) SSL negotiation failed for IP xxx.xxx.xxx.xxx: Encountered end of file (-5938).
The error reports on two IP addresses, most likely due to the load balancer. Otherwise, the service is running without problems.
If only the mythical Messaging Server Error Guide were able. The user could have then discovered that the above message merely indicates that a connection was made to the IMAP SSL port on the Messaging Multiplexor (MMP), but no SSL negotiation took place. (By the way, you can reproduce this sort of behaviour by simply telnetting to the IMAP SSL port, disconnecting, and then looking at the log files.)
Cause of the error message? In general, load balancers are the culprits. Load balancers tend to connect to each back-end server port they provide load balancing services for to determine if the service is running or not, and then disconnect.
The bottom line on this error message? It's merely information, and from an administrative perspective, you needn't worry.
Hat tip AM