jesperbagge commented on issue #505: URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1606947653
Just wanted to chip in with what I came out with after a bit of a rabbit chase and how I got things to not repeatledy restart. On version 0.4.0 (but some of the errrors are probably there in 0.3.0 as well) I found out that `entrypoint.sh` checks if the ENV variable `SPRING_CONFIGURATION_FILE` is configured. If it is, it tries to start supervisord with a reference to this config. However, the `docker/supervisord-configuration-file.conf` is [configured to look for the config file](https://github.com/apache/pulsar-manager/blob/22c8587e641ca524f4edda9ba8444aa5ff494da2/docker/supervisord-configuration-file.conf#L32) in another ENV variable. Namely `ENV_SPRING_CONFIGURATION_FILE` :( So both those ENV:s has to point to the same config file. Fixing that, the backend still restarts since the [helm chart for the pulsar manager deployment](https://github.com/apache/pulsar-helm-chart/blob/b3c19fd7fc7067e67940244777dd4241c8295dd4/charts/pulsar/templates/pulsar-manager-deployment.yaml#L93) creates an ENV named `PULSAR_MANAGER_OPTS` that references itself. Also found by @kocaki [here](https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582190167). So that ENV also has to be fixed. My final version of the values.yaml file looks like this: ``` 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" ``` With those three ENV:s configured I managed to get the backend into a running state but still had to manually create a user as described by @malaskowski [here](https://github.com/apache/pulsar-manager/issues/505#issuecomment-1583010641). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
