Hello Guys,<br><br>&nbsp;&nbsp;&nbsp; This issue has now been fixed, it was due to a difference of timezones from our main cluster, and the new server added to the cluster, thus causing it to &quot;expire&quot; usrloc locations.&nbsp; Issue is resolved and lesson of the day is -- timezones do matter :).
<br><br>Thank you everyone.<br><br><div><span class="gmail_quote">On 10/30/07, <b class="gmail_sendername">Brandon Armstead</b> &lt;<a href="mailto:brandon.armstead@gmail.com">brandon.armstead@gmail.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello Guys,<br><br>&nbsp;&nbsp;&nbsp; I&#39;m clustering subscribers at the database level, however it seems this one specific server I added into cluster that uses usrloc, is removing location entries, completely randomly?&nbsp; I&#39;ve turned debug=9, but all I can see is... a bunch of: &quot;core:db_free_rows: freeing 0 rows&quot; over and over, this is with revision 2602 and latest trunk from openser.&nbsp; Which is thus on a usrloc mode of (3) causing essentially inbound calls to stop working.&nbsp; Any ideas anyone?&nbsp; Anyone with similiar issue?&nbsp; Every other server is running just fine, just only when this SINGLE server connects / runs to the rest of the cluster (MySQL) -- it starts dropping openser&#39;s locations.
<br><br>Any help appreciated, thanks!<br><br><br>P.S. Also tried with libmysqlclient libs from 5.2.0-beta and 5.0 stable.<br><br><br clear="all"><br>-- <br><span class="sg">Brandon Armstead
</span></blockquote></div><br><br clear="all"><br>-- <br>Brandon Armstead