How to run official Stress Testing for the Clearwater-docker deployment

[chunchill]

Symptoms

when running the stress testing tool on the clearwater-docker deployment environment which is installed on a host server, runing into the following failures in the log file.

2018-03-06 11:21:09.365930 1520335269.365930: Call-Id: 1-234@172.18.0.3, receive timeout on message Clearwater registration:1 without label to jump to (ontimeout attribute): aborting call.

All the error messages are the same in the log file.

Impact

I fail to run the stress testing tool on the clearwater-docker deployment environment

Release and environment

Run "sudo docker-compose -f minimal-distributed.yaml up -d" on one server.

Steps to reproduce

1. install the clearwater-docker project with docker-compose
2. build a new stress container node, the "Clearwater_stress_testing' docker container
3. enter into the Clearwater_stress_testing docker container
4. run '/usr/share/clearwater/bin/run_stress <home_domain> 20 10', I just replace the <home_domain> as ' '.
5. see the '/var/log/clearwater-sip-stress/xxx_initial_reg_errors.log'

I have create a new project which contains the stress testing tool based on this repo: clearwater-docker-stress

[BennettAllen1]

Hi,
We use https://github.com/Metaswitch/clearwater-infrastructure/blob/master/debian/clearwater-auto-config-docker.init.d#L51 to help set up our code and this sets the home_domain as “example.com” if you don’t specify one. So I suggest trying command 4 with that.
If that doesn’t work, you can follow the SIP message through the logs in bono and sprout to try and see if the clearwater nodes is receiving the request and how far it gets through them before timing out.
Let us know how it goes,
Ben