This message was deleted.
# general
s
This message was deleted.
a
Hi Timo, if I remember correctly, Pulsar manager requires you to create a superuser first as described here. Alternatively, if you can wait a little more, streamvisor.com might be right up your alley 😉
👍 2
j
Hi! I can reproduce the issue. pulsar-manager doesn't boot because of the following issue: https://github.com/apache/pulsar-manager/issues/505 There is a workaround here: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1606947653 I submitted a PR to fix the getting started guide. The workaround is as follows: 1. Make sure the
values-minikube.yaml
file contains the following lines before installing the helm chart:
Copy code
pulsar_manager:
  configData:
    ENV_SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
    SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
    PULSAR_MANAGER_OPTS: " -Dlog4j2.formatMsgNoLookups=true"
2. create the `pulsar`user account:
Copy code
kubectl exec -it YOUR_PULSAR_MANAGER_POD_NAME -n pulsar -- /bin/bash
CSRF_TOKEN=$(curl <http://localhost:7750/pulsar-manager/csrf-token>)
curl \
    -H "X-XSRF-TOKEN: $CSRF_TOKEN" \
    -H "Cookie: XSRF-TOKEN=$CSRF_TOKEN;" \
    -H 'Content-Type: application/json' \
    -X PUT <http://localhost:7750/pulsar-manager/users/superuser> \
    -d '{"name": "pulsar", "password": "pulsar", "description": "test", "email": "<mailto:username@test.org|username@test.org>"}'
Hope this helps. Please let me know if it worked for you
t
Hi @Julien Jakubowski. Thanks for confirming the problem and your help. I followed your steps but did not manage to log into the pulsar manager. Here is what I did: • Delete the minikube cluster. Cloned the repo as described in the guide. • Edit the
/examples/values-minikube.yaml
file with the values you provided. • Continue with the guide until step four. Ran the code to create the pulsar user account you provided. • Run
minikube service -n pulsar pulsar-mini-pulsar-manager
to open pulsar manager UI in the brower. On the log in screen, I still can not log in. The browser console showes the following error:
POST <http://127.0.0.1:64477/pulsar-manager/login> 404 (Not Found)
Any idea why it's not working for me?
This is what my /`examples/values-minikube.yaml` file looks like:
Copy code
## deployed withh emptyDir
volumes:
  persistence: false

# disabled AntiAffinity
affinity:
  anti_affinity: false

# disable auto recovery
components:
  autorecovery: false
  pulsar_manager:
    configData:
      ENV_SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
      SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
      PULSAR_MANAGER_OPTS: " -Dlog4j2.formatMsgNoLookups=true"

zookeeper:
  replicaCount: 1

bookkeeper:
  replicaCount: 1

broker:
  replicaCount: 1
  configData:
    ## Enable `autoSkipNonRecoverableData` since bookkeeper is running
    ## without persistence
    autoSkipNonRecoverableData: "true"
    # storage settings
    managedLedgerDefaultEnsembleSize: "1"
    managedLedgerDefaultWriteQuorum: "1"
    managedLedgerDefaultAckQuorum: "1"

proxy:
  replicaCount: 1
j
Thank you for providing those details. Looks like the YML file contains an indentation issue. Try to: 1. Move the pulsar_manager section to the end of the file 2. Ensure there is no space at the beginning of the
pulsar_manager
line 3. Exactly 2 spaces at the beginning of the
configData
line 4. Exactly 4 spaces at the beginning of the 3 other lines
Hi @Timo! Could you let me know if this problem has been solved? I'd love to help if you need to.
t
Hey @Julien Jakubowski. Unfortunately, I did not managed to get it working. Uninstalled minikube and docker, went through the getting started guide again, adding the values to the `values-minikube.yaml`and proceeding as described in the guide. I still got the same error when trying to log into the Managment UI. How could I troubleshoot this issue? Could be related to the fact that I run this on an M1 mac?
j
That works perfectly fine on my M1 mac. Could you please share your YML file?
On M1 Macs, I would recommend: • Allocating as much RAM as you can to Docker • Enabling Rosetta
👍 1