Artifactory 从 7.55.* 升级到最新自托管版本如何处理?

问题描述 投票:0回答:1

我有两个运行

7.55.9
(旧的..)自托管
artifactory
版本的实例,我想将其迁移到最新版本。 (
7.98.12
)。我想在保持服务的同时做到这一点。 (一台服务器接着另一台服务器)

所以在这样做之前,我尝试了

sandbox

编辑: 在那

sandbox
我有2台旧版本的服务器而不是HA。 我升级了一台,并启动了服务,所以
db
也迁移了。 但如果我想在另一个上启动服务,我就会遇到一些问题。

这里

artifactory-service.log

2025-01-21T12:47:17.916Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [o.a.c.h.HaNodeProperties:65   ] [Catalina-utility-1  ] - Artifactory is running in non-clustered mode.
2025-01-21T12:47:17.926Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [tifactoryHomeConfigListener:85] [Catalina-utility-1  ] - Resolved Home: '/u01/app/jfrog/artifactory
2025-01-21T12:47:18.167Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [o.a.c.h.ArtifactoryHome:1005  ] [Catalina-utility-1  ] - Setting '' to system property 'spring.profiles.active'
2025-01-21T12:47:18.534Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [o.a.c.h.ArtifactoryHome:1005  ] [Catalina-utility-1  ] - Setting '' to system property 'spring.profiles.active'
2025-01-21T12:47:18.551Z [jfrt ] [INFO ] [                ] [o.j.c.w.FileWatcher:146       ] [file-watcher-poller ] - Starting watch of folder configurations
2025-01-21T12:47:18.686Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [.BasicConfigurationManager:186] [Catalina-utility-1  ] - Artifactory (jfrt) service initialization started. Version: 7.55.11 Revision: 75511900 PID: 55824 Home: /jfrog/artifactory
2025-01-21T12:47:18.729Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [d.c.m.ConverterManagerImpl:212] [Catalina-utility-1  ] - Triggering PRE_INIT conversion, from 7.55.11 to 7.55.11
2025-01-21T12:47:18.729Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [d.c.m.ConverterManagerImpl:215] [Catalina-utility-1  ] - Finished PRE_INIT conversion, current version is: 7.55.11
2025-01-21T12:47:18.730Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [d.i.DbInitializationManager:48] [Catalina-utility-1  ] - Initializing DB Schema initialization manager
2025-01-21T12:47:18.730Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [.i.DbInitializationManager:176] [Catalina-utility-1  ] - Database: PostgreSQL 13.18. Driver: PostgreSQL JDBC Driver 42.4.3 Pool: postgresql
2025-01-21T12:47:18.995Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [d.i.DbInitializationManager:52] [Catalina-utility-1  ] - DB Schema initialization manager initialized
2025-01-21T12:47:19.023Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [SchemaInitializationManager:48] [Catalina-utility-1  ] - Initializing Post-DB initialization manager
2025-01-21T12:47:19.387Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [o.j.c.DbSchemaVersionLogDao:89] [Catalina-utility-1  ] - Column 'error_message' already exists on 'schema_change_log' table.
2025-01-21T12:47:19.493Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [d.c.m.ConverterManagerImpl:212] [Catalina-utility-1  ] - Triggering HOME_SYNC_FILES conversion, from 7.98.12 to 7.55.11
2025-01-21T12:47:19.494Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [d.c.m.ConverterManagerImpl:215] [Catalina-utility-1  ] - Finished HOME_SYNC_FILES conversion, current version is: 7.55.11
2025-01-21T12:47:19.494Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [.c.ConfigurationManagerImpl:97] [Catalina-utility-1  ] - Starting file sync
2025-01-21T12:47:19.617Z [jfrt ] [INFO ] [c7f3b6ebcc45b3ba] [SchemaInitializationManager:51] [Catalina-utility-1  ] - Post-DB initialization manager initialized
2025-01-21T12:47:19.996Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [ctoryContextConfigListener:326] [art-init            ] -
:      
     /\        | | (_)/ _|         | |                   |  __ \
    /  \   _ __| |_ _| |_ __ _  ___| |_ ___  _ __ _   _  | |__) | __ ___
   / /\ \ | '__| __| |  _/ _` |/ __| __/ _ \| '__| | | | |  ___/ '__/ _ \
  / ____ \| |  | |_| | || (_| | (__| || (_) | |  | |_| | | |   | | | (_) |
 /_/    \_\_|   \__|_|_| \__,_|\___|\__\___/|_|   \__, | |_|   |_|  \___/
 Version:  7.55.11                                 __/ |
 Revision: 75511900                               |___/
 Product Version:  7.55.9
 Product Revision: 75509900
 Artifactory Home: '/jfrog/artifactory'
 Node ID: 'localhost'

2025-01-21T12:47:20.102Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [ifactoryApplicationContext:603] [art-init            ] - Artifactory application context set to NOT READY by refresh
2025-01-21T12:47:27.398Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.a.a.d.c:20                  ] [art-init            ] - Cloud environment is NOT_SPECIFIED
2025-01-21T12:47:27.400Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.a.a.d.c:20                  ] [art-init            ] - Cloud environment is NOT_SPECIFIED
2025-01-21T12:47:27.402Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [a.LicenseAddonsManagerImpl:125] [art-init            ] - Reading system property IS_AWS_LICENSE: null
2025-01-21T12:47:28.085Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [.GoogleCloudBinaryProvider:141] [art-init            ] - Bucket exists = true
2025-01-21T12:47:29.316Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [ritiesStorageServiceFactory:25] [art-init            ] - Initializing DB-based Priorities Storage Service
2025-01-21T12:47:33.284Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [HaRoleManagerServiceFactory:27] [art-init            ] - Initializing Task Affinity HA role manager
2025-01-21T12:47:33.607Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [actorySchedulerFactoryBean:729] [art-init            ] - Starting Quartz Scheduler now
2025-01-21T12:47:33.608Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [actorySchedulerFactoryBean:729] [art-init            ] - Starting Quartz Scheduler now
2025-01-21T12:47:33.651Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [ifactoryApplicationContext:291] [art-init            ] - Artifactory context starting up 83 Spring Beans...
2025-01-21T12:47:33.748Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.a.s.a.AccessServiceImpl:684 ] [art-init            ] - Initialized new service id: jfrt@01jj1vkm9dn0h31624a7aa1pef
2025-01-21T12:47:33.773Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [oryAccessClientConfigStore:510] [art-init            ] - Using Access Server URL: http://localhost:8046/access source: System Config
2025-01-21T12:47:35.428Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [.a.c.AccessClientBootstrap:146] [art-init            ] - Cluster join: Executing join on 'http://localhost:8046/access'
2025-01-21T12:47:35.558Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [.a.c.AccessClientBootstrap:156] [art-init            ] - Cluster join: Successfully joined the cluster
2025-01-21T12:47:36.486Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.j.a.c.g.AccessGrpcClient:111] [art-init            ] - Opened gRPC streams: 0
2025-01-21T12:47:36.509Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.j.a.c.g.AccessGrpcClient:111] [art-init            ] - Opened gRPC streams: 1
2025-01-21T12:47:36.510Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.a.s.a.AccessServiceImpl:615 ] [art-init            ] - Initialized access service successfully with client id 30060333, closing old client id [null]
2025-01-21T12:47:36.868Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [o.a.s.a.AccessServiceImpl:588 ] [art-init            ] - Successfully copied ldapConfig LdapConfig(forceGroupMemberAttFullDn=false, applyHeadlessValidation=true, connectTimeoutMillis=10000, readTimeoutMillis=10000, referralStrategy=follow, poolTimeoutMillis=0, paging=LdapPagingConfig(maxPageSize=1000, blacklistExpireAfterWriteMinutes=1440), group=LdapGroupConfig(search=LdapGroupSearchConfig(disableAttributesLimitation=false, filterThreshold=0), cleanOnFail=true))
2025-01-21T12:47:36.942Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [ryConfigStorageServiceImpl:171] [art-init            ] - About to update 130 repository configurations
2025-01-21T12:47:36.987Z [jfrt ] [INFO ] [d09758ea3cd08ff3] [.a.d.r.CentralConfigReader:115] [art-init            ] - The current Artifactory config schema namespace is 'http://artifactory.jfrog.org/xsd/3.2.6' The provided config does not seem to be compliant with it.
2025-01-21T12:47:37.057Z [jfrt ] [ERROR] [d09758ea3cd08ff3] [d.c.m.ConverterManagerImpl:278] [art-init            ] - Conversion failed. You should analyze the error and retry launching Artifactory. Error is: The current Artifactory config schema namespace is 'http://artifactory.jfrog.org/xsd/3.2.6' The provided config does not seem to be compliant with it.
The auto discovery of Artifactory configuration version did not find any valid version for the artifactory.config.xml file.
Please fix this file manually!                                                                                                                                                             

所以我已经尝试通过以下方式手动修复它,但遵循 jfrog 的这篇文章似乎不兼容复古。 https://jfrog.com/help/r/artifactory-how-to-resolve-application-could-not-be-initialized-the-current-artifactory-config-schema-namespace-is/artifactory-how-to -解决应用程序无法初始化当前artifactory-config-schema-namespace-is

但我仍然有问题。

所以我的问题是,我是否必须刻意停止两台服务器上的服务,并立即升级它们并重新启动服务,或者还有其他方法吗?

mwi

upgrade artifactory jfrog
1个回答
0
投票

谢谢David,我会遵循这个操作方式。

© www.soinside.com 2019 - 2024. All rights reserved.