“3CXPhoneSystem.trace.log” already over 2.7GB

[5qg4]

My “3CXPhoneSystem.trace.log” already over 2.7GB. It growth around 300MB daily. Is it normal or not? Any max. log file size controlled by the 3CX Phone system. At ini file the max. log file size is 2048KB. How come my log file over 2.7GB.

My production version still 3CX Phone System Version3.0.2328.0 running on Windows XP pro. Please advice.

 

[archie]

Please, post here the portion of your INI file, containing section [CallManager\Logger\Outputs\TraceFile]

Have you restarted service after changing settings for MaxFileSizeKB value?

 

[5qg4]

Hi Archie,

Please find the portion of your INI file, containing section [CallManager\Logger\Outputs\TraceFile] as below:

[CallManager\Logger\Outputs\TraceFile]
File=3CXPhoneSystem.trace.log
Level=20
Format=$ShortDT|$FileLine|$Severity$Level|$Subsystem|$Method:
Severity=Log Error Critical Debug Trace Message
MaxFileSizeKB=20480

Since I haven't changed any value before at INI. Therefore, the default value is 20MB. I just upgraded to current version 3CX Phone System v3.1.2434.0. I will keep monitor the trace log file size. To see it can be fixed by current version or not.

Thanks,
5QG4

 

[archie]

Let us know if the problem persists in latest version.

 

[5qg4]

Hi Archie,

I also hit the issue by in place upgrade. The error as below:

21:44:01.265 DBPostgressAccessor:utHistory ERROR: duplicate key violates unique constraint "history_pkey"
21:44:01.265 DBPostgressAccessor:utHistory ERROR: duplicate key violates unique constraint "history_pkey"

To fixed this issue still by restore the system backup file again. I found this issue from Build 2295 to 2328 and Build 2328 to 2434.

Regards,
5QG4