I further looked into the homestead and see following errors reported in 
homestead_current.txt, any idea what is missing in this case? I don’t have hss 
deployed, why does hss is being called by dnscachedresolver?

28-02-2018 05:28:19.832 UTC [7efd8a7f4700] Warning dnscachedresolver.cpp:836: 
Failed to retrieve record for hss.example.com: Domain name not found
28-02-2018 05:28:19.832 UTC [7efd8a7f4700] Error diameterstack.cpp:853: No 
Diameter peers have been found
28-02-2018 05:28:47.203 UTC [7efe78c04700] Status alarm.cpp:244: Reraising all 
alarms with a known state
28-02-2018 05:28:47.203 UTC [7efe78c04700] Status alarm.cpp:37: homestead 
issued 1502.3 alarm
28-02-2018 05:29:17.203 UTC [7efe78c04700] Status alarm.cpp:244: Reraising all 
alarms with a known state
28-02-2018 05:29:17.203 UTC [7efe78c04700] Status alarm.cpp:37: homestead 
issued 1502.3 alarm
28-02-2018 05:29:47.203 UTC [7efe78c04700] Status alarm.cpp:244: Reraising all 
alarms with a known state
28-02-2018 05:29:47.203 UTC [7efe78c04700] Status alarm.cpp:37: homestead 
issued 1502.3 alarm
28-02-2018 05:30:17.203 UTC [7efe78c04700] Status alarm.cpp:244: Reraising all 
alarms with a known state
28-02-2018 05:30:17.203 UTC [7efe78c04700] Status alarm.cpp:37: homestead 
issued 1502.3 alarm
28-02-2018 05:30:36.754 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:36.755 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:36.812 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:36.813 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:37.628 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:37.629 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:37.656 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:37.657 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:38.325 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:38.326 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:38.379 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:38.379 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:38.981 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:38.982 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:39.027 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:39.028 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:39.803 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:39.803 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:39.850 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:39.851 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:40.625 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:40.626 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:40.671 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:40.673 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:41.354 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:41.355 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:41.401 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:41.402 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:42.076 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:42.077 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:43.077 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:43.078 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:43.593 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:43.593 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:44.593 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:44.594 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.166 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.167 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.209 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.210 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.882 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.883 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.920 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:45.921 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:47.035 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:47.036 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
28-02-2018 05:30:47.110 UTC [7efdd57fa700] Error diameterstack.cpp:268: Routing 
error: 'No remaining suitable candidate to route the message to' for message 
with Command-Code 300, Destination-Host hss.example.com and Destination-Realm 
example.com
:


From: Muhammad Shaikh (Salman)
Sent: Tuesday, February 27, 2018 5:45 PM
To: clearwater@lists.projectclearwater.org
Subject: [Project Clearwater] Live Test Errors


I am running clearwater live test and see following errors, it looks like Basic 
call is failing, any idean why?


Basic Call - Mainline (TCP) - (6505550002, 6505550005) ESC[37;41mFailedESC[37;0m
Exception in quaff_cleanup_blk:
- Expected 401|200, got 480 (call ID 6010ee4ef4aad7c14b1d7ee4a430f5d9)
ESC[37;41mFailedESC[37;0m
  RuntimeError thrown:
   - Expected 401|200, got 480 (call ID 6010ee4ef4aad7c14b1d7ee4a430f5d9)
     - /home/muhammad_shaikh/clearwater-live-test/quaff/lib/call.rb:223:in 
`recv_response'
     - /home/muhammad_shaikh/clearwater-live-test/quaff/lib/endpoint.rb:175:in 
`register'
     - /home/muhammad_shaikh/clearwater-live-test/lib/tests/basic-call.rb:25:in 
`block (2 levels) in <top (required)>'
     - /home/muhammad_shaikh/clearwater-live-test/lib/test-definition.rb:258:in 
`run'
     - /home/muhammad_shaikh/clearwater-live-test/lib/test-definition.rb:126:in 
`block (2 levels) in run_all'
     - /home/muhammad_shaikh/clearwater-live-test/lib/test-definition.rb:112:in 
`collect'
     - /home/muhammad_shaikh/clearwater-live-test/lib/test-definition.rb:112:in 
`block in run_all'
     - /home/muhammad_shaikh/clearwater-live-test/lib/test-definition.rb:111:in 
`each'
     - /home/muhammad_shaikh/clearwater-live-test/lib/test-definition.rb:111:in 
`run_all'
     - /home/muhammad_shaikh/clearwater-live-test/lib/live-test.rb:23:in 
`run_tests'
     - /home/muhammad_shaikh/clearwater-live-test/Rakefile:18:in `block in <top 
(required)>'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/task.rb:240:in
 `block in execute'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/task.rb:235:in
 `each'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/task.rb:235:in
 `execute'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/task.rb:179:in
 `block in invoke_with_call_chain'
     - /usr/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/task.rb:172:in
 `invoke_with_call_chain'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/task.rb:165:in
 `invoke'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:150:in
 `invoke_task'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:106:in
 `block (2 levels) in top_level'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:106:in
 `each'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:106:in
 `block in top_level'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:115:in
 `run_with_threads'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:100:in
 `top_level'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:78:in
 `block in run'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:176:in
 `standard_exception_handling'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/lib/rake/application.rb:75:in
 `run'
     - 
/home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/gems/rake-10.4.2/bin/rake:33:in 
`<top (required)>'
     - /home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/bin/rake:23:in `load'
     - /home/muhammad_shaikh/.rvm/gems/ruby-1.9.3-p551/bin/rake:23:in `<main>'
Basic Call - SDP (TCP) - (6505550005, 6505550007) ESC[37;41mFailedESC[37;0m
Exception in quaff_cleanup_blk:
_______________________________________________
Clearwater mailing list
Clearwater@lists.projectclearwater.org
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to