Manager and worker silence with no activity

[bbros-dev]

We start a web server:

 $ podman run --publish 5000:5000 --rm -ti the-internet

We observe this activity

[2021-06-17 15:37:52] INFO  WEBrick 1.6.0
[2021-06-17 15:37:52] INFO  ruby 2.7.2 (2020-10-01) [x86_64-linux]
[2021-06-17 15:37:52] INFO  WEBrick::HTTPServer#start: pid=1 port=5000

We start a manager:

$ podman run --env RUST_BACKTRACE=full \
                       --network="host" \
                       --rm \
                       -ti gti /usr/local/bin/gti --host http://127.0.0.1:5000 --manager --users 2 --expect-workers 2

We observe no output.

Then in another console we start a worker:

$ podman run --env RUST_BACKTRACE=full \
                       --network="host" \
                       --rm \
                       -ti gti /usr/local/bin/gti --manager-host 127.0.0.1 --worker

We observe no output.

The web server console shows no output.

We kill the Goose master and observe the worker panic that the master has gone away.

We'd expect some output indicating the status of the master and worker.

[jeremyandrews]

If you want verbosity, use -v when you start the Manager and/or the Worker. (Or -g --log-file goose.log to instead write logs to a file.)

If you don’t want a panic capture the error and handle it in your code.

[jeremyandrews]

Note, you can also change the Goose default to be more verbose (so you don't even need to add -v) with set_default.

You can see an example of this in this snippet: https://docs.rs/goose/*/goose/trait.GooseDefaultType.html#another-example