Critical Error reported by check-cre: File not found

All documents from the original Software Support Library (SSL)

Moderators: Leon van Heerden, Lee Hendricks, Luanda_Junzi, Belinda Frick

Critical Error reported by check-cre: File not found

Postby kebogile Porogo » Tue May 22, 2018 3:42 pm

How to deal with Critical Error Reported by
CRE recording servers have a script called "check-cre.sh" which is run At 08:45 on every day-of-week from Monday through Friday.

What it does:
    1. Checks to see if the CRE is running and if there are recordings found.
    2. Checks to see if there are 5 consecutive calls without call details
    3. Checks & reports extensions seen by the CRE but not marked for recordings

Subject of the ticket: Critical Error reported by check-cre
Body of the ticket
Code: Select all
File not found for 20180321

This error messages reports that no log files could be found for the specific day

What to do:
Go and check the CRE log on that day to see if there were recordings.
Code: Select all
ls /opt/datatex/amtmitelcre/logs/20180321/*.log*

What you will see if NO files found
Code: Select all
/opt/datatex/amtmitelcre/logs/20180321/*.log: No such file or directory

What you should see if files found
Code: Select all
/opt/datatex/amtmitelcre/logs/20180322/amtmitelcre.log.gz  /opt/datatex/amtmitelcre/logs/20180322/dtxsrctunnels.log.gz  /opt/datatex/amtmitelcre/logs/20180322/voipsweeper.log.gz

Replace the dates '20180321' with days reported.
In this case, 20180321 was a Public Holiday and the client was not recording, in other cases if recordings were not found, we would need to investigate further.

Check if the CRE is running
Code: Select all
# ps auwxf | grep amtmitelcre
root     21975  0.0  0.0   8228  1660 ?        Ssl  Apr23   4:04 ./amtmitelcre -D

If you do not see ./amtmitelcre -D the CRE is not running.
kebogile Porogo
 
Posts: 46
Joined: Mon Oct 02, 2017 9:52 am

Return to Support Archive's

Who is online

Users browsing this forum: No registered users and 1 guest

cron