Can I Delete Chronicall Logs to Clear Up Space on My Hard Drive?

Answer

Yes, you can delete older Tomcat .txt logs if they're taking up too much room. We'd recommend keeping recent ones in case any recent issues need to be diagnosed.

Steps

1. Log on to the Chronicall server and navigate to one of the file paths below to review logs that may no longer be needed.

   32-Bit — Chronicall

   • C:\Program Files (x86)\Xima Software\Chronicall\tomcat\logs (Chronicall troubleshooting logs)
   • C:\Program Files (x86)\Xima Software\Chronicall\logs (raw .xml logs from PBX)
   • C:\Program Files (x86)\Xima Software\Chronicall\bin\app (.hprof memory dump logs)
   • C:\Program Files (x86)\Xima Software\Chronicall\recording library\logs (Recording Library logs, if you use voice recording)

   64-Bit — Chronicall

   • C:\Program Files\Chronicall\tomcat\logs (Chronicall troubleshooting logs)
   • C:\Program Files\Chronicall\logs (raw .xml logs from PBX)
   • C:\Program Files\Chronicall\recordinglibrary\logs (Recording Library logs, if you use voice recording)

   64-Bit — Avaya Call Reporting

   • C:\Program Files\Avaya Call Reporting\tomcat\logs (Chronicall troubleshooting logs)
   • C:\Program Files\Avaya Call Reporting\logs (raw .xml logs from PBX)
   • C:\Program Files\Avaya Call Reporting\recordinglibrary\logs (Recording Library logs, if you use voice recording)

   Multimedia Server — 32-Bit Chronicall

   • C:\Program Files (x86)\Xima Software\Chronicall\multimedia\logs (Multimedia troubleshooting logs)
   • C:\Program Files (x86)\Xima Software\Chronicall\multimedia\bin\app (.hprof memory dump logs)

   Multimedia Server — 64-Bit Chronicall

   • C:\Program Files\Chronicall\multimedia\logs (Multimedia troubleshooting logs)
   • C:\Program Files\Chronicall\multimedia\bin\app (.hprof memory dump logs)

   Multimedia Server — Avaya Call Reporting

   • C:\Program Files\Avaya Call Reporting\multimedia\logs (Multimedia/Contact Center troubleshooting logs)
   • C:\Program Files\Avaya Call Reporting\multimedia\bin\app (.hprof memory dump logs)

   Linux — 32-Bit Chronicall

   • var/lib/Xima Software/Chronicall/tomcat/logs (Chronicall troubleshooting logs)
   • var/lib/Xima Software/Chronicall/recording library/logs (Recording Library logs, if you use voice recording)
   • var/lib/Xima Software/Chronicall/multimedia/tomcat/logs (Multimedia troubleshooting logs)
   • var/lib/Xima Software/Chronicall/bin/app (.hprof memory dump logs)

   Linux — 64-Bit Chronicall

   • var/lib/Chronicall/tomcat/logs (Chronicall troubleshooting logs)
   • var/lib/Chronicall/logs (raw .xml logs from PBX)
   • var/lib/Chronicall/bin/app (.hprof memory dump logs)

   Linux — 64-Bit Avaya Call Reporting

   • var/lib/avaya call reporting/tomcat/logs (Chronicall troubleshooting logs)
   • var/lib/avaya call reporting/logs (raw .xml logs from PBX)
   • var/lib/avaya call reporting/bin/app (.hprof memory dump logs)

2. You can delete any older logs you don't think will be necessary — we'd recommend keeping the last two weeks for troubleshooting. The system won't let you delete logs that are currently in use.

   📘

   Note

   If Chronicall is creating large logs at an alarming rate, feel free to contact Xima Support to see if there's an underlying issue, or an advanced form of logging turned on in the advanced settings.