Recharge Notifications Not Working and ccsCDRLoader Logs Message 'WARNING: RechargeSMSPlugin: Couldn't open FIFO'
(Doc ID 1352958.1)
Last updated on APRIL 19, 2021
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 and laterInformation in this document applies to any platform.
Symptoms
- Subscribers may report that recharge notifications are not working.
- The syslog on the SMS shows the following errors accessing a "first in, first out" (FIFO) file, indirectly indicating a notification problem:
Changes
None.
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 |
| The ccsCDRLoader plugin and ccsSSMDispatcher are configured to use different FIFO file names. |
| ccsCDRLoader is running on the machine but the ccsSSMDispatcher is not. |
| ccsSSMDispatcher is running but the FIFO file mentioned in the error message does not exist. |
| In a clustered SMS environment the ccsCDRLoader may be running on one node and ccsSSMDispatcher is running on another node. |
| The permissions on the FIFO are incorrect and ccsCDRLoader cannot send notifications. |
| Solution |
| The ccsCDRLoader plugin and ccsSSMDispatcher are configured to use different FIFO file names. |
| ccsCDRLoader is running on the machine but the ccsSSMDispatcher is not. |
| ccsSSMDispatcher is running but the FIFO file mentioned in the message does not exist. |
| In a clustered SMS environment the ccsCDRLoader may be running on one node and ccsSSMDispatcher is running on another node. |
| The permissions on the FIFO are incorrect and ccsCDRLoader cannot send notifications. |
| Final Notes |
| References |