On Sat, Jun 14, 2025 at 3:09 AM Piotr P. Karwasz <pi...@mailing.copernik.eu> wrote: > > Hi Gary, > > On 14.06.2025 03:22, Gary Gregory wrote: > > Running: > > > > mvn clean verify -Pdocker > > > > I.get: > > > > [INFO] DOCKER> Pulling from library/elasticsearch > > [INFO] DOCKER> Digest: > > sha256:2cc40b15dff85281ac804e7ff27cbc07b31fdd542e94ea7a2bdb6470e3b6bb68 > > [INFO] DOCKER> Status: Downloaded newer image for elasticsearch:8.17.3 > > [INFO] DOCKER> Pulled elasticsearch:8.17.3 in 29 seconds > > [INFO] DOCKER> Pulling from library/logstash > > [INFO] DOCKER> Digest: > > sha256:01feca1dd93ae1c7b0d16d6a7ec08070d13a2e9af16cba88ea916600af8ea8b8 > > [INFO] DOCKER> Status: Downloaded newer image for logstash:8.17.3 > > [INFO] DOCKER> Pulled logstash:8.17.3 in 27 seconds > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Start container > > e514938157d8 > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Network mode: > > log4j-layout-template-json-network > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Waiting for > > ports [9200] directly on container with IP (172.19.0.2). > > [ERROR] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Timeout after > > 60736 ms while waiting on tcp port '[/172.19.0.2:9200]' > > [ERROR] DOCKER> Error occurred during container startup, shutting down... > > [INFO] DOCKER> [elasticsearch:8.17.3] "elasticsearch": Stop and > > removed container e514938157d8 after 0 ms > > [ERROR] DOCKER> I/O Error [[elasticsearch:8.17.3] "elasticsearch": > > Timeout after 60736 ms while waiting on tcp port '[/172.19.0.2:9200]'] > > According to plugin documentation[1], you can print the logs from the > container to the console by adding: > > -Ddocker.showLogs=true > > (perhaps -Ddocker.showLogs works too). > > I hope this helps you debug what is going on during the ElasticSearch > startup.
It appears that port 9200 is published in Docker, but it doesn't seem to be visible outside of Docker, maybe. See https://gist.github.com/garydgregory/a83914942faa2d904bd16966559d07bc Does that ring a bell? Ty, Gary > > Note that unlike the `log4j-mongodb` tests, the integration tests in > `log4j-layout-template-json` are not essential for the main capability > of the module. They only verify that the ECS template we distribute is > compatible with the newest version of ElasticSearch. > > The ITs for ElasticSearch succeeded in the Ubuntu CI build and on my > Debian 12. > > Piotr > > [1] https://dmp.fabric8.io/#start-configuration
