Server disk filled up due to re-registrations

[n8tive]

3CX Version: Professional Annual 16.0.9
Server OS: Debian 9
Is the 3CX Server Hosted and where? Virtual server hosted by South African company
IP Phone Make/Model/Firmware: Yealink SIP-T33G 124.85.0.40
Provisioning Method: STUN
Trunk Provider: Dataphone
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: YES

Hi

We had a strange problem today where the IP phones constantly registered and filled up the server logs (the server log folder ended up to be 7.5Gb).

Below is a snippet of the log file: 3cxManagementConsole.162155.log

2021/06/22 16:21:05.735|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.0044ms
2021/06/22 16:21:05.735|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.0096ms
2021/06/22 16:21:05.735|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.0035ms
2021/06/22 16:21:05.735|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.0029ms
2021/06/22 16:21:05.736|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.003ms
2021/06/22 16:21:05.736|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.0038ms
2021/06/22 16:21:05.736|926|0007|Trc|Updated REGISTRAR:Wregistration.234: - Wextension.25: 202 - [ V4 **OMITTED**:1026 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0e65ff1 - 0.006ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0024ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0033ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0027ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0042ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0029ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0057ms
2021/06/22 16:21:05.754|926|0007|Trc|Updated REGISTRAR:Wregistration.236: - Wextension.27: 302 - [ V4 **OMITTED**:1027 UDP flowKey=15 transportKey=1 ] - 6/22/2021 2:23:05 PM - Yealink SIP-T33G 124.85.0.40 805ec0eb6646 - 0.0028ms

It's endless re-registrations and I basically would like to know if anyone had this problem before and any suggestions on how to fix this problem and prevent it from happening again.

 

[JohnS_3CX]

What Logging level is 3CX set to now?

 

[n8tive]

Hi

Medium

 

[JohnS_3CX]

Hello,

Set it to Low, keep a backup of 1 days (or disable log backup too - this can also take up space).

Use the Purge button to clear your old logs and reclaim disk space.

Restart All your 3CX Services to reset the the current logs too.



Even on medium, logs will eventually start eating up your disk space. We recommend to keep it on Low by default, and only increase it if you have actual problems that require reading rich logs.

 

[n8tive]

Ok, thanks