Hello Yuri, Perfect !
Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 11/14/2013 04:15 PM, Yuri Ritvin wrote: > Thank you, Bogdan. > You are absolutely right. OpenSIPS is OK. > I made an "investigation" and found a culprit - an rsyslog.conf got > corrupted from an automated action taken by Puppet ... > I restored the rsyslog.conf from a backup and the log normal operation > has been resumed. > > Thanks a lot ! > Yuri > > > On Thu, Nov 14, 2013 at 5:16 AM, Bogdan-Andrei Iancu > <[email protected] <mailto:[email protected]>> wrote: > > Hello Yuri, > > It may be a syslog problem IMHO. What you can do is to set > "log_stderror = yes" in your cfg - this will make opensips to > write to console instead of syslog. If you see the logs, it means > there is no problem with opensips, but rather with syslog. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > > On 11/11/2013 01:37 AM, Yuri Ritvin wrote: >> I have installed Opensips 1.9.1 which works fine, but recently it >> stopped writing into the opensips.log file - just in the middle. >> Enough space, memory, CPU resources. Something triggered this issue. >> I tried to revive logging by restarting rsyslog and opensips >> processes, but it doesn't help. Reboot didn't change this >> phenomenon too. >> Any ideas / hints on this subject ? >> >> Thank you, >> Yuri >> >> >> _______________________________________________ >> Users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
