My Oracle Support Banner

Solaris Cluster Shows "sccheckd: Session init failed (pex)" or "sccheckd: Session init failed (scex)" (Doc ID 1584617.1)

Last updated on DECEMBER 05, 2017

Applies to:

Solaris Cluster - Version 3.2 to 4.3 [Release 3.2 to 4.3]
Solaris Cluster Geographic Edition - Version 3.2 to 4.3 [Release 3.2 to 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)

Goal

What does the following error mean when a security port scanner software (like Qualys, IPINS or others)  is running on a Solaris Cluster node?

Aug 25 07:16:59 node1 sccheckd: [ID 904563 daemon.notice] Starting...
Aug 25 07:16:59 node1 sccheckd: [ID 871217 daemon.error] sccheckd: Session init failed (pex).

Aug 25 07:16:59 node1 sccheckd: [ID 444814 daemon.notice] Finished.

 

Oct 20 07:27:15 node1 sccheckd: [ID 386336 daemon.notice] Using existing server.
Oct 20 07:27:17 node1 sccheckd: [ID 302715 daemon.error] sccheckd: Session init failed (scex).
Oct 20 07:27:17 node1 sccheckd: [ID 444814 daemon.notice] Finished.

 

 

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.