Hey All<div>Ok so this is not an issue; but some of you may run into this so I'm updating myself. </div><div><br></div><div>imuxsock in rsyslog was rate-limiting my messaging. Basically since the xlogs were too fast to rsyslog, it just stopped reporting them. imuxsock reports this error, but that report goes into the main syslog, and not the directed opensips.log I had configured. So I had no idea it was happening until I started to poke around. </div>
<div><br></div><div>Doh!</div><div>-Brett</div><div><br><div><br><div class="gmail_quote">On Wed, Feb 20, 2013 at 9:05 PM, Brett Nemeroff <span dir="ltr"><<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello List,<div><br></div><div>OpenSIP 1.8.2 v9777<br><div>I'm using avp_db_query to pull a cursor with a few hundred rows. I think loop over the results pulling the field in with this syntax</div>
<div><br></div><div>
$(avp(someval)[$var(i)])</div><div><br></div><div>This works great for 196 rows. Then it just dies. It doesn't process any more rows. No process death that I can see. I do this in a timer route and this is causing future items that also run in the timer route to not run (like additional avp_db_query processes).</div>
<div><br></div><div>Has anyone else seen this?</div></div><div><br></div><div>Thanks,</div><div>Brett</div><div><br></div>
</blockquote></div><br></div></div>