Hello Guys,<br><br> 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 "expire" usrloc locations. 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> <<a href="mailto:brandon.armstead@gmail.com">brandon.armstead@gmail.com</a>> 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> I'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? I've turned debug=9, but all I can see is... a bunch of: "core:db_free_rows: freeing 0 rows" over and over, this is with revision 2602 and latest trunk from openser. Which is thus on a usrloc mode of (3) causing essentially inbound calls to stop working. Any ideas anyone? Anyone with similiar issue? 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'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