Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: soporte_sd on October 30, 2017, 03:28:59 PM
-
Hi all,
SIPServer is showing the following alarm 'Unable open log file' and some log files are not written. After that the SIPServer behaviour becomes unstable and we are forced to do a manual switchover to solve the issue.
Have you ever had the same issue?
Why does writing logs issue is affecting SIPServer application in such a way?
Best regards,
-
Most projects I have worked on, log files are the point that mostly consumes I/O on a Server/Virtual Server, causing unexpected behavior on applications (specially SIP Servers and Stat Servers). This is more impacting in virtual servers, where the Virtual Disk is accessed via network through iSCSI.
The thing is, as the processing of a thread is sequential, that thread is "blocked" until it finishes its current execution - in that case, write to the log file.
Check if you do have enough space on the partition;
On linux, check the limits of Max Open Files; Check the quota for the user;
Check the permissions to write the logs; Check if no other process is accessing that log file with exclusice acess.
On a virtual server, check the hypervisor monitoring tool for delays on I/O writes; Check the storage if it has write-through or write-back caching.
We usually leave production applications on "Standard" log verbose level, switching to "all"/"debug" only when a troubleshooting is needed.
This behavior is also true in other kinds of systems. The software/hardware provider usually recommends to only enable debugging when needed.