1

Recent times jfrog server got rebooted from there when we start jfrog we are getting below stating like 8046 refused.

ERROR:

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:8046 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

TylerH
  • 20,799
  • 66
  • 75
  • 101
kranthi kk
  • 21
  • 3

2 Answers2

1

The problem the access.war file, the folder which was created out of access.war is empty so that created such an issue. Later after deleting the folder and started the service, jfrog came up and running

kranthi kk
  • 21
  • 3
0

Appears to be an issue with the port availability. By meaning reboot, are you referring to the VM reboot [or] it's just the Application restart? If it's a VM reboot, we might need to review the port configuration (firewall configuration - whether the required ports are available, security groups - if any external provider is being used).

Yuvarajan
  • 450
  • 2
  • 5
  • Thanks for the reply @yuvarajan firewall status is switched off, done VM and applications reboots both. ERROR LOG-Artifactory-service.log Caused by: java.util.concurrent.ExecutionException: org.jfrog.common.ExecutionFailed: Cluster join: Service registry ping failed; Error while trying to connect to local router at address 'http://localhost:8046/access': Connect to localhost:8046 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused) Please help me out from this – kranthi kk Sep 12 '22 at 07:35
  • 2022-09-12T07:29:28.832Z [jfrou] [FATAL] [735858fd40b2750d] [e_tenant_services_holder.go:35] [main ] [] - Failed joining Access: cluster join: Service registry ping failed; context deadline exceeded. last error: could not parse error from service registry, status code: 404, Please verify bot the logs and share your suggestions @yuvarajan – kranthi kk Sep 12 '22 at 07:39
  • Are there any specific errors returned in the access-service.log? – Yuvarajan Sep 12 '22 at 08:17