If DoSarray doesn't work then try running the configuration checker for an informative break-down of checks. The script's output can be made more detailed by tweaking it as described in the FAQ.
For more in-depth troubleshooting try the following:
- Has DoSarray worked previously on this setup? If not then make sure you've followed our setup instructions and that the target has been started.
- Is the host network configured correctly?
- Is docker running?
Run
service docker status
- Is the image installed?
Run
docker images
. For example, on one of the clusters DoSarray was installed upon docker images disappeared. The cluster is shared, and one cannot always account for what other users get up to. - Is the container network configured correctly?
Run
ifconfig
and look fordocker_bridge
. Make sure you've run thedosarray_configure_networking.sh
script. This script must also be run against physical machines that don't run docker (e.g., running the targets) otherwise they won't be able to send packets back to the DoSarray containers. - Are the containers created & started?
Run
docker ps
- Are the containers interacting over the network with each other?
Try sending packets from inside to outside and vice versa.
For example, use
tcpdump
andping
within a container. See the setup advice on how to run commands in containers.
Finally, look for clues in the DoSarray stdout and stderr logs, and the raw logs.