-
Notifications
You must be signed in to change notification settings - Fork 447
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
JoinKey not being found and Artifactory not starting when using value from secret. Present in bootstrap dir but not copied. #1918
Comments
same as #1917 |
@artm I installed artifactory-oss from scratch. It is a fresh installation |
@shettypriy we also installed from scratch, maybe something in #1917 can unblock you - especially about looking for errors elsewhere |
@reespozzi I am trying to create security.import.xml and artifactory.config.import.xml as mentioned #1917 . But I want to what should be the contents in this file. But I do not see any other error apart from join key is missing |
can someone help me with the contents of security.import.xml and artifactory.config.import.xml? |
@shettypriy you can ignore those. Removed from my original comment, not directly related |
@reespozzi artifactory-server and access-server log had below error
After adding below configurations in values.yaml file and correcting the indentation, it worked
|
Hi All, Please Note: JFrog does not support to run Artifactory on Kubernetes with Derby database. When running Artifactory with JFrog Helm Chart - You must use the embedded PostgreSQL database (Or external database like Oracle, MSSQL, etc) I will suggest to enable PostgreSQL and reinstalled the chart. |
Is this a request for help?: yes
Version of Helm and Kubernetes:
argocd version | grep -i helm
Helm Version: v3.6.0+g7f2df64
EKS kubernetes version 1.29
Which chart:
artifactory-oss
Which product license (Enterprise/Pro/oss): oss
What happened:
Artifactory will not start. Logs are full of stack traces relating to the join key:
2024-09-10T16:48:58.990Z [jfrou] [INFO ] [5dde291e9e618397] [security_keys.go:185 ] [main ] [] - Cluster join: Join key is missing. Pending for 5 seconds with 5m0s timeout
What you expected to happen:
I expected the artifactory pod to run completely
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
I have created kubernetes secrets for both masterkey and joinkey and mentioned the secretname in values.yaml file. Below is my helm values file
The text was updated successfully, but these errors were encountered: