I would look at your database replication. It might be that they are switching back and forth and deleting the rows. Why are you replicating as master/master? Also examine the time on both servers and make sure the date and time are in sync.<div>
<br></div><div>Regards,</div><div>Ali Pey</div><div><br><br><div class="gmail_quote">On Mon, Aug 20, 2012 at 2:00 PM, Schneur Rosenberg <span dir="ltr"><<a href="mailto:rosenberg11219@gmail.com" target="_blank">rosenberg11219@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It happened again just out of the nowhere, please can someone please<br>
suggest what can cause it, I'm going crazy already.<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Aug 19, 2012 at 12:48 PM, Schneur Rosenberg<br>
<<a href="mailto:rosenberg11219@gmail.com">rosenberg11219@gmail.com</a>> wrote:<br>
> I'm having a interesting scenario, every once in a while my OpenSIPS<br>
> location table begins losing its contents, I lose like 100 at a time,<br>
> then it might regain some and then loses again another 100 or so.<br>
><br>
> I have 2 servers one active and one standby via Heartbeat, heartbeat<br>
> shuts and turns on opensips when becoming the active node, the MYSQL<br>
> databases are replicated as a MASTER/MASTER replication.<br>
><br>
> First time this happened was when I tested a updated OpenSIPS script,<br>
> so I turned on OpenSIPS on the standby node, I did not close OpenSIPS<br>
> right away and thats why I suspected that the standby node kept on<br>
> erasing lines once they expired and the active node kept on adding<br>
> rows, this was a full fledged OpenSIPS war :-)<br>
><br>
> But this same thing happened last week again for no reason, I did not<br>
> touch the standby server at all, all of the sudden we got calls from<br>
> customers that their phones are acting weird, going online and offline<br>
> all the time, sure enough I saw that the location table was down to<br>
> maybe 20 registrations, I rebooted the master and it did not help, I<br>
> rebooted the slave too and it did not help so I did a<br>
> /etc/init.d/heartbeat stop and the slave fired up and everything went<br>
> back to normal, within a few minutes all registrations were all back<br>
> up.<br>
><br>
> I then ran a apt-get upgrade and one of the applications that were<br>
> updated was mysql server, so I said maybe that will fix the problem, I<br>
> rebooted the master and heartbeat fired up OpenSIPS and everything was<br>
> fine till today.<br>
><br>
> Today I by mistake ran opensipsctl fifo lb_list on the slave<br>
> (standby) server and sure enough it gave me a error because opensips<br>
> was not running, but 30 minutes later I got a call from a customer<br>
> that his lines were down.<br>
><br>
> Could it be that be merely running "opensipsctl fifo lb_list"<br>
> something would of caused this issue? I did not run "ps aux | grep<br>
> opensips" because I right away rebooted the servers, is there anything<br>
> else that could cause such symptoms?<br>
><br>
> thanks<br>
> S. Rosenberg<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><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>
</div></div></blockquote></div><br></div>