Question posted in
Some documentation to get you started can be found here.

Gemfire throws 502 Gateway error on starting a locator – Apache

I had Apache Geode cluster running and I was connected to it using gfsh client. In order to test something, I stopped the Cache Server using, “stop server –name=xxxxserver” command. The Cache server stopped successfully.

Further, I stopped the locator using the “stop locator –name=xxxxlocator” command. The locator stopped successfully. However, my gfsh client connection was also disconnected.

Now, I am trying to reconnect my gfsh client to the locator, but it always gives me a 502 bad gateway error. I have tried accessing the pulse url, I get the same error:

“502 Bad Gateway: Registered endpoint failed to handle the request.”

What I am missing and how can this be fixed?

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    Right. But, the problem is I am unable to start the locator due to the error I have mentioned. I created another cache instance to verify, but don't see this problem. Stopped/started locator with no issues and able to access the pulse as well.


  2. 0

    If you stopped your locator, it’s expected for gfsh and PULSE to be disconnected as there’s no JMX Manager they can talk to. You should start your locator again and re-connect, then everything should be fine.
    Cheers.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search