ECGCDRLoader 4.4

Troubleshooting and Restarting ECGCDRLoader

Check ECGCDRLoader's installation

  1. Confirm ECGCDRLoader has been configured to restart after a reboot. text $ chkconfig --list | grep ecgcdrloader ecgcdrloader 0:off 1:off 2:on 3:on 4:on 5:on 6:off
  2. Follow the installation procedure outlined in the installation guide if ECGCDRLoader is not configured to start after a reboot.

Manual Restart of ECGCDRLoader

  1. To perform a manual restart of ECGCDRLoader perform the following:
    • service ecgcdrloader restart
      • If the command is not recognized ensure the ECGCDRLoader was installed properly and the service configured as detailed in the installation guide.
      • If you encounter a permissions error as a result of the restart, review the permissions for the file reported. If the file is owned by root or a superuser attempt to restart as root or use sudo for the proper user.

Check ECGCDRLoader Status

  1. Ensure ECGCDRLoader is running:

    • service ecgcdrloader status
      • Output of the command should indicate running, if not attempt a restart.

  2. Ensure the CDRs are properly provided to the server.

    • If the CDRs are provided by NFS, confirm the nfs are mounted. text df ... as1:/bw/broadworks/billing 47221104 14548944 30266784 33% /mnt/CDRs/as1 as2:/bw/broadworks/billing 47221104 21814096 23001632 49% /mnt/CDRs/as2
    • If the CDRs are not available, review the installation steps for ECGCDRLoader and confirm NFS is configured properly.

  3. Ensure ECGCDRLoader is processing CDRs provided by the NFS.

    • ECGCDRLoader reads the CDRs once every minute.
    • Tail the active log file to confirm CDRs are being read.
      • Perform a quick call on the system to generate a new CDR to if call volume is low.
      • The following is an example of what you should see in ECGCDRLoader's logs. text $ tail -F ecgcdrloader.log 2017-10-16 13:21:11,426 WARN co.ecg.CDRProcessor - Done Sleeping 2017-10-16 13:21:11,426 WARN co.ecg.TextFileProcessor - Entering processFiles 2017-10-16 13:21:11,426 INFO co.ecg.FileStatController - getWorkFileList: Checking for new files in /mnt/CDRs/as1/archive to process 2017-10-16 13:21:11,600 INFO co.ecg.FileStatController - getWorkFileList: Checking for new files in /mnt/CDRs/as1/latest to process 2017-10-16 13:21:11,601 INFO co.ecg.FileStatController - getWorkFileList: Checking for new files in /mnt/CDRs/as1/active to process 2017-10-16 13:21:11,602 INFO co.ecg.FileStatController - Adding file for processing: BW-CDR-20171016120000-2-005056A5BEA9-004065.csv 2017-10-16 13:21:11,602 WARN co.ecg.TextFileProcessor - Adding files to fileList: [/mnt/CDRs/as1/active/BW-CDR-20171016120000-2-005056A5BEA9-004065.csv] 2017-10-16 13:21:11,602 INFO co.ecg.FileStatController - getWorkFileList: Checking for new files in /mnt/CDRs/as2/archive to process 2017-10-16 13:21:11,792 INFO co.ecg.FileStatController - getWorkFileList: Checking for new files in /mnt/CDRs/as2/latest to process 2017-10-16 13:21:11,793 INFO co.ecg.FileStatController - getWorkFileList: Checking for new files in /mnt/CDRs/as2/active to process 2017-10-16 13:21:11,795 WARN co.ecg.TextFileProcessor - Starting reprocessing BW-CDR-20171016120000-2-005056A5BEA9-004065.csv at 649619 2017-10-16 13:21:11,806 INFO co.ecg.TextFileProcessor - processCDRTextFile took 0 seconds to process 0/20 records 2017-10-16 13:21:11,807 WARN co.ecg.TextFileProcessor - processCDRTextFile: complete for BW-CDR-20171016120000-2-005056A5BEA9-004065.csv 2017-10-16 13:21:11,807 WARN co.ecg.TextFileProcessor - Exiting processFiles 2017-10-16 13:21:11,807 WARN co.ecg.CDRProcessor - Sleeping 60 seconds
      • If an Invalid File Format error is reported review the next section, for other errors document the error and contact ECG for assistance.

InvalidFileFormat Error

This error is reported when the CDR's number of fields does not match the configuration within ECGCDRLoader. Generally there are 3 causes for why this may occur.

  1. CDR entry is still being written when ECGCDRLoader processes the CDRs.

    • Tail the log file and confirm if the reported CDR entry in the InvalidFileFormat is reported again.
    • If the problem is reported again check for the other 2 possible causes below.

  2. CDR entry uses a number of fields which ECGCDRLoader is not configured to process.

    • This generally occurs after a BroadWorks patch which adjusts the fields within the CDR entries is applied.
    • Check the reported CDR entry against the CDR entry on the Application Server.
      • If the CDR entry on the application on the Application Server matches the CDR entry reported in the InvalidFileFormat, ECGCDRLoader's configuration will need to be updated. Contact ECG for assistance.
      • Otherwise check the next possible cause below.

  3. CDR entries are no longer available to the ECGCDRLoader Server.

    • This problem may be reported as an InvalidFileFormat error if the CDR entry reported was different from the CDR entry found on the Application Server.
    • This problem may also occur if an the NFS or share method used to provide the CDRs to the ECGCDRLoader Server stops working after writing a partial CDR.
      • To resolve this problem:
        • First, confirm the NFS mounts are properly configured and mounted on the ECGCDRLoader server.
        • Second, confirm any firewalls or other network devices are not blocking or hindering the CDR files shared via NFS.