Hello Guys,
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.
Any help appreciated, thanks!
P.S. Also tried with libmysqlclient libs from 5.2.0-beta and 5.0 stable.
Hello Guys,
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 :).
Thank you everyone.
On 10/30/07, Brandon Armstead brandon.armstead@gmail.com wrote:
Hello Guys,
I'm clustering subscribers at the database level, however it seemsthis 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.
Any help appreciated, thanks!
P.S. Also tried with libmysqlclient libs from 5.2.0-beta and 5.0 stable.
-- Brandon Armstead
Brandon Armstead wrote:
Hello Guys,
This issue has now been fixed, it was due to a difference oftimezones 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 :).
The same happened to me some time ago and it was rather difficult to debug. In our case, the timezones were fine but one clock was running several minutes behind. This had the effect that some phones got unregistered for half a minute or so.
It turned out that our ubuntu installations did only do an NTP sync at boot time. So, in addition to "timezones do matter" one should always setup an NTP daemon on all proxies in a cluster.
/Christian
Thank you everyone.
On 10/30/07, *Brandon Armstead* <brandon.armstead@gmail.com mailto:brandon.armstead@gmail.com> wrote:
Hello Guys, 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. Any help appreciated, thanks! P.S. Also tried with libmysqlclient libs from 5.2.0-beta and 5.0 stable. -- Brandon Armstead-- Brandon Armstead
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
-
Brandon Armstead -
Christian Schlatter