Closed wolfstudy closed 4 years ago
I encountered the same issue and can reproduce it. Help needed. Thanks.
I can reproduce these symptoms on OSX by starting prometheus before starting pulsar.
I encountered the same issue when running pulsar in docker.
mac Mojave 10.14.6 pulsar 2.4.1
https://pulsar.apache.org/docs/en/standalone-docker/ --> Get Started --> Run pulsar in Docker
I am not able to see this issue as interim people can try and use the docker image and volume mount the data folder, also please check to see /etc/hosts files or any strange entries.
I am not able to see this issue as interim people can try and use the docker image and volume mount the data folder, also please check to see /etc/hosts files or any strange entries.
I reproduced the issue. It happened After I pressed Ctrl+C to stop the program. I tried three times, and the exception happened three times.
To Reproduce
Environment mac Mojave 10.14.6 pulsar 2.4.1 wifi connected
I found this thread as I was having similar exceptions. I received consistent failures while logged into wifi but seemed a bit more stable when hard connected to the network. It would still crash, however, when plugged into the network. Looking through the logs I noticed that the hostname of my mac is being used as a connection for some service in standalone mode (and I assume non-standalone mode). I found my hostname was not in DNS. I added my mac's hostname to /etc/hosts and everything started up fine and is stable.
There is a change #5856 in release 2.5.0. It will use the "localhost" if the hostname is unresolved.
Hi, I still have this issue (macOS Mojave 10.14.6) with apachepulsar/pulsar:2.7.0 (docker 20.10.0, build 7287ab3), I've fixed it in adding my hostname to /etc/hosts.
Describe the bug In the case of a WI-FI connection, when I use
./bin/pulsar standalone
to start pulsar, I get the following error:Then i tried to solve this problem with
./bin/pulsar standalone -a 127.0.0.1
, unfortunately, I still encountered the same error.However, this problem will not occur when you disconnect all connected networks (eg: wifi)
To Reproduce
This problem is not a bug that can be reliably reproduced. Some people will encounter this problem, but some people will not encounter it.
Screenshots
Desktop (please complete the following information):