Call recording DISABLED after logs fill drive

[Callinectes]

This morning we were alerted to a system that had an issue with its drive reaching capacity. After investigation we found the system running at 100% CPU usage and the logs for the 3CX conference service completely filled the drive. There were about 4300 10GB log files created between about 4AM and 7AM. We rebooted the system which corrected the error and we cleared the log files to free up space but the system now shows recording as DISABLED and I assume this is a protection against recordings completely filling the drive (where it should have been those log files). Can someone please tell me how to re-enabled the recordings? Screenshot of recordings being disabled below. Note this system is running on VMWare and is the latest release V20 u2 (715) with 64GB drive, 4GB RAM, and 2 vCPUs on VMWare.

 

[Callinectes]

Well, nevermind. It appears they re-enabled on their own. By the time I checked again the DISABLED message was gone.



Someone may want to log this issue as a bug. Below is the message (verbatim - copy and pasted) from the log that repeated probably millions of times:

05:09:19.854|7fed577fe6c0| Info|DBServ.cpp(547): SL:Application '' is not initialized
05:09:19.854|7fed9f1d86c0| Info|DBServ.cpp(547): SL:Startup completed for
05:09:19.854|7fed9f1d86c0| Info|DBServ.cpp(547): SL:ConnectionThread. Application start failed
05:09:19.854|7fed9f1d86c0| Info|DBServ.cpp(547): SL:ConnectionThread. Initialization of new connection is completed.
05:09:19.854|7fed9e1d66c0| Info|DBServ.cpp(547): SL:Application '' is not initialized
05:09:19.854|7fed9e1d66c0| Info|DBServ.cpp(547): SLDestroying SLAPPImpl::~SLAPPImpl():127.0.0.1:5485<->127.0.0.1:35946
05:09:19.854|7fed9e1d66c0| Info|DBServ.cpp(547): SLDestroyed SLAPPImpl::~SLAPPImpl():127.0.0.1:5485<->127.0.0.1:35946
05:09:19.854|7fed9e1d66c0| Info|DBServ.cpp(547): SL:Closing socket channel(8) 127.0.0.1:5485<->127.0.0.1:35946
05:09:19.854|7fed9e1d66c0| Info|DBServ.cpp(547): SL:Socket channel has been closed 8
05:09:19.855|7fed9f1d86c0| Info|DBServ.cpp(547): SL:ConnectionThread. Accepting new connection
05:09:19.855|7fed9f1d86c0| Info|DBServ.cpp(547): SL:ConnectionThread. Connection from: '127.0.0.1' has been accepted
05:09:19.855|7fed9f1d86c0| Info|DBServ.cpp(547): SL:ConnectionThread. Configuring new socket.
05:09:19.855|7fed9f1d86c0| Info|DBServ.cpp(547): SL:ConnectionThread. Starting new application
05:09:19.855|7fed9f1d86c0| Info|DBServ.cpp(547): SL:Socket channel(8) 127.0.0.1:5485<->127.0.0.1:35960
05:09:19.855|7fed9f1d86c0| Info|DBServ.cpp(547): SL:Stage 1: no appID specified
05:09:19.855|7fed9f1d86c0|Error|DBServ.cpp(94): UNKNOWN application from 127.0.0.1:35960 to 127.0.0.1:5485. Conenction rejected: connection protocol failed

 

[JohnS_3CX]

Hi Kevin,

Please open a ticket so we can investigate further.

 

[TheodorosG_3CX]

Are WEBRTC logs enabled for this installation?