Hello Lilin, I'm running latest clearwater after upgrading following manual instructions through to Yojimbo and Another Nine and a Half Weeks releases.
I had to change some ip addresses in /etc/clearwater/config after upgrade. (maybe because of manual upgrade) Initially sprout wasn't talking to homestead and I was seeing 403 Forbidden. What address and port is sprout listening on? Use netstat -anp. Does it match the address that homestead is trying to connect to? sprout.clearwater.demo ? $ sudo netstat -anp |grep :5054 |head tcp 0 0 *10.124.51.133:5054 <http://10.124.51.133:5054>* 0.0.0.0:* LISTEN 5978/sprout $ ps -elf|grep sprout 4 S sprout 5978 1 0 80 0 - 327025 futex_ Mar03 ? 00:10:15 /usr/share/clearwater/bin/sprout --domain openims.test --localhost 10.124.51.133 --sprout-domain 10.124.51.133 --alias 10.124.51.133, --realm openims.test --memstore /etc/clearwater/cluster_settings --hss 10.124.51.133:8888 --chronos localhost:7253 --xdms 10.124.51.133:7888 --sas 0.0.0.0:[email protected] --pjsip-threads 1 --worker-threads 50 --record-routing-model pcscf --authentication -a /var/log/sprout -F /var/log/sprout -L 4 --scscf 5054 --icscf 5052 Not sure if this will help much. Beware I'm just figuring out clearwater!? :-) James. On 6 March 2014 03:13, Lilin Zhang <[email protected]> wrote: > Hello, > > I noticed that there is a new release of clearwater, Yojimbo. So I'm > deploying it by following the updated online wiki page. I started from > clean slate, by creating new VMs. Now I have all the components running: > ellis, bono, sprout, homestead, homer, by checking the monit status. The > corresponding "poll_*" programs also have status OK reported by monit (by > the way, what's the use of poll_* programs? They are new to the Yojimbo > release). > > Then I'm using Blink client to test the deployment. I have got REGISTER > error received at the client side: 403 Forbidden. > > Here are related log traces: (I didn't attach the entire log file, as it > makes the message too long to post to this mailing list.) > > (1) The log of bono, which runs with default log_level (=2), says " > Rejecting request from untrusted source". (doesn't say much, so I go to > check sprout log.) > > (2) The log of sprout, which runs with log_level=5, says: > 06-03-2014 02:25:04.800 Error httpconnection.cpp:394: > http://hs.clearwater.demo:8888/impi/6505550414%40clearwater.demo/av?impu=sip%3A6505550414%40clearwater.demofailed > at server : Timeout was reached (28 0) : retrying. (The problem is > to do with hs, so I go to check homestead log.) > > (3) The log of homestead, which runs with log_level=5, says: > 06-03-2014 02:26:36.887 Status freeDiameter: Unable to resolve address > for peer '' (Temporary failure in name resolution), aborting. (Very > Strange! have Never seen this error before.) > > I double checked the following: > > (1) the DNS server was set up and contacted correctly: the Blink client > runs on the machine who can resolve "bono.clearwater.demo"; the sprout node > can resolve the name "hs.clearwater.demo". (the domain name is > clearwater.demo for my deployment. ) > > (2) all the components are running: ellis, bono, sprout, homestead, homer, > by checking the monit status. The corresponding "poll_*" programs all have > status OK. > > (3) the security groups (and open ports) for each clearwater component > were set the same as what is required in the online wiki page (Clearwater > IP usage). > > What confuses me is that I don't quite understand the error in the > homestead log: Unable to resolve address for peer ''. I'd very much > appreciate if you could give me some insights on where this error comes > from and how to solve it. Thanks! > > Regards, > Lilin > > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/listinfo/clearwater > > -- <http://www.linkedin.com/company/76647?trk=fc_badge> openmindnetworks.com
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
