Skip to main content

Messages log growing huge...

Posted by aponnath on Thu, 01/28/2021

Any idea why the message log is getting huge, i get on my console a lot of lines with thirdlane an in the message log it self there are a huge amount of lines like this, below

Jan 28 16:58:58 thirdlane '
Jan 28 16:58:59 thirdlane ], to tag []
Jan 28 16:58:59 thirdlane '
Jan 28 16:58:59 thirdlane ], to tag []
Jan 28 16:58:59 thirdlane '
Jan 28 16:58:59 thirdlane ], to tag []
Jan 28 16:58:59 thirdlane '
Jan 28 16:59:03 thirdlane ], to tag []
Jan 28 16:59:06 thirdlane ], to tag []
Jan 28 16:59:21 thirdlane ], to tag []
Jan 28 16:59:32 thirdlane ], to tag []

hopefully there is a simple fix for this


Submitted by volodya on Fri, 01/29/2021 Permalink

Hello,

What version of the system are you running? Please locate the line that starts with "#!define LOG_LEVEL" (should be near the top) in the /etc/kamailio/local.cfg configuration file. How does it look like?

/var/log/messages log file is being rotated. Is it growing too fast?

Submitted by aponnath on Fri, 01/29/2021 Permalink

Yes it grows to fast that it sometimes causes the system run out of space...
here is the debug portion of kamilio cfg
#Set log level. Check kamailio.cfg for reference
#!define LOG_LEVEL L_DBG //L_ERR
#Uncomment following line to log rejected requests
##!define LOG_REJECTED_REQUESTS

so there is nothing defined..
Also what causes the "2021 Jan 29 09:28:12 thirdlane" type of entries in my console ?

Submitted by volodya on Fri, 01/29/2021 Permalink

You have debug enabled on your system. Please replace "#!define LOG_LEVEL L_DBG //L_ERR" with "#!define LOG_LEVEL L_ERR". Then apply changes by running service kamailio restart. But make sure to do this outside of business hours because it will affect calls.

Submitted by aponnath on Sat, 01/30/2021 Permalink

Thanks that did the trick , is that the debug the default setting ? If not how did it get set as i know i never edited this file in first place

Submitted by volodya on Mon, 02/01/2021 Permalink

Hello,

No, it's not. But there was a version of the configuration that had debug enabled. It looks like you are running an older version as this was adjusted in the newer release.