I think that the sip-stress scripts actually register for an hour and don't un-register. This means that if you run the scripts and then try to quiesce bono, it will wait until at least an hour after the start of the stress run before the quiesce will finish.
If all you're doing is running stress (i.e. you're not worried about the impact to service once the stress run is done) then I'd suggest you stop, rather than quiesce, bono so that you don't have to wait so long. Thanks, Seb. -----Original Message----- From: Faustinoni Fabrizio [mailto:[email protected]] Sent: 27 January 2017 13:16 To: Sebastian Rex Cc: [email protected] Subject: Re: Unable to restart bono Yes you are right, I waited only a couple of minutes. A question: If I run the sip-stress-test, it will register 15000 users. For all active user there will be a connection in bono nodes right? When I stop the stress service (sudo clearwater-sip-stress stop), this connection will be stopped immediately or I have to wait as you said 10/20 minutes? However my clearwater version is: Version: 1.0-170113.135901 thanks > On Jan 27, 2017, at 1:47 PM, Sebastian Rex <[email protected]> > wrote: > > HI, > > Quiescing Bono will take a long time to finish, as it must wait for all > active registrations to timeout. So if you have a re-registration time of 10 > minutes, it can take up to 10 minutes (20 if using UDP) for the bono quiesce > command to complete. So I suspect that you didn't wait long enough. > If you're not worried about preserving service when restarting Bono, you can > just stop it with: > > sudo service bono stop > > although this will not preserve existing REGISTERs. > > As for the alarm question: that alarm is benign. Any alarm which ends with a > ".1" means that the alarm is cleared and there's no issue. > > To find out the version you have installed, you can run > > dpkg -s clearwater-infrastructure > > which will include "Version: xxx" in the output. > > Regards, > > Seb. > > -----Original Message----- > From: Clearwater [mailto:[email protected]] On > Behalf Of Faustinoni Fabrizio > Sent: 27 January 2017 09:59 > To: [email protected] > Subject: [Project Clearwater] Unable to restart bono > > Hi guys, > > I’ve the following deployment: 5 bono, 5 sprout, 4 homestead, 4 homer, 1 ellis > > If I try to restart the bono node: > sudo service clearwater-infrastructure restart sudo service bono quiesce > > the command is stuck after the output: * Quiescing Bono SIP Edge Proxy bono > > In the log file I see: > Quiesce signal received > 27-01-2017 09:50:49.759 UTC Status stack.cpp:155: Setting quiescing = PJ_TRUE > 27-01-2017 09:50:49.766 UTC Status stack.cpp:186: Quiescing state changed > 27-01-2017 09:50:49.767 UTC Status quiescing_manager.cpp:164: The Quiescing > Manager received input QUIESCE (0) when in state ACTIVE (0) > 27-01-2017 09:50:49.767 UTC Status quiescing_manager.cpp:290: Close untrusted > listening port > 27-01-2017 09:50:49.767 UTC Status stack.cpp:398: Destroyed TCP transport for > port 5060 > 27-01-2017 09:50:49.767 UTC Status quiescing_manager.cpp:298: Quiesce > FlowTable > > (after that I restart the node to be sure that the bono node is restarted > successfully) > > Have you any Idea? > > Also in the log file I see a lot of : > UTC Status alarm.cpp:62: sprout issued 1005.1 alarm > > What does this log means? > > My clearwater version is the last one. > Last question: Where can I find the exact clearwater version number in my > deployment? (I’ve installed it manually with apt-get install) > > thanks > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
