SLEE Applications Failing to Start with CRITICAL Alarm "SleeException: Temp file not found (1) in sleeShmManager.cc at ABC by process id XYZ errno(2) - No such file or directory" (Doc ID 2150218.1)

Last updated on JULY 18, 2017

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (NCC), all Service Logic Execution Environment (SLEE) applications rely on ftok() (when called with a file name) to return a key which can be used to address the SLEE shared memory.

The temporary SLEE file used is based on the SLEE_FILE environment variable which when unset, will default to /tmp/slee.  If this file does not exist when the SLEE first starts up, it is created.

No NCC application deletes this file.

If this file is accidentally deleted, then any new applications trying to connect to the SLEE will throw the following error:

CRITICAL SleeException=2 sleeError.cc@53: SleeException: Temp file not found (1) in sleeShmManager.cc at 124 by process id 12286 errno(2) - No such file or directory

and upon startup, will fail since it is not able to communicate with any running SLEE applications.  This includes the scripts/binaries used to stop the SLEE if the file is deleted while the SLEE is running.

Changes

Deletion of /tmp/slee.

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