I opened an issue for it: https://github.com/apache/pulsar/issues/23717
It seems to crash when loading the native SSL library. Thanks, Yunze On Thu, Dec 12, 2024 at 11:21 AM Yunze Xu <x...@apache.org> wrote: > > Hi all, > > When I started a container for Python client tests locally, I found > the cluster failed to start. > > Reproduce steps: > > ``` > git clone https://github.com/apache/pulsar-client-python.git > cd pulsar-client-python > ./build-support/pulsar-test-service-start.sh > ``` > > The script was blocked at: > > ``` > until curl http://localhost:8080/metrics > /dev/null 2>&1 ; do sleep 1; done > ``` > > When I went inside the container, I found the 8080 port was never > listening. The logs can be checked under the `/pulsar/logs` directory, > it stopped at: > > ``` > 2024-12-12T02:49:54,604+0000 [main] INFO > org.apache.pulsar.broker.service.BrokerService - Started Pulsar Broker > service > ``` > > When I changed the image version back to 4.0.0, it succeeded and the logs > were: > > ``` > 2024-12-12T03:12:07,452+0000 [main] INFO > org.apache.pulsar.broker.service.BrokerService - Started Pulsar Broker > service on /0.0.0.0:6650, TLS: (none), listener: (none) > 2024-12-12T03:12:07,806+0000 [main] INFO > org.apache.pulsar.broker.service.BrokerService - Started Pulsar Broker > service on /0.0.0.0:6651, TLS: OPENSSL, listener: (none) > ``` > > There might be a regression introduced in 4.0.1. > > Thanks, > Yunze