|
I'm reopening this ticket because the _StepdownThread.logger is a child of the fixture logger, which doesn't include a timestamp in its log messages because one is expected to be present from the MongoDB server. yves.duhem, feel free to file a more generic SERVER ticket about having the loggers used by resmoke.py rather than the MongoDB processes have separate prefixes and also include timestamps in their messages. I just want to track that the goal of this ticket has yet to actually be achieved so we don't try and backport it right now.
[ContinuousStepdown:job4] Stepdown Thread threw exception
|
Traceback (most recent call last):
|
File "/data/mci/320ed3830c9bfc5cfe1cd94a28960edb/src/buildscripts/resmokelib/testing/hooks/stepdown.py", line 188, in run
|
self._step_down_all()
|
File "/data/mci/320ed3830c9bfc5cfe1cd94a28960edb/src/buildscripts/resmokelib/testing/hooks/stepdown.py", line 257, in _step_down_all
|
self._step_down(rs_fixture)
|
File "/data/mci/320ed3830c9bfc5cfe1cd94a28960edb/src/buildscripts/resmokelib/testing/hooks/stepdown.py", line 355, in _step_down
|
primary.await_ready()
|
File "/data/mci/320ed3830c9bfc5cfe1cd94a28960edb/src/buildscripts/resmokelib/testing/fixtures/standalone.py", line 102, in await_ready
|
self.port, MongoDFixture.AWAIT_READY_TIMEOUT_SECS))
|
ServerFailure: Failed to connect to mongod on port 21001 after 300 seconds
|
https://logkeeper.mongodb.org/lobster/build/615bbff2964c989bd71e2670ae8d7f0d/test/5b7c2939c2ab6832aa05449f#bookmarks=0%2C20381%2C20382%2C20383%2C20384%2C20385%2C20386%2C20387%2C20388%2C20389%2C20390%2C20391%2C20577
|