-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/scylladb] JMX service fails #68036
Comments
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
Unfortunately, i'm too noob to contribute :( |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
The jmx process is not executed unless you enable this env var SCYLLADB_RUN_JMX_PROXY That env var is set to "no" by default. Can you try setting that env var to yes and confirm that JMX is started properly? |
No it doesn't. |
Hi @siddjellali, I just configured that env var and the process was launched without problems
If you continue running into issues, please take a look at the log file at |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/scylladb:6.0/debian-12
What architecture are you using?
amd64
What steps will reproduce the bug?
What is the expected behavior?
Run JMX service
What do you see instead?
JMX fails to start in ScyllaDB due to an incorrect definition of the LOCATION_SCRIPTS variable in the /opt/scylladb/jmx/scylla-jmx script.
LOCATION_SCRIPTS must be "jmx" instead of "scripts"
Additional information
The text was updated successfully, but these errors were encountered: