<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
font-size:10.0pt;
font-family:"Courier New";}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:"Consolas",serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:768357303;
mso-list-type:hybrid;
mso-list-template-ids:2128664156 1153049614 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";
mso-fareast-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks all for your information.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now this morning on live SIP Proxies, I have configured the /etc/systemd/journald.conf with :<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>RateLimitIntervalSec=0<br>RateLimitBurst=0<o:p></o:p></p><p class=MsoNormal>I have restarted the journald/rsyslog services. But few seconds later, the logging still stop again.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have applied the other values suggested in the old article:<o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>RateLimitBurst=1000000 in /etc/systemd/journald.conf <o:p></o:p></p><p class=MsoNormal style='margin-left:36.0pt'>$imjournalRatelimitInterval 1 and $imjournalRatelimitBurst 500000 in /etc/rsyslog.conf<o:p></o:p></p><p class=MsoNormal>With the above values, I have new no more logs issues like reported in the article.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The above issue is a pure OS problem and I will probably open a ticket to RedHat.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Now back on my initial question related to journald. <o:p></o:p></p><p class=MsoNormal>On my SIP Proxies, journald is using about 10% of the CPU configured, which is very high when Kamailio used about 1%.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I’m looking to replace the current mechanism to write log thru the standard openlog() and syslog() functions. I assume this is done using the ‘xlog’ module.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Do you think possible to change this by a mechanism to send log messages thru UDP to write the logs directly to rsyslog, <o:p></o:p></p><p class=MsoNormal>meaning to replace all the xlog calls in the kamailio.cfg script ?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='mso-element:para-border-div;border:none;border-top:solid #CCCCCC 1.0pt;padding:4.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-bottom:3.0pt;border:none;padding:0cm'><b><span lang=FR-BE style='color:#444444'>Cordialement.<o:p></o:p></span></b></p><p class=MsoNormal style='margin-bottom:3.0pt;border:none;padding:0cm'><b><span lang=FR-BE style='color:#444444'>Patrick GINHOUX</span></b><span lang=FR-BE style='color:#444444'> <b><o:p></o:p></b></span></p></div><p class=MsoNormal style='margin-bottom:3.0pt'><span lang=FR-BE style='font-size:9.0pt;color:#444444'>Unisys | +33 1 46 69 52 12 </span><span lang=FR style='font-size:9.0pt;color:#444444'>| +33 6 60 32 24 74</span><span lang=FR style='font-size:9.0pt;color:#444444'> </span><span lang=FR style='font-size:9.0pt;color:#444444'>| patrick.ginhoux@unisys.com</span><span lang=FR><o:p></o:p></span></p></div><p class=MsoNormal><span lang=FR><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=FR>De :</span></b><span lang=FR> Sergey Safarov <s.safarov@gmail.com> <br><b>Envoyé :</b> mercredi 24 novembre 2021 21:49<br><b>À :</b> Daniel-Constantin Mierla <miconda@gmail.com>; Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org><br><b>Cc :</b> Ginhoux, Patrick <patrick.ginhoux@fr.unisys.com><br><b>Objet :</b> Re: [SR-Users] How to not write logs to journald with kamailio<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div style='border:solid #060606 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt'><p class=MsoNormal style='line-height:12.0pt'><b><span style='font-size:10.0pt;color:black'>EXTERNAL EMAIL - Be cautious of all links and attachments.<o:p></o:p></span></b></p></div><div><div><p class=MsoNormal>you need configure journald config file <o:p></o:p></p><div><p class=MsoNormal>/etc/systemd/journald.conf<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[root@bcf-b ~]# grep RateLimit /etc/systemd/journald.conf<br>RateLimitIntervalSec=0<br>RateLimitBurst=0<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Nov 24, 2021 at 7:50 PM Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p>Hello,<o:p></o:p></p><p>kamailio uses internally openlog() and syslog() functions from standard libc. It has not control of what the syslog daemon does, it is a matter of OS configuration, so what you mention might be the required configuration, not a workaround. Anyhow, maybe others can comment more.<o:p></o:p></p><p>There are many other cases when the OS has to be tuned to get desired behaviour, eg., increase file descriptor limits to handle lots of connections.<o:p></o:p></p><p>Cheers,<br>Daniel<o:p></o:p></p><div><p class=MsoNormal>On 23.11.21 12:16, Ginhoux, Patrick wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I resend this mail because of the initial destination address was not correct.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The topic was a logging problem :<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>With the upgrade of my SIP Router proxies to RHEL 7 (and Kamailio 5.0.7) , we encounter problems where the logs are blocked to be written in the syslog.</span><o:p></o:p></pre><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt'>This problem is similar as the one reported in this article : <a href="https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html" target="_blank">[SR-Users] Kamailio logs in RHEL 7 environment</a>.<o:p></o:p></p><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>The resolution was to increase some journald/rsyslog settings (RateLimitBurst=1000000 / $imjournalRatelimitInterval 1 $imjournalRatelimitBurst 500000).</span><o:p></o:p></pre><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>But it is somehow a workaround. </span><o:p></o:p></pre><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>I’m looking to know if it should be possible for kamailio to write directly the logs to the syslog only.</span><o:p></o:p></pre><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><pre style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Thanks in advance to those can help me.</span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Patrick Ginhoux<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=FR> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>De :</b> Ginhoux, Patrick <br><b>Envoyé :</b> lundi 22 novembre 2021 16:49<br><b>À :</b> 'sr-users' <a href="mailto:sr-users-bounces@lists.kamailio.org" target="_blank"><sr-users-bounces@lists.kamailio.org></a><br><b>Objet :</b> How to not write logs to journald with kamailio<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>With the upgrade of my SIP Router proxies to RHEL 7 (and Kamailio 5.0.7) , we encounter problems where the logs are blocked to be written in the syslog.</span><o:p></o:p></pre><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This problem is similar as the one reported in this article : <a href="https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html" target="_blank">[SR-Users] Kamailio logs in RHEL 7 environment</a>.<o:p></o:p></p><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>The resolution was to increase some journald/rsyslog settings (RateLimitBurst=1000000 / $imjournalRatelimitInterval 1 $imjournalRatelimitBurst 500000).</span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>But it is somehow a workaround. </span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>I’m looking to know if it should be possible for kamailio to write directly the logs to the syslog only.</span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Thanks in advance to those can help me.</span><o:p></o:p></pre><pre><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></pre><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Patrick Ginhoux<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><pre>__________________________________________________________<o:p></o:p></pre><pre>Kamailio - Users Mailing List - Non Commercial Discussions<o:p></o:p></pre><pre> * <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><o:p></o:p></pre><pre>Important: keep the mailing list in the recipients, do not reply only to the sender!<o:p></o:p></pre><pre>Edit mailing list options or unsubscribe:<o:p></o:p></pre><pre> * <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><o:p></o:p></pre></blockquote><pre>-- <o:p></o:p></pre><pre>Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">www.asipto.com</a><o:p></o:p></pre><pre><a href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a><o:p></o:p></pre><pre>Kamailio Advanced Training - Online<o:p></o:p></pre><pre> Feb 21-24, 2022 (America Timezone)<o:p></o:p></pre><pre> * <a href="https://www.asipto.com/sw/kamailio-advanced-training-online/" target="_blank">https://www.asipto.com/sw/kamailio-advanced-training-online/</a><o:p></o:p></pre></div><p class=MsoNormal>__________________________________________________________<br>Kamailio - Users Mailing List - Non Commercial Discussions<br> * <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>Important: keep the mailing list in the recipients, do not reply only to the sender!<br>Edit mailing list options or unsubscribe:<br> * <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><o:p></o:p></p></blockquote></div></div></div></body></html>