[SR-Users] xlog issue

[Daniel-Constantin Mierla]

Hello,

typically syslog has some rate limiting, and with centos, you get extra
limits with selinux. You have to dive into rsyslog, system config and
selinux.

What you can do is to start with log_stderror=yes (or -E command line
option) and see if it is printing the messages you are looking for to
the terminal. You can eventually direct sderror to a file to be easier
to search/match...

Cheers,
Daniel

On 04.12.18 10:40, Soltanici Ilie wrote:
> Hello,
>
> Actually, async Syslog option was the initial option which I tried -
> it wasn't working properly so I changed to a synchronous mode in the
> hope that it will work better, but unfortunately it didn't.
>
>     Daniel-Constantin Mierla <miconda at gmail.com>:
>
>     Hello,
>
>     try with async syslogging option in rsyslog config: add a - in
>     front of the file name, like:
>
>     local0.*             -/var/log/kamailio/kamailio.log
>
>     See if the results are better.
>
>     Cheers,
>     Daniel
>
>     On 02.12.18 16:14, Soltanici Ilie wrote:
>>
>>     Hello,
>>
>>     I have a strange situation by using xlog module. I don't know for
>>     what reason I'm not receiving all logs generated by kamailio.
>>
>>     This is the configuration which I'm using in kamailio.cfg:
>>
>>     log_facility=LOG_LOCAL0
>>     log_name="kamailio"
>>     log_prefix="{$rm ($mt) | Seq=$cs | Source IP=$si ($proto) | Call
>>     ID=$ci} "
>>
>>     # ----- xlog -----
>>     modparam("xlog", "buf_size", 8192)
>>     modparam("xlog", "long_format", 0)
>>     modparam("xlog", "force_color", 1)
>>     modparam("xlog", "log_colors", "L_ERR=cr;L_WARN=px,L_INFO=px")
>>
>>     This is rsyslog configuration file:
>>     local0.*             /var/log/kamailio/kamailio.log
>>
>>     Kamailio is running under kamailio user, permission for the log
>>     file are as shown below:
>>     -rwxrwxr-x 1 kamailio kamailio 252885132 Dec  2 14:51
>>     /var/log/kamailio/kamailio.log
>>
>>     In request_route block this is the first line:
>>
>>     xlog("L_INFO","[START ROUTING]-(Source IP=$si:$sp/Destination
>>     IP=$Ri:$Rp)\n");
>>
>>     The problem is that not every request is logged in the log-file.
>>     For example, some "INVITES" requests I can find in the log file,
>>     but some of them - I cannot, even that in sngrep I see the
>>     request and the call is successfully processed by kamailio. Also,
>>     for some requests i can see only partial data, not full call-flow
>>     as it supposed to be (for ex. i see only BYE requests, or ACK
>>     response instead of full call flow).
>>
>>     Does someone have the same issue? If you don't - how are you
>>     dealing with kamailio log files? I'm thinking to send them to the
>>     central ELK stack, but if I have such problems by saving them
>>     locally - I don't see any reason to send them elsewhere.
>>     I may think that the problem could be in rsyslog itself, but how
>>     can I troubleshoot that?
>>
>>     The traffic on the server is not very high - 30-50 concurrent
>>     calls. As a storage i'm using an SSD disk and xfs filesystem.
>>     Load on the disk - according to iostat/iotop - is minimum. 
>>
>>     OS: CentOS Linux 7 (Core), Kamailio: 5.2.0 (x86_64/linux) 535e13
>>     Thank You.
>>
>>
>>     _______________________________________________
>>     Kamailio (SER) - Users Mailing List
>>     sr-users at lists.kamailio.org
>>     https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>     -- 
>     Daniel-Constantin Mierla -- www.asipto.com
>     www.twitter.com/miconda -- www.linkedin.com/in/miconda
>     Kamailio World Conference -- www.kamailioworld.com
>     Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
>
-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20181204/1a8df8e8/attachment.html>