My Oracle Support Banner

Kill -USR1 Signal to CM Fills Children to Maximum (Doc ID 1336349.1)

Last updated on MAY 09, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Linux x86-64

Symptoms

Passing kill -USR1 signal to CM, it is updating the children count to maximum allowed, and CM can not be connected after that.

Steps to re-produce :

  1. Open the cm pin.conf and make the following entry
    #==================================================================
    # cm_max_connects
    #
    # Specifies the maximum number of client connections to the CM.
    #
    # The parent CM listens on the port for new connections and spawns a
    # child process for each one. Use this entry to limit the maximum number
    # of child CMs that are spawned by a single CM parent process (or thread).
    #==================================================================
    - cm cm_max_connects 100
  2. Restart cm
  3. Clear cm pinlog
  4. Do a kill -USR1 <proc id>
  5. See that the nkids is set to 1 in the cm.pinlog
  6. Run kill -USR1 to the same proc id again without clearing the logs
  7. See that the nkids gets set to 100 (which should not be the case.)
  8. Run testnap, the following error can be seen :
    ERROR: testnap: PCM_CONNECT():: err 49:PIN_ERR_STREAM_IO, field 0/0:0,
    loc 0:Unknown pin location, errclass 3:PIN_ERRCLASS_SYSTEM_RETRYABLE, rec_id 0, resvd 0

The only option now is to kill the cm since it no longer accepting any connection.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


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