OID DIP 10g (odisrv) Process For Provisioning Suddenly Fails: Sgslupscheckprocess: Sigsend To Pid <Pid#> Failed, Os Error = 3 (Doc ID 783236.1)

Last updated on NOVEMBER 07, 2019

Applies to:

Symptoms

• Oracle Internet Directory (OID) Directory Integration Platform (DIP) had previously working odisrv Provisioning process, on instance=1 configset=0, suddenly failed to run.
  
  For OID version 10.1.4 or higher, running  oidctl connect=<SID> status  returns:
  
  
  Checking ODISRV instance 1 ...
  sgslupsCheckProcess: sigsend to pid <PID> failed, os error = 3
  Process odisrv is not running
• oidmon keeps attempting to restart it, which fails with the same above error logged in  $ORACLE_HOME/ldap/log/oidmon.log.
  
  OID version 10.1.4.2 or higher $ORACLE_HOME/ldap/log/odisrv01.log shows error:
  
  
  =====================================================
  Copyright (c) 2002-2007, Oracle Corporation. All rights reserved.
  Oracle Directory Integration Server:Version 10.1.4.2.0 Production
  Oracle Directory Integration Server instance# 01 started..
  Fri Feb 13 14:00:29 CST 2009 : Starting Server to execute Profile Group :default against LDAP
  Server (<HOSTNAME>:<PORT>)
  Fri Feb 13 14:00:29 CST 2009 : Retrieved Credentials from Local Wallet
  Fri Feb 13 14:00:29 CST 2009 : Connection to LDAP Server Successful
  Fri Feb 13 14:00:29 CST 2009 : SSL Mode :0
  Fri Feb 13 14:00:29 CST 2009 : Connecting to LDAP...
  Fri Feb 13 14:00:39 CST 2009 : DIP Server Instance Entry Exists : 1
  Fri Feb 13 14:00:39 CST 2009 : DIP Server Instance Entry Created By OIDMON
  Fri Feb 13 14:00:39 CST 2009 : DIP Server Instance Entry Exists : 1
  Fri Feb 13 14:00:39 CST 2009 : ODI Server Instance Registration Failure : java.lang.Exception: Connector group : DEFAULTGROUP Already Being Executed By instance 2
  Cannot start another Instance with the same connector group.
  Error Registering Server Instance ..
  Fri Feb 13 14:00:39 CST 2009 : Exiting with Status -1: null
  =====================================================
  
  Note:   The error could also be as follows:
  
  
  Wed Jul 25 23:24:22 PDT 2007 : ODI Server Instance Registration Failure :
  java.lang.Exception: Connector group : DEFAULTGROUP Already Being Executed By instance 2
  Cannot start another Instance with the same Config Set..
  Error Registering Server Instance ..
  
  Note:  For OID 10.1.2 or lower, the error may be:
  
  
  Fri Oct 22 13:21:24 GMT-07:00 2004 : MAIN: Error Registering ODI Server Instance : java.lang.Exception: Config Set : 1 Already Being Executed By instance 2
  Cannot start another Instance with the same Config Set..
  Exception while validating config sets/profile Groups..
  Error Registering Server Instance ..
• Double-checking the other odisrv process (sync on instance=2 configset=1), it is found to be running with no errors in its corresponding $ORACLE_HOME/ldap/log/odisrv02.log
• The following also do not help:
  
  • Stopping both odisrv processes with oidctl.
  • Stopping and restarting OID with 'opmnctl stopall' then 'opmnctl startall'.
  
  
  • Double-checking that no other DIP odisrv processes were running, with command:
    
    
    ps -ef | grep odisrv
  
  
  • Cleanly restarting the OID LDAP server only with opmnctl startproc ias-component=OID.
  
  
  • Starting only the odisrv for Prov as per <Document 462523.1> for OID version 10.1.4.2 and higher:
    
    
    oidctl connect=<SID> server=odisrv instance=1 configset=0 flags="host=<OID_HOSTNAME> port=<OID_NONSSL_PORT> grpid=default debug=63" start
    
    Or as per <Document 262985.1> for OID version 10.1.4.0.1 and lower.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.