【发布时间】：2019-04-27 04:44:08
【问题描述】：
我已使用以下位置提供的说明将 Artifactory 6.0.2 安装的一些测试实例升级到版本 6.9.1：
https://www.jfrog.com/confluence/display/RTF/Upgrading+Artifactory
我已经尝试过 yum 升级和 rpm 安装路径，并且希望在安装结束时在日志文件中不显示任何错误消息，以尽量减少此类错误带来的任何潜在问题。
在安装和许多手动修复步骤后，我遇到了一个错误"Unable to request the Metadata Service Service-Id"，我无法在 Google 上找到以下结果：
2019-04-09 16:22:13,409 [art-init] [ERROR] (o.a.m.s.s.ArtifactoryMetadataClientConfigStore:111) - Unable to request the Metadata Service Service-Id
2019-04-09 16:22:13,409 [art-init] [ERROR] (o.a.m.s.MetadataEventServiceImpl:188) - Unable to init the Metadata client. The Metadata Event pipeline will be disabled.
yum 升级和 rpm 安装途径我都试过了。
升级后，我注意到 Catalina 和 Artifactory 日志文件中存在错误，并关注了有关这些错误消息的 google 搜索结果（在我的问题下方添加以供后代使用）：
(1) 创建：
/var/opt/jfrog/artifactory/access/etc/bootstrap.creds
Containing:
access-admin@127.0.0.1=NEW_PASSWORD
(2) 删除访问文件夹：
rm -rf /opt/jfrog/artifactory/tomcat/webapps/access
(3) Artifactory 目录权限改变：
cd /var/opt/jfrog/artifactory/
chown -R artifactory:artifactory .
(4) 编辑artifactory.system.properties 文件添加：
artifactory.pathChecksum.migration.job.enabled=true
(5) 通过将此内容添加到同一文件中来启用 sha 256 迁移：
##SHA2 Migration block
artifactory.sha2.migration.job.enabled=true
artifactory.sha2.migration.job.queue.workers=5
(5) 最后，Rebooted instance。
但包括The Metadata Event pipeline will be disabled 在内的错误仍然存在。
我希望 Artifactory 服务器的最终状态不会在 Artifactory 和 Catalina 日志文件中出现错误消息。
我们将非常感谢任何有关纠正此错误以便我可以部署最新的 Artifactory 版本的帮助。
提前谢谢你。
=======================
以下是一些引发上述更改的错误日志：
(1)2019-03-27 05:03:22,872 [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-27 05:03:22,872 [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.
(2)2019-03-27 05:06:53,235 [art-exec-3] [INFO ]
(o.a.s.j.m.s.Sha256MigrationJobDelegate:216) - SHA256 migration job (for existing artifacts) is disabled and will not run, there are 52496 artifacts without SHA256 values in the database. Future versions of Artifactory may enforce this migration as a prerequisite for upgrades.
(3)2019-04-04 16:20:10,951 [localhost-startStop-1] [JFrog-Access] [WARN ] (o.s.b.c.e.AnnotationConfigEmbeddedWebApplicationContext:550) - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start embedded container; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.boot.autoconfigure.jersey.JerseyAutoConfiguration': Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jerseyConfig' defined in URL [jar:file:/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-application-4.2.0.jar!/org/jfrog/access/rest/config/JerseyConfig.class]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.jfrog.access.rest.config.JerseyConfig]: Constructor threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'systemResource' defined in URL [jar:file:/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-server-rest-4.2.0.jar!/org/jfrog/access/server/rest/resource/system/SystemResource.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'backupSubResource' defined in URL [jar:file:/opt/jfrog/artifactory/tomcat/webapps/access/WEB-INF/lib/access-server-rest-4.2.0.jar!/org/jfrog/access/server/rest/resource/system/backup/BackupSubResource.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'backupServiceImpl': Unsatisfied dependency expressed through field 'importerExporter'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'accessImporterExporterImpl': Unsatisfied dependency expressed through method 'setServerBootstrap' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'accessServerBootstrapImpl': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Failed to bootstrap initial access credentials.
【问题讨论】：
-
我相信您面临的问题是因为工件没有暴露访问api。这可能是因为删除了访问文件夹。你的神器也不是因为这个而倒闭的，对吧？它已经启动并运行了吗？
-
@error404 不，我的 Artifactory 实例没有关闭：我已经升级了一个测试实例。我一直收到错误消息：
org.jfrog.access.client.AccessClientHttpException: HTTP response status 404:Failed on executing /api/v1/system/ping, with response: Not Found并在此处遵循建议的解决步骤：stackoverflow.com/questions/55196720/… -
该帖子建议删除所述目录以修复观察到的问题。我可以在不删除此访问文件夹的情况下尝试另一次升级，但需要不同的解决步骤才能通过错误消息
org.jfrog.access.client.AccessClientHttpException: HTTP response status 404:Failed on executing /api/v1/system/ping, with response: Not Found -
其中一条评论还指出它曾经不成功。你 。可以尝试从 6.0.2 测试升级到 6.9.1。这也没有数据库迁移，对吗？升级时还要检查数据库驱动程序是否也需要更新？另外，您使用 derby 或 postgres 的数据库是什么？
-
@error404，没有数据库迁移，实例刚刚就地升级。数据库驱动程序很好。我们使用默认的 derby 数据库。
标签： artifactory