-
Notifications
You must be signed in to change notification settings - Fork 299
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
Fresh installation of Artifactory OSS 7.12.6 doesn't start, missing jffe service #210
Comments
Can you please compress and upload the content of /opt/jfrog/artifactory/var/log |
Here it is |
Having the same issue on Ubuntu 20.04, on a fresh intall
Edit: DON'T DO THIS IF YOU HAVE ANY CONFIG YOU WISH TO KEEP
Wait for a little then try to open the page, all should be good. |
@Suphax how long did you wait for services to come up in 7.12.6 ? In a VM i tried, it took me around 28 seconds for all the services to come up. |
Roughly 30 minutes |
We are also seeing this issue on a Redhat 7 New Installation: 2021-02-16T23:49:15.747Z [jffe ] [ERROR] [ ] [ ] [main ] - ArtifactoryClient::http [get] request to /api/system/ping failed with 502 code and the status shows a Service is Healthy missing jffe error as well. |
2021-03-26T12:53:45.078Z [jffe ] [ERROR] [ ] [ ] [main ] - ArtifactoryClient::http [get] request to /api/system/ping failed with 404 code |
Can anyone tell me what this JFFE service is? |
I found that libvirtd was running. It wasn't libvirtd, itself, that prevented artifactory from coming up. It was the fact that the virbr0 interface was up. It doesn't seem to be a problem bringing this interface back up after artifactory comes up. |
I'm also having this issue. These three services do not start up. Seeing lots of "connection refused" errors from the different services as well as a java stacktrace when trying to initialize Home
Eventually, after many failed pings, the services all shut down. |
I've been getting stuck on this for the better part of the last day now. What I think is happening is the services are starting up before the
The
I'll see if I can gather enough evidence to open a bug with JFrog for this. I had to do the same workaround and start with 7.12.6 and then change up the version which is not how any of this should work. |
This is an old issue with an old version. |
Please re-read :) The only way to get this to work is to start with 7.12.6 and then upgrade after it is bootstrapped. |
logs.txt |
Thx. I'll have someone in the team review this again with the newer version. |
I ran into this issue while trying to bootstrap the configuration of my server. Then I added users and repositories, and copied the config- and security descriptors from the admin page to After rebooting, I hade the problem described above. By tinkering with the configuration over multiple resets, I found out that the Funnily enough, the admin user can have an unencoded user property (the one it has after the first boot with JSON), but after completing the setup, the security descriptor in the export contains some sort of encoded or encrypted value, and that will cause the server to fail on start-up, hanging forever while waiting for the I wasn't able to find anything in the log files about invalid configurations though, and it was purely (protracted) trial and error that led me to this. |
I actually found something similar. I got a case open with JFrog and worked with them live to troubleshoot. They had me use their |
Maybe add a deep link to help those who come here later? |
It's the same as the docker-compose download link on the Download page but this looks like it should be a fairly good permalink. |
I had the same issue that was due to another service using the artifactory default service port netstat -tunapl | grep 8081 I fixed the issue by defining an alternative port in the artifactory:
port: <another port> |
I am having the same issue on a fresh install |
I had the same issue, only to discover I was running on a M1 mac with the |
same issue on a fresh install with the latest version on Amazon Linux 2. |
I'm seeing what I think is the same behavior on Ubuntu 22.04 with
|
An FYI for anyone running into this issue. I ran into this same error today on an old version of Amazon Linux. The version of node that comes bundled with Artifactory requires a newer version of GLIB_C then can be installed on this version of AL. This stops the frontend service from starting leading to the jffe service not being available.
|
@isaac84 Thanks for this, do you know what version of node it now needs? |
Fixed this issue by setting environment variable no_proxy=localhost,127.0.0.1 |
I have the same problem on almalinux 9 starting artifactory as a service. Launching "$JFROG_HOME/artifactory/app/bin/artifactoryctl start" instead works. |
Thanks @mooh-pooh ! Your answer solved my issue, as I have proxy configured. |
I have done everything according to manuals from https://jfrog.com/open-source/
My Ubuntu version is 20.04. Since there is no "focal" in https://releases.jfrog.io/artifactory/artifactory-debs/, I've added "bionic":
Then I've installed jfrog-artifactory-oss version 7.12.6 and tried launching the service. It has launched, but browser, connected to ports :8081 or :8082 of localhost, shows that 3 services don't start:
Attached is the relevant part of logs:
art.log
The text was updated successfully, but these errors were encountered: