You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2023/01/13 10:53:14 UTC
[GitHub] [pulsar-manager] malaskowski opened a new issue, #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
malaskowski opened a new issue, #505:
URL: https://github.com/apache/pulsar-manager/issues/505
Running Pulsar Manager with the default [Pulsar Helm Chart settings](https://github.com/apache/pulsar-helm-chart/blob/pulsar-3.0.0/charts/pulsar/values.yaml#L1051) ends with not working manager instance.
## Steps to reproduce
Run the container using the default:
```bash
docker pull apachepulsar/pulsar-manager:v0.3.0
docker run -it \
-p 9527:9527 -p 7750:7750 \
-e REDIRECT_HOST="http://127.0.0.1" \
-e REDIRECT_PORT="9527" \
-e DRIVER_CLASS_NAME="org.postgresql.Driver" \
-e URL="jdbc:postgresql://127.0.0.1:5432/pulsar_manager" \
-e USERNAME="pulsar" \
-e PASSWORD="pulsar" \
-e LOG_LEVEL="DEBUG" \
apachepulsar/pulsar-manager:v0.3.0
```
## Result
First, the user is asked for the information by the `adduser` command from the https://github.com/apache/pulsar-manager/blob/v0.3.0/docker/entrypoint.sh#L27 (looks like fix for this is pretty easy: `adduser --disabled-password --gecos "" --ingroup pulsar pulsar`). However, later running the `/pulsar-manager/startup.sh` fails with:
```bash
/pulsar-manager/startup.sh: 21: initdb: not found
/pulsar-manager/startup.sh: 22: pg_ctl: not found
createdb: error: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
```
Then in the `/pulsar-manager/pulsar-manager.log` you can see the connection error (as the DB didn't start):
```bash
2023-01-13 10:49:51.463 ERROR 156 --- [pool-2-thread-1] com.zaxxer.hikari.pool.HikariPool : HikariPool-1 - Exception during pool initialization.
org.postgresql.util.PSQLException: Connection to 127.0.0.1:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
```
Finally, the backend never starts properly.
## Expected result
The Pulsar Manager creates an internal DB instance and runs properly.
## Additional details
I'm running the command above on M1 Apple Silicon processor and Docker Desktop for Mac `v4.15.0`.
--
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: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] malaskowski commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "malaskowski (via GitHub)" <gi...@apache.org>.
malaskowski commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1581303784
@kocaki
Try to run pulsar manager with the following `configData`:
```yaml
configData:
SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
# Workaround for https://github.com/apache/pulsar-manager/issues/505
URL: ""
```
This works with `apachepulsar/pulsar-manager:v0.3.0` for me.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] bpereto commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "bpereto (via GitHub)" <gi...@apache.org>.
bpereto commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1542410152
^
> [streamnative/pulsar-manager:v0.3.1-rc2](https://hub.docker.com/layers/streamnative/pulsar-manager/v0.3.1-rc2/images/sha256-2b1f9eaac6300f4a1d5a5e8cfd03a7ed789056fb8db4757f52d056c5199a716e?context=explore)
>
> Since the official release may take some time, I tried to build an image manually, can you try it? @bpereto @Zand3r24 @doug-ba @malaskowski @splio-rbechon
keeps crashing:
```
2023-05-10 15:28:19,418 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-05-10 15:28:19,418 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-05-10 15:28:20,422 INFO spawned: 'pulsar-manager-backend' with pid 1145
```
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582069144
@malaskowski
```
Pulsar Manager config:
pulsar_manager:
component: pulsar-manager
replicaCount: 1
# True includes annotation for statefulset that contains hash of corresponding configmap, which will cause pods to restart on configmap change
restartPodsOnConfigMapChange: false
# nodeSelector:
# cloud.google.com/gke-nodepool: default-pool
annotations: {}
tolerations: []
gracePeriod: 30
resources:
requests:
memory: 250Mi
cpu: 0.1
configData:
SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
REDIRECT_HOST: "http://127.0.0.1"
REDIRECT_PORT: "9527"
DRIVER_CLASS_NAME: org.postgresql.Driver
URL: jdbc:postgresql://127.0.0.1:5432/pulsar_manager
LOG_LEVEL: DEBUG
## If you enabled authentication support
## JWT_TOKEN: <token>
## SECRET_KEY: data:base64,<secret key>
## Pulsar manager service
## templates/pulsar-manager-service.yaml
##
service:
type: LoadBalancer
port: 9527
targetPort: 9527
annotations: {}
## Pulsar manager ingress
## templates/pulsar-manager-ingress.yaml
##
ingress:
enabled: false
annotations: {}
tls:
enabled: false
## Optional. Leave it blank if your Ingress Controller can provide a default certificate.
secretName: ""
hostname: ""
path: "/"
## If set use existing secret with specified name to set pulsar admin credentials.
existingSecretName:
admin:
user: pulsar
password: pulsar
# These are jobs where job ttl configuration is used
# pulsar-helm-chart/charts/pulsar/templates/pulsar-cluster-initialize.yaml
# pulsar-helm-chart/charts/pulsar/templates/bookkeeper-cluster-initialize.yaml
job:
ttl:
enabled: false
secondsAfterFinished: 3600
```
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] doug-ba commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "doug-ba (via GitHub)" <gi...@apache.org>.
doug-ba commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1430648414
@tuteng , sorry to ping you directly, but it looks like you push the container images. Is there any chance of getting a new version of the pulsar-manager with the fix for this pushed?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] enzo-dechaene commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "enzo-dechaene (via GitHub)" <gi...@apache.org>.
enzo-dechaene commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1545772761
still have the back-end crashing in the 4.0.0
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] splio-rbechon commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "splio-rbechon (via GitHub)" <gi...@apache.org>.
splio-rbechon commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582110208
Hello @kocaki
Do you have this in your helm template file that deployed pulsar manager ?
```
- name: PULSAR_MANAGER_OPTS
value: "$(PULSAR_MANAGER_OPTS)
```
On my side, this variable was the root cause of Supervisord issue ... I just removed it to fix my issue
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work [pulsar-manager]
Posted by "jak78 (via GitHub)" <gi...@apache.org>.
jak78 commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1849729682
Hi everyone! The [PR](https://github.com/apache/pulsar-helm-chart/pull/385) is merged. Huge thanks for your investigations!
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1584078857
Hi @malaskowski,
Thanks I will try it. With 0.4.0 I see that the db is being created in the pod but unfortunately the pulsar_manager_backend keeps restarting.
Are you running the db embedded or using an external db and version 0.3.0 or 0.4.0? Because the embedded db will be destroyed once you redeploy the pod right or will it migrate the db to the new pod?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582190167
Hi @splio-rbechon,
It is exixting in the pulsar-manager-deployment.yaml but looks different:
```
- name: PULSAR_MANAGER_OPTS
value: "$(PULSAR_MANAGER_OPTS) -Dlog4j2.formatMsgNoLookups=true"
```
Tried a new deployment without it but it is still stuck on the same. Logs:
```
Starting PostGreSQL Server
Adding group `pulsar' (GID 1000) ...
Done.
Adding user `pulsar' ...
Adding new user `pulsar' (1000) with group `pulsar' ...
Creating home directory `/home/pulsar' ...
Copying files from `/etc/skel' ...
Changing the user information for pulsar
Enter the new value, or press ENTER for the default
Use of uninitialized value $answer in chop at /usr/sbin/adduser line 582.
Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 583.
/pulsar-manager/startup.sh: 21: initdb: not found
/pulsar-manager/startup.sh: 22: pg_ctl: not found
createdb: error: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] Starting Pulsar Manager Front end
Starting Pulsar Manager Back end
Start Pulsar Manager by specifying a configuration file.
2023-06-08 08:59:30,389 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.
2023-06-08 08:59:30,390 INFO supervisord started with pid 64
2023-06-08 08:59:31,393 INFO spawned: 'pulsar-manager-backend' with pid 65
2023-06-08 08:59:32,538 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
```
So with the suggestion of @malaskowski the backend startup problem has been solved but now there is still a db issue.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] bpereto commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "bpereto (via GitHub)" <gi...@apache.org>.
bpereto commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1542412933
@tisonkun I will test [v0.4.0-candidate-2](https://github.com/apache/pulsar-manager/releases/tag/v0.4.0-candidate-2) if you will release a docker image.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1584613458
Hi @enzo-dechaene,
Thanks for the info and help. The problem is that the pulsar-manager-backend keeps restarting and we cannot find out why.
The config looks as following:
```
configData:
REDIRECT_HOST: "http://127.0.0.1"
REDIRECT_PORT: "80"
DRIVER_CLASS_NAME: org.postgresql.Driver
URL: jdbc:postgresql://127.0.0.1:5432/pulsar_manager
LOG_LEVEL: DEBUG
SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
#Workaround for https://github.com/apache/pulsar-manager/issues/505
PASSWORD: pulsar
USERNAME: pulsar
LOG_LEVEL: DEBUG
```
I attached the log of the pulsar manager where you can see that db is being created successfully with 0.4.0 but then it the backend keeps restarting so even if I should create a user I am unable to login.
Our configuration is in Azure AKS. When I check the resources I see there is an internal and external ip assigned and necessary ports are set open automatically. Besides Pulsar Manager also the Proxy pod is restarting with the error it cannot start http server on port 80. No idea if it is related to each other.
If I install version 0.1.0, I can login on the webinterface but receive a lot of errors (500 internal server error). And with 3.0 there is this known issue regarding the db which this topic is about.
Tried also an external PostgreSql db but looks like it is not being used. DB stays empty and no errors in log.
[pulsar_manager_1.txt](https://github.com/apache/pulsar-manager/files/11706843/pulsar_manager_1.txt)
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] tuteng commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "tuteng (via GitHub)" <gi...@apache.org>.
tuteng commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1499870621
[streamnative/pulsar-manager:v0.3.1-rc2](https://hub.docker.com/layers/streamnative/pulsar-manager/v0.3.1-rc2/images/sha256-2b1f9eaac6300f4a1d5a5e8cfd03a7ed789056fb8db4757f52d056c5199a716e?context=explore)
Since the official release may take some time, I tried to build an image manually, can you try it? @bpereto @Zand3r24 @doug-ba @malaskowski @splio-rbechon
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] Aaron-ML commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "Aaron-ML (via GitHub)" <gi...@apache.org>.
Aaron-ML commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1502519317
Hitting this as well, looks like a lot of this stuff is on hold or what?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1580776789
Hi,
I am deploying Pulsar in Kubernetes (Azure) and am facing the same issue. I deploy using Helm. Is there a way to solve this for my deployment? If yes, how?
Thanks in advance!
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] enzo-dechaene commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "enzo-dechaene (via GitHub)" <gi...@apache.org>.
enzo-dechaene commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582563595
It finally started yesterday with pulsar 0.4.0 for me, can you try adding this conf :
``` PASSWORD: pulsar
USERNAME: pulsar
REDIRECT_HOST: your_ingress_url
REDIRECT_PORT: '80'
URL: jdbc:postgresql://127.0.0.1:5432/pulsar_manager
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] tisonkun commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "tisonkun (via GitHub)" <gi...@apache.org>.
tisonkun commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1499871402
@tuteng Out of curiosity, are you working on v0.3.1 release based on current master branch?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] htbmw commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "htbmw (via GitHub)" <gi...@apache.org>.
htbmw commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1616778020
Also stumbled upon the issue with the postgres not starting up in 0.3.0 as well as the restarting backend issue.
Updated my values to specify 0.4.0 and that solved the postgres issue.
Then it took a bit further reading here and after I had changed the
PULSAR_MANAGER_OPTS to remove the self-referenced value, the backend was working.
Then I also discovered here that the pulsar:pulsar credentials is not for the frontend and that you have to generate that yourself using the API.
Finally I can use pulsar-manager after two late nights :-)
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582623336
Hi @enzo-dechaene,
Unfortunately also failing with this setup. Logs show me that the pular_manager_backend keeps restarting. Can you share your pulsar manager config so I can compare?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] Zand3r24 commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "Zand3r24 (via GitHub)" <gi...@apache.org>.
Zand3r24 commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1499753391
Just wanted to say I'm also hitting this, and waiting for a new image to be built with the fix.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] splio-rbechon commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by GitBox <gi...@apache.org>.
splio-rbechon commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1385176693
Hello @malaskowski
It seems that there is an issue in startup script. Database can't be created because binary path is not in the environment variable PATH.
Another related issue has been created [here](https://github.com/apache/pulsar-manager/issues/465)
You can find a commit that will provide you a way to fix this [here](https://github.com/apache/pulsar-manager/pull/478/commits/25aab24fc92fc7ed92eca101c15d1a65656178b6)
Unfortunately, you docker will fail each time during init so you will have to fix this manually until the patch is deployed
Have a nice day
Robin
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work [pulsar-manager]
Posted by "rankumar1955 (via GitHub)" <gi...@apache.org>.
rankumar1955 commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1823764401
Hi enzo-dechaene,
can you please post here the url of the pulsar/pulsar helm repository?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] enzo-dechaene commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "enzo-dechaene (via GitHub)" <gi...@apache.org>.
enzo-dechaene commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1693371010
I think the chart deployment on the pulsar/pulsar repository needs to be updated as well ?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] tuteng commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "tuteng (via GitHub)" <gi...@apache.org>.
tuteng commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1430788012
@urfreespace Can you help take a look at it? thanks
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] bpereto commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "bpereto (via GitHub)" <gi...@apache.org>.
bpereto commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1466438205
@urfreespace @splio-rbechon @nodece
can someone of you release (or poke the maintainer) to release a new release with commit https://github.com/apache/pulsar-manager/pull/478/commits/25aab24fc92fc7ed92eca101c15d1a65656178b6 included?
thank you!
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work [pulsar-manager]
Posted by "lvs071103 (via GitHub)" <gi...@apache.org>.
lvs071103 commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-2058773098
new create Dockerfile file
```
FROM apachepulsar/pulsar-manager:latest
RUN useradd -ms /bin/bash pulsar
COPY entrypoint.sh /pulsar-manager/
ENTRYPOINT [ "/pulsar-manager/entrypoint.sh" ]
```
exegesis addgroup and adduser in the file of entrypoint.sh:
```bash
...
# addgroup pulsar
# adduser --disabled-password --ingroup -ms /bin/sh pulsar pulsar
...
```
rebuild image and run it:
```bash
$ docker build -t apachepulsar/pulsar-manager:20240416 .
$ docker run -dit \
-p 9527:9527 -p 7750:7750 \
-v $PWD/config/application.properties:/pulsar-manager/pulsar-manager/application.properties \
-v $PWD/secret/admin.key:/pulsar-manager/private.key \
-e SPRING_CONFIGURATION_FILE=/pulsar-manager/pulsar-manager/application.properties \
-e URL='jdbc:postgresql://127.0.0.1:5432/pulsar_manager' \
-e USERNAME=pulsar \
-e PASSWORD=pulsar \
-e LOG_LEVEL=DEBUG \
-v $PWD/data:/data \
apachepulsar/pulsar-manager:20240416 /bin/sh
```
> @tuteng I was still prompted on `docker run`:
>
> ```
> Enter the new value, or press ENTER for the default
> Full Name []:
> Room Number []:
> Work Phone []:
> Home Phone []:
> Other []:
> Is the information correct? [Y/n] Y
> ```
>
> But manager started correctly and works, thank you.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] jak78 commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "jak78 (via GitHub)" <gi...@apache.org>.
jak78 commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1690473837
Hi! I reproduced the problem and @jesperbagge suggestion works also fine for me. I just submitted a PR to fix the boot issue.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] malaskowski commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "malaskowski (via GitHub)" <gi...@apache.org>.
malaskowski commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1583010641
@kocaki
The default `pulsar`/`pulsar` credentials does not work in my project's Pulsar setup.
I followed the [instructions for creating user via the backend API](https://github.com/apache/pulsar-manager#access-pulsar-manager):
```bash
CSRF_TOKEN=$(kubectl exec --namespace pulsar -it $manager_pod -- curl http://localhost:7750/pulsar-manager/csrf-token)
kubectl exec --namespace pulsar -it $manager_pod -- 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": "admin", "password": "mypassword", "description": "console admin", "email": "admin@example.com"}'
```
This is also fairly easy to automate.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] bpereto commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "bpereto (via GitHub)" <gi...@apache.org>.
bpereto commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1545797121
I builded the docker image with FROM openjdk:17-slim-bullseye and needed an extra java opts: JAVA_OPTS: "--add-opens java.base/java.lang=ALL-UNNAMED"
with this setup it works fine.
https://github.com/apache/pulsar-manager/issues/509#issuecomment-1544740033
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] malaskowski commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "malaskowski (via GitHub)" <gi...@apache.org>.
malaskowski commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1502798303
@tuteng
I was still prompted on `docker run`:
```
Enter the new value, or press ENTER for the default
Full Name []:
Room Number []:
Work Phone []:
Home Phone []:
Other []:
Is the information correct? [Y/n] Y
```
But manager started correctly and works, thank you.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] doug-ba commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostreSQL does not work
Posted by "doug-ba (via GitHub)" <gi...@apache.org>.
doug-ba commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1430639363
@splio-rbechon , the fix was committed in August of 2022. Is there any chance of getting a new container image release? The last release is effectively broken.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] jesperbagge commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "jesperbagge (via GitHub)" <gi...@apache.org>.
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] kocaki commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "kocaki (via GitHub)" <gi...@apache.org>.
kocaki commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1582032943
@malaskowski thanks for your answer! It looks like pulsar manager does more now because now I get " username or password is wrong". I try to login with pulsar and pulsar but it does not work.
When I check logs I see:
`Starting PostGreSQL Server
Adding group `pulsar' (GID 1000) ...
Done.
Adding user `pulsar' ...
Adding new user `pulsar' (1000) with group `pulsar' ...
Creating home directory `/home/pulsar' ...
Copying files from `/etc/skel' ...
Changing the user information for pulsar
Enter the new value, or press ENTER for the default
Use of uninitialized value $answer in chop at /usr/sbin/adduser line 582.
Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 583.
/pulsar-manager/startup.sh: 21: initdb: not found
/pulsar-manager/startup.sh: 22: pg_ctl: not found
createdb: error: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] Starting Pulsar Manager Front end
Starting Pulsar Manager Back end
Start Pulsar Manager by specifying a configuration file.
2023-06-08 07:04:43,465 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.
2023-06-08 07:04:43,466 INFO supervisord started with pid 64
2023-06-08 07:04:44,469 INFO spawned: 'pulsar-manager-backend' with pid 66
2023-06-08 07:04:45,562 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)`
So there is still an issue somewhere. I also tried deploying 0.4.0. In the logs of that release I do see that the db is created but for some reason also that one does not work. Logs of 0.4.0:
`Starting PostGreSQL Server
Adding group `pulsar' (GID 1000) ...
Done.
Adding user `pulsar' ...
Adding new user `pulsar' (1000) with group `pulsar' ...
Creating home directory `/home/pulsar' ...
Copying files from `/etc/skel' ...
Changing the user information for pulsar
Enter the new value, or press ENTER for the default
Use of uninitialized value $answer in chop at /usr/sbin/adduser line 582.
Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 583.
pg_ctl: directory "/data/postgresql" does not exist
Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] The files belonging to this database system will be owned by user "pulsar".
This user must also own the server process.
The database cluster will be initialized with locale "C".
The default database encoding has accordingly been set to "SQL_ASCII".
The default text search configuration will be set to "english".
Data page checksums are disabled.
creating directory /data/postgresql ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
Success. You can now start the database server using:
/usr/lib/postgresql/13/bin/pg_ctl -D /data/postgresql -l logfile start
waiting for server to start....2023-06-07 14:44:08.940 UTC [64] LOG: starting PostgreSQL 13.11 (Debian 13.11-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-06-07 14:44:08.940 UTC [64] LOG: listening on IPv6 address "::1", port 5432
2023-06-07 14:44:08.940 UTC [64] LOG: listening on IPv4 address "127.0.0.1", port 5432
2023-06-07 14:44:08.949 UTC [64] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-06-07 14:44:08.956 UTC [65] LOG: database system was shut down at 2023-06-07 14:44:08 UTC
2023-06-07 14:44:08.962 UTC [64] LOG: database system is ready to accept connections
done
server started
ALTER ROLE
CREATE DATABASE
GRANT
You are now connected to database "pulsar_manager" as user "pulsar".
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
Starting Pulsar Manager Front end
Starting Pulsar Manager Back end
Start servie no enable JWT.
2023-06-07 14:44:09,764 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.
2023-06-07 14:44:09,766 INFO supervisord started with pid 92
2023-06-07 14:44:10,769 INFO spawned: 'pulsar-manager-backend' with pid 93
2023-06-07 14:44:11,843 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-07 14:44:11,843 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-06-07 14:44:12,847 INFO spawned: 'pulsar-manager-backend' with pid 118
2023-06-07 14:44:13,936 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-07 14:44:13,936 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-06-07 14:44:14,939 INFO spawned: 'pulsar-manager-backend' with pid 143
2023-06-07 14:44:16,006 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-07 14:44:16,006 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-06-07 14:44:17,009 INFO spawned: 'pulsar-manager-backend' with pid 168
2023-06-07 14:44:18,072 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-07 14:44:18,072 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-06-07 14:44:19,075 INFO spawned: 'pulsar-manager-backend' with pid 193
2023-06-07 14:44:20,140 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-06-07 14:44:20,140 INFO exited: pulsar-manager-backend (exit status 1; not expected)`
Do you have any suggestions?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-manager] enzo-dechaene commented on issue #505: Starting Docker container pulsar-manager-0.3.0 with internal PostgreSQL does not work
Posted by "enzo-dechaene (via GitHub)" <gi...@apache.org>.
enzo-dechaene commented on issue #505:
URL: https://github.com/apache/pulsar-manager/issues/505#issuecomment-1584577019
Hello, @kocaki,
I'm using db postgresql embedded with pulsar manager **0.4.0**.
For the deployment of Pulsar Manager, I only refer to the configmap configuration in the env parameter:
```
spec:
containers:
- env:
- name: PULSAR_CLUSTER
value: pulsar
envFrom:
- configMapRef:
name: pulsar-pulsar-manager
image: apachepulsar/pulsar-manager:v0.4.0
imagePullPolicy: Always
name: pulsar-pulsar-manager
ports:
- containerPort: 9527
name: 9527tcp
protocol: TCP
resources:
requests:
cpu: 100m
memory: 250Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /data
name: pulsar-manager-data
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
terminationGracePeriodSeconds: 30
volumes:
- name: pulsar-manager-data
emptyDir: {}
```
The config map
```
DRIVER_CLASS_NAME: org.postgresql.Driver
JWT_TOKEN: my_pulsar_admin_token
LOG_LEVEL: DEBUG
PASSWORD: pulsar
USERNAME: pulsar
REDIRECT_HOST: your_ingress_url
REDIRECT_PORT: '80'
SECRET_KEY: my_secret_key
SPRING_CONFIGURATION_FILE: /pulsar-manager/pulsar-manager/application.properties
URL: jdbc:postgresql://127.0.0.1:5432/pulsar_manager
```
Notice that USERNAME and PASSWORD is not the credential for access the interface. It's the username of database.
You can check all parameter on this [link](https://pulsar.apache.org/docs/2.11.x/administration-pulsar-manager/#configuration)
If you want to add user pulsar, you must connect to the pulsar manager pod and run this script
```
apt update && apt install curl
CSRF_TOKEN=$(curl http://localhost:9527/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": "Administrateur", "email": "test@test.fr"}'
```
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org