人为因素6.8.7无法启动,因为无法连接到访问服务器

时间:2019-03-16 12:21:55

标签: artifactory

由于在RHEL 7上使用rpm升级到6.8.7,使用systemctl启动工件失败

在日志中查找此时的失败

2019-03-16 09:50:28,952 [art-init] [INFO ] (o.a.s.a.ArtifactoryAccessClientConfigStore:593) - Using Access Server URL: http://localhost:8040/access (bundled) source: detected
2019-03-16 09:50:29,379 [art-init] [INFO ] (o.a.s.a.AccessServiceImpl:353) - Waiting for access server...
2019-03-16 09:50:30,625 [art-init] [WARN ] (o.j.a.c.AccessClientHttpException:41) - Unrecognized ErrorsModel by Access. Original message: Failed on executing /api/v1/system/ping, with response: Not Found
2019-03-16 09:50:30,634 [art-init] [ERROR] (o.a.s.a.AccessServiceImpl:364) - Could not ping access server: {}
org.jfrog.access.client.AccessClientHttpException: HTTP response status 404:Failed on executing /api/v1/system/ping, with response: Not Found

以前我们会得到

2019-03-13 09:56:06,293 [art-init] [INFO ] (o.a.s.a.ArtifactoryAccessClientConfigStore:593) - Using Access Server URL: http://localhost:8040/access (bundled) source: detected
2019-03-13 09:56:06,787 [art-init] [INFO ] (o.a.s.a.AccessServiceImpl:353) - Waiting for access server...
2019-03-13 09:56:24,068 [art-init] [INFO ] (o.a.s.a.AccessServiceImpl:360) - Got response from Access server after 17280 ms, continuing.

有关调试此访问服务器是否已启动的任何建议吗?

此外,我发现了一些日志,其中显示了该日志在工作时用于启动jar文件

2019-03-08 09:19:11,609 [localhost-startStop-2] [INFO ] (o.j.a.AccessApplication:48) - Starting AccessApplication v4.1.48 on hostname.nexor.co.uk with PID 5913 (/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-application-4.1.48.jar started by artifactory in /)

现在,当我看时,我发现/ opt / jfrog / artifactory / tomcat / webapps / access /为空,因此没有运行的jar文件

rpm确实提供了一个access.war文件,并且已经存在

$ ls -l /opt/jfrog/artifactory/webapps
total 104692
-rwxrwxr-x. 1 root root 51099759 Mar 14 12:14 access.war
-rwxrwxr-x. 1 root root 56099348 Mar 14 12:14 artifactory.war

我是否可以执行一些手动步骤来扩展此war文件以获取jar(您可能会猜到我不在我的Java应用程序中)

3 个答案:

答案 0 :(得分:1)

最终通过删除空的/ opt / jfrog / artifactory / tomcat / webapps / access目录并创建了一个包含所需jar文件的新目录来使其工作。

不知道为什么会这样,但这对我有用

答案 1 :(得分:0)

尝试将tomcat\conf\server.xml下的端口号从8081更改为另一个未使用的端口。然后,重新启动Artifactory服务,以确保更改生效。

答案 2 :(得分:0)

我在 CentOS 7 上遇到了类似的问题,解决方案是通过运行以下命令来降级新更新的 java 包:

yum downgrade java-1.8.0*

然后重启神器:

systemctl restart artifactory