We just update our artifactory 6.10.9 to 7.6.3 on Ubuntu using debian package.
The migration.log show that the migration complete successfully
the service start bu we get a 404 when accessing the server.
There is errors on router-service.log:
[jfrou] [FATAL] [1ef8ac7a8bab9898] [bootstrap.go:93] [main] - Cluster join: Failed resolving join key: failed resolving 'shared.security.joinKey' key; file does not exist: /opt/jfrog/artifactory/var/etc/security/join.key
in frontend-service.log :
[jffe ] [ERROR] [ ] [ ] [main] - Error: connect ECONNREFUSED 127.0.0.1:8046
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
in metadata-service.log :
[jffe ] [ERROR] [ ] [ ] [main] - Error: connect ECONNREFUSED 127.0.0.1:8046
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
And this is the first errors in the console.log :
2020-08-18T19:27:12.494Z [jfrt ] [ERROR] [d2fc2e16d5fc1039] [actoryContextConfigListener:83] [ocalhost-startStop-1] - Failed initializing Artifactory context: Artifactory home not initialized.
2020-08-18T15:27:12.495L [tomct] [SEVERE] [ ] [org.apache.catalina.core.StandardContext] [org.apache.catalina.core.StandardContext startInternal] - One or more listeners failed to start. Full details will be found in the appropriate container log file
2020-08-18T15:27:12.497L [tomct] [SEVERE] [ ] [org.apache.catalina.core.StandardContext] [org.apache.catalina.core.StandardContext startInternal] - Context [/artifactory] startup failed due to previous errors
Does someone already had this kind of issue ? Thanks for clues.
2
Answers
Final problem was due to bad host file. fixing it with good entries solved the last problem
Based on the error log snippet, it looks like the issue is with the router not coming up. Can you check the $JFROG_HOME/artifactory/var/log/router-service.log file if there is an error entry causing this issue?