My Oracle Support Banner

"Could Not Stat" Error Thrown by cmnPushFiles Process (Doc ID 2075634.1)

Last updated on MARCH 19, 2019

Applies to:

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


While processing Event Data Records (EDRs), cmnPushFiles throw the below Error message in the log files:

Oct 26 08:51:05 slc04 cmnPushFiles: [ID 675952 user.error] cmnPushFiles(14126) ERROR: Could not stat /IN/service_packages/SMS/cdr/closed/ACS_201510260850500_16510.cdr: No such file or directory
Oct 26 09:25:15 slc04 cmnPushFiles: [ID 675952 user.error] cmnPushFiles(14126) ERROR: Could not stat /IN/service_packages/SMS/cdr/closed/ACS_201510260924581_16535.cdr: No such file or directory



cmnPushFiles transfers files to specific directories on the Service Management Server (SMS) from Service Logic Controllers (SLCs). The files transferred typically include:

On each SLC the cmnPushFiles can be spawned in multiple instances on different accounts: smf_oper and acs_oper (one for CDRs and one for PIN files); each instance of the cmnPushFiles daemon should be started with a separate entry in the inittab of the machine where it will run. It runs under the control of init.d:

##from inittab:
scp1:34:respawn:/IN/service_packages/SMS/bin/cmnSU - smf_oper -c "exec /IN/service_packages/SMS/bin/ >> /IN/service_packages/SMS/tmp/cmnPushFiles.log 2>&1" > /dev/null 2>&1 0<&1
acs7:34:respawn:/IN/service_packages/SMS/bin/cmnSU - acs_oper -c "exec /IN/service_packages/ACS/bin/ >> /IN/service_packages/ACS/tmp/cmnPushFiles.log 2>&1" > /dev/null 2>&1 0<&1


The mostly used start-up command_line in   

##for smf_oper -> user for CDRs:
    exec /IN/service_packages/SMS/bin/cmnPushFiles -d /IN/service_packages/SMS/cdr/closed -f /IN/service_packages/SMS/cdr/retry -r /IN/service_packages/SMS/cdr/received -h -s 10 -p 2028 -S cdr
    ##for acs_oper -> used for PIN files:
    exec /IN/service_packages/ACS/bin/cmnPushFiles -d /IN/service_packages/SMS/cdr/closed -f /IN/service_packages/SMS/cdr/retry -r /IN/service_packages/SMS/cdr/received -h -s 10 -p 2028 -P PIN -S txt

Parameters from above:
    -d <dir> -> Scan Directory. The directory to search for files to transfer to the receiving side. cmnPushFiles will only transfer those files matching a pattern. See -P or -S.
    -f <dir> -> The retry directory. Cannot be the same as -d <dir>;
    -r <dir> -> Remote directory prefix. Required if -d <dir> (on page 130) is a relative directory.
    -h <host> -> The hostname of the remote machine.
    -s <secs> -> The re-scan interval (The number of seconds for the sleep period). After cmnPushFiles has scanned its input directory and found no files to transfer, it goes to sleep for a configurable interval. To change this interval, specify the number of seconds to sleep after the -s.
    -p <port> -> The port number on the remote machine on which cmnReceiveFiles will listen for receiving files (Port to connect to).
    -S <suffix> -> The file suffix.
        Example: -S cdr: will cause all files matching *cdr in the source directory to be transferred.
    -P <prefix> -> Match Pattern. Specify a filename prefix that must be matched in order to qualify a file for transfer to the remote side.
        Example: -P PIN will cause all files matching PIN* in the source directory to be transferred.


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

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