search

NLnetLabs / rpki-deploy

RPKI deployment related tooling developed for/by NLnet Labs.
https://nlnetlabs.nl/rpki
3 stars 2 forks source link

Container error logs missing on Krill configure failure. #10

Closed ximon18 closed 4 years ago

ximon18 commented 4 years ago

Krill E2E test builds are failing with errors in the NGINX Docker container logs but the error summary is empty:

module.post.null_resource.run_tests[0] (local-exec): configure_krill.sh: Dumping container logs that match error filter (ERR|Bad|Fail|WARN)
module.post.null_resource.run_tests[0] (local-exec): ~/work/krill/rpki-deploy/terraform/krill-e2e-test/lib/docker ~/work/krill/rpki-deploy/terraform/krill-e2e-test/run_on_do
module.post.null_resource.run_tests[0]: Still creating... [1m0s elapsed]
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): Connection pool is full, discarding connection: 157.245.71.226
module.post.null_resource.run_tests[0] (local-exec): ~/work/krill/rpki-deploy/terraform/krill-e2e-test/run_on_do

Where is the NGINX error? It is visible in the full log dump:

nginx               | ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

Maybe the NGINX error wasn't logged yet at the time of the Krill configure failure? Timestamps are missing from the logs (just fixed by commit 4b40a987) so I can't tell if that's the reason...

ximon18 commented 4 years ago

Obsoleted by 1396c5a9202625ba7914126b4f7c1359c1c00434.