Oh sorry, I should have been able to differentiate that..<div><br></div><div>I was getting 500 Server Errors in the replies. The errorlog showed memory errors. I haven't seen it in a while. I'll see if I can replicate it. I think I may have posted to the list a while back when it happened.</div>
<div><br></div><div>For what it's worth, I do dialog profiling on all of my calls (profiles with value). I use this to see which accounts have approx how many calls active (love it!). I have a script that basically loops through all of my accounts and uses the fifo to count the calls and prints out a table. </div>
<div><br></div><div>So upon retrieving these counts, sometimes, I got the error.. Like I said, I'll see if I can reproduce it..</div><div><br></div><div>-Brett</div><div><br></div><div><br><div class="gmail_quote">On Wed, May 27, 2009 at 10:35 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">No, this is some XMPRPC specific stuff.<br>
<br>
What kind of errors did you get on FIFO?<br>
<br>
Regards,<br>
Bogdan<br>
<br>
Brett Nemeroff wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Bogdan,<br>
I've had some issues where running fifo commands sometimes returns errors. Simple things like dumping the dialogs. Is this related do you think?<br>
-Brett<br>
<br>
<br></div><div class="im">
On Wed, May 27, 2009 at 8:53 AM, Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>>> wrote:<br>
<br>
Hi,<br>
<br>
In the last years there were several reports about the blocking of the<br>
mi_xmlrpc module - actually this was the reason for having this MI<br>
XMLRPC 2 FIFO proxy right now.<br>
<br>
Thanks to the help of Dan Pascu, we manage to identify the cause :a<br>
design bug in xmlrpc lib - the signal handler used for getting the<br>
SIGCHLD (for the terminated worker processes) contained functions that<br>
may trigger a deadlock between the main code and the handler (for<br>
example because of malloc/free which have an internal lock).<br>
<br>
This bug was fixed in all OpenSIPS versions (available on SVN) and<br>
it is<br>
strongly recommended to upgrade your code.<br>
<br>
<br>
Regards,<br>
Bogdan<br>
<br>
_______________________________________________<br>
Users mailing list<br></div>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><div class="im"><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div>