Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

IMG 1010 - Log File Management

The IMG manages the logs files so there is never more than one days worth of log files in the log directory. Each day at approximately 23:00 the complete log file directory is zipped up and roll over into a directory named zipfiles which is located in the  /opt/dialogic/common directory. The newly created files in the log directory will then re-start accumulating data for that day.  

The IMG also doesn't allow log files to be overwritten or to continue to grow indefinitely. When starting GCEMS and ClientView the log files will be created. If ClientView and/or GCEMS is stopped and restarted, new log files will get created. The new files will have a new Process ID appended to the end of the filename. The old file will not be overwritten. For example, if ClientView and GCEMS are started and they are communicating with an IMG a file named socket.log will get created. If for some reason the GCEMS reboots, that socket.pid.log file will be archived and a new socket.pid.log will be created. The logfile will once again contain current information. As explained above all log files are zipped and archived each day so that there should never be more than 1 days worth of log files in the log directory

Log Directory:

The log files are written to the /opt/dialogic/common/log directory.

Close Time:

You can specify the time the file is closed by modifying the default behavior. By default, each file is closed every day at 23:00 local time. The environment variable SK_FILE_CLOSEOUT_HOUR can be used to modify the time to close the files. The default is 0 (midnight).

Maximum Size:

SK_FILE_MAX_SIZE specifies the size, in megabytes, to which the log file is allowed to grow before cycling. When a log cycles because the size is too big, the existing timer is not reset. The log will still cycle at the proper time.

Debugging Channel Management Issues:

There is additional logging available to debug channel management issues. As this is CPU-intensive logging, it should only be done with the help of an Sangoma support engineer. Please contact Sangoma technical support for assistance.

  • No labels