Messaging 7, SSL Initialization Fails After Installing Solaris Patches (Doc ID 1448959.1)

Last updated on JANUARY 11, 2017

Applies to:

Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 27-Jan-2014***

Symptoms

Messaging 7 patch 137204-12, with Solaris Crypto Framework (SCF).

After Solaris patches were applied on a Messaging Server system, the Messaging IMAP, POP, HTTP and SMTP SSL failed to start up.

Sample of POP proxy log:

20120302 201521 PopProxyAService.cfg ASockSSL_Init: PK11 auth failed to Sun Metaslot (-8127)
20120302 201521 PopProxyAService.cfg Messaging Multiplexor (Sun Java(tm) System Messaging Server 7.3-12.01 (built Oct 15 2009)) started
20120302 201525 PopProxyAService.cfg (id 4) session start, client IP 123.12.12.12:43697, server IP 123.12.12.2:110
...
20120302 201555 PopProxyAService.cfg (id 52) SSL negotiation failed for IP 123.12.12.13: Cannot connect: SSL is disabled. (-12268)

 

Summarising the conditions where this problem occurs:

- Messaging Server 7 running SSL with Solaris Crypto Framework / SSL hardware accelerator, and

- the user that starts up the Messaging Server (e.g. root) is not the same as the user that Messaging Server runs as (e.g. mailsrv), and

- Solaris 10 pkcs11 patch 144542-03 or later is applied.

 

Changes

Solaris patches were applied just before the problem started.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms