Logs Locked Crash
Issue
An unexpected and abrupt shutdown of all the channels within an Iguana instance. Distinct from actual crashes in that the service remains up and running
Commonly accompanied with a red warning statement:
The log index commit system has failed. Possible reasons:
– The disk has run out of space.
– An external process (such as antivirus or backup software) is locking files in the log system,
or has changed the file permissions.
– Some other unknown I/O error occurred, please provide this error to iNTERFACEWARE.
Possible Causes
Log files are locked by another process, such as antivirus or backup software, for more than 30 minutes, causing Iguana to go into safe mode and shut down all the channels
Disk is out of space - check the log usage statistics <iguana_url>:<web_serv_port>/log_usage_statistics
Log index corruption, possibly from ungraceful service shutdowns or processes locking the logs
Possible Solutions
Restarting the service will usually clear the error and get the channels back up and running for a short-term solution
Logs locked:
Ensure that the log directory is whitelisted from any antivirus or backup software process (see help doc https://help.interfaceware.com/v6/prevent-antivirus-and-backup-software-locking-iguana-index-files)
Change the Iguana log purge time to a different time than when your backup program runs, ideally during a time of day with low-volume traffic
Ensure only "*.log"Â files that are older than one day are backed up.
Corrupted log index files:
Stop the service, delete the log index and meta files, and restart the service to regenerate the files
Shortening the log purge time can reduce the chances of index file corruption