Pulsar Manager UI (created by a helm release) has lost all configuration

[oceanminded]

I started getting incorrect username and password for an account that previously worked. When I look into the pulsar-manager pod logs, I see that the pulsar manager service is starting up without any of the values used during creation:

2024-06-11 18:00:31.740 UTC [51] LOG:  database system was interrupted; last known up at 2024-06-11 17:58:50 UTC
2024-06-11 18:00:31.765 UTC [51] LOG:  database system was not properly shut down; automatic recovery in progress
2024-06-11 18:00:31.770 UTC [51] LOG:  redo starts at 0/16242C0
2024-06-11 18:00:31.771 UTC [51] LOG:  invalid record length at 0/16243A8: wanted 24, got 0
2024-06-11 18:00:31.771 UTC [51] LOG:  redo done at 0/1624370
2024-06-11 18:00:31.814 UTC [50] LOG:  database system is ready to accept connections
 done
server started
2024-06-11 18:00:31.966 UTC [59] ERROR:  database "pulsar" already exists
2024-06-11 18:00:31.966 UTC [59] STATEMENT:  CREATE DATABASE pulsar;
createdb: error: database creation failed: ERROR:  database "pulsar" already exists
ALTER ROLE
2024-06-11 18:00:32.063 UTC [68] ERROR:  database "pulsar_manager" already exists
2024-06-11 18:00:32.063 UTC [68] STATEMENT:  CREATE DATABASE pulsar_manager OWNER pulsar;
psql:/pulsar-manager/init_db.sql:16: ERROR:  database "pulsar_manager" already exists
GRANT
You are now connected to database "pulsar_manager" as user "pulsar".
psql:/pulsar-manager/init_db.sql:27: NOTICE:  relation "environments" already exists, skipping
CREATE TABLE
psql:/pulsar-manager/init_db.sql:48: NOTICE:  relation "topics_stats" already exists, skipping
CREATE TABLE
psql:/pulsar-manager/init_db.sql:64: NOTICE:  relation "publishers_stats" already exists, skipping
CREATE TABLE
CREATE TABLE
psql:/pulsar-manager/init_db.sql:85: NOTICE:  relation "replications_stats" already exists, skipping
psql:/pulsar-manager/init_db.sql:103: NOTICE:  relation "subscriptions_stats" already exists, skipping
CREATE TABLE
psql:/pulsar-manager/init_db.sql:120: NOTICE:  relation "consumers_stats" already exists, skipping
CREATE TABLE
psql:/pulsar-manager/init_db.sql:128: NOTICE:  relation "tokens" already exists, skipping
CREATE TABLE
CREATE TABLE
psql:/pulsar-manager/init_db.sql:142: NOTICE:  relation "users" already exists, skipping
psql:/pulsar-manager/init_db.sql:151: NOTICE:  relation "tenants" already exists, skipping
CREATE TABLE
CREATE TABLE
psql:/pulsar-manager/init_db.sql:158: NOTICE:  relation "namespaces" already exists, skipping
Starting Pulsar Manager Front end
Starting Pulsar Manager Back end
Start Pulsar Manager by specifying a configuration file.
2024-06-11 18:00:32,388 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-06-11 18:00:32,390 INFO supervisord started with pid 82
2024-06-11 18:00:33,393 INFO spawned: 'pulsar-manager-backend' with pid 83
2024-06-11 18:00:34,957 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

However, the rest of the stack is pulling and pushing messages just fine - so it seems I haven't lost my queues.
User pulsar/pulsar didn't work so I created a new admin user via curl command and then created the environment via UI - inserting the service urls for pulsar-proxy ports 80 and 6650.

After doing so, I can see my queues but had quite the scare.

• Is there a way to look up why the pulsar manager restarted without any config? With the initial helm install, I definitely didn't set up a user or password anywhere but in the settings/init script.
• Should I be worried about what may have caused the Manager to restart without a config? (potential resource issue?)

[lhotari]

What Pulsar Helm chart version are you using? Please upgrade to the latest 3.4.1 to get fixes. Please check the release notes to see if a fixed issue matches your problem. https://github.com/apache/pulsar-helm-chart/releases . Your problem might be fixed in the latest recently released 3.4.1 version. apache/pulsar-helm-chart#485 might be related