https://pulsar.apache.org/ logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
a
@Yang Yang Maybe you know?
What does the log show?
e
@Asaf Mesika all pods and services are running
it's just proxy service that is simply not running, I have tried to run it over NodePort (but it's should not be needed according to the documentation, since proxy is an internal service)
however
NodePort did not work
I can reach the revers proxy but getting some stupid glassfish server error ...
a
Like any pod that is not starting, something should reveal in the logs right?
e
all pods are running, I can access the frontend
proxy is pending mode since it cannot get external IP, which is not needed according to the documentation, at least I have not found
a
Sorry what frontend exactly are you reffering to?
e
anything in the documentation of what needs to be specified in the values
a
Proxy == Pulsar Proxy right?
e
manager
pulsar-manager
a
Oh.
So Pulsar Manager is the one not starting?
e
pulsar manager runs but I cannot log in
a
You can not access it’s login screen you mean?
ahhhhh
You can’t access 
pulsar-manager/login
from the browser
You installed it via helm?
or manually?
e
I can - but cannot log in
installed via helm
a
@Yang Yang would probably know.
This repo is unmaintained. I just reminded the community again to mark it.
Unmaintained == nobody stepped up to maintain it
y
1. pulsar proxy is not pulsar-manager. 2. search csrf in slack or mailing list
e
@Yu Wei Sung I know that proxy is not manager, so the default username and password does not work for helm installed pulsar?
2023-10-24T170103,679+0400 [main-EventThread] ERROR org.apache.curator.framework.imps.EnsembleTracker - Invalid config event received: {server.2=10.0.55.19528883888:participant, server.1=0.0.0.028883888:participant, server.3=10.0.55.19628883888:participant, version=0}
I have tried to install now on baremetal
but initialization is returning this error
how should I solve it?
y
this thread is confusing to me. what problem do you try to resolve?
e
@Yu Wei Sung why ? I am trying hard to somehow deploy Pulsar
I have tried over helm on K8S it did not work
now I am trying to deploy on bare metal
and getting this error when ran the initialization script 2023-10-24T170103,679+0400 [main-EventThread] ERROR org.apache.curator.framework.imps.EnsembleTracker - Invalid config event received: {server.2=10.0.55.19528883888:participant, server.1=0.0.0.028883888:participant, server.3=10.0.55.19628883888:participant, version=0}
so
I am following the installation documentation but clearly it is not working ...
y
You are facing errors in different stage. your original question is pulsar-manager cannot login. This means you have everything running. But installing in baremetal, you face different issue on zk (you don’t have anything “running”).
Open in Slack
PreviousNext
Powered by