Upgrade Wildfly 10.1 to 21 via jboss-server-migration-wildfly10.0-1.10.0.Final Tool
386 views
Skip to first unread message
Stefan Harbich
Jan 21, 2021, 10:29:20 AM1/21/21
to WildFly
Hello, I want to update my WildFly version. From version 10.1 to version 21. Unfortunately, when I start the migration tool, I get an error message:
root@dsme01:/usr/share/CA/wildfly-server-migration/dist/standalone/target/jboss-server-migration# ./jboss-server-migration.sh -s /usr/share/CA/wildfly-10.1.0.Final -t /usr/share/CA/wildfly-21.0.0.Final/
----------------------------------------------------------
---- JBoss Server Migration Tool -----------------------
----------------------------------------------------------
Retrieving servers...
INFO SOURCE server name: WildFly Full, version: 10.1.0.Final.
INFO TARGET server name: WildFly Full, version: 21.0.0.Final.
----------------------------------------------------------
----------------------------------------------------------
Server migration starting...
INFO --- Migrating modules requested by environment...
INFO No modules to migrate.
Migrate the source's standalone server?
yes/no? y
INFO --- Migrating standalone server...
INFO Source's standalone content migrated.
INFO Source's standalone configurations found: [standalone-full-ha.xml, standalone-full.xml, standalone-ha.xml, standalone.xml]
Migrate all configurations?
yes/no? y
INFO Migrating standalone configuration standalone-full-ha.xml...
INFO Subsystem infinispan updated.
INFO Subsystem undertow updated.
INFO Subsystem jgroups updated.
INFO Subsystem core-management added.
INFO Subsystem elytron added.
INFO Subsystem discovery added.
INFO Subsystem ee-security added.
INFO Subsystem microprofile-config-smallrye added.
INFO Subsystem microprofile-health-smallrye added.
INFO Subsystem microprofile-opentracing-smallrye added.
INFO Subsystem microprofile-metrics-smallrye added.
INFO Socket binding's multicast address expressions added.
INFO Security realms migrated.
INFO Security realm ApplicationRealm SSL server identity configured.
INFO Non-persistent deployments found in /usr/share/CA/wildfly-10.1.0.Final/standalone/deployments: [mariadb-java-client.jar, ejbca.ear]
This tool is not able to assert if the non-persistent deployments found are compatible with the target server, skip scanner's deployments migration?
yes/no? y
INFO Migrating standalone configuration standalone-full.xml...
INFO Subsystem infinispan updated.
INFO Subsystem undertow updated.
INFO Subsystem core-management added.
INFO Subsystem elytron added.
INFO Subsystem discovery added.
INFO Subsystem ee-security added.
INFO Subsystem microprofile-config-smallrye added.
INFO Subsystem microprofile-health-smallrye added.
INFO Subsystem microprofile-opentracing-smallrye added.
INFO Subsystem microprofile-metrics-smallrye added.
INFO Security realms migrated.
INFO Security realm ApplicationRealm SSL server identity configured.
INFO Migrating standalone configuration standalone-ha.xml...
INFO Subsystem infinispan updated.
INFO Subsystem undertow updated.
INFO Subsystem jgroups updated.
INFO Subsystem core-management added.
INFO Subsystem elytron added.
INFO Subsystem discovery added.
INFO Subsystem ee-security added.
INFO Subsystem microprofile-config-smallrye added.
INFO Subsystem microprofile-health-smallrye added.
INFO Subsystem microprofile-opentracing-smallrye added.
INFO Subsystem microprofile-metrics-smallrye added.
INFO Socket binding's multicast address expressions added.
INFO Security realms migrated.
INFO Security realm ApplicationRealm SSL server identity configured.
INFO Migrating standalone configuration standalone.xml...
INFO Subsystem infinispan updated.
ERROR Migration failed: org.jboss.migration.core.ServerMigrationFailureException: org.jboss.migration.wfly10.config.management.ManagementOperationException: WFLYCTL0369: Required capabilities are not available:
org.wildfly.network.socket-binding.https; Possible registration points for this capability:
/socket-binding-group=*/socket-binding=*
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:174) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.execute(TaskExecutionImpl.java:159) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:68) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:32) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.CompositeSubtasksBuilder.lambda$null$2(CompositeSubtasksBuilder.java:33) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.CompositeSubtasks.run(CompositeSubtasks.java:42) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.TaskRunnable$Builder.lambda$null$0(TaskRunnable.java:44) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.ComponentTask$Builder.lambda$buildRunnable$0(ComponentTask.java:129) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.ComponentTask.run(ComponentTask.java:46) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:169) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.execute(TaskExecutionImpl.java:159) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:68) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:32) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.ServerConfigurationMigration$1.run(ServerConfigurationMigration.java:106) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:169) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.execute(TaskExecutionImpl.java:159) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:68) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:32) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.ServerConfigurationsMigration$Task.migrateConfig(ServerConfigurationsMigration.java:151) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.ServerConfigurationsMigration$Task.migrateAllConfigs(ServerConfigurationsMigration.java:120) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.ServerConfigurationsMigration$Task.run(ServerConfigurationsMigration.java:105) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:169) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.execute(TaskExecutionImpl.java:159) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:68) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:32) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.StandaloneServerMigration$1.run(StandaloneServerMigration.java:61) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.console.UserConfirmationServerMigrationTask.runTask(UserConfirmationServerMigrationTask.java:58) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.console.UserConfirmationServerMigrationTask.confirmTaskRun(UserConfirmationServerMigrationTask.java:50) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.console.UserConfirmationServerMigrationTask.run(UserConfirmationServerMigrationTask.java:63) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.env.SkippableByEnvServerMigrationTask.run(SkippableByEnvServerMigrationTask.java:47) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:169) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.execute(TaskExecutionImpl.java:159) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:68) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskContextImpl.execute(TaskContextImpl.java:32) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.ServerMigration.run(ServerMigration.java:45) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.WildFlyServer10.migrate(WildFlyServer10.java:40) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.ServerMigration$1.run(ServerMigration.java:153) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:169) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.ServerMigration.run(ServerMigration.java:160) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.cli.CommandLineServerMigration.main(CommandLineServerMigration.java:131) [jboss-server-migration-cli-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
Caused by: org.jboss.migration.wfly10.config.management.ManagementOperationException: WFLYCTL0369: Required capabilities are not available:
org.wildfly.network.socket-binding.https; Possible registration points for this capability:
/socket-binding-group=*/socket-binding=*
at org.jboss.migration.wfly10.config.management.impl.AbstractManageableServerConfiguration.processResult(AbstractManageableServerConfiguration.java:103) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.management.impl.AbstractManageableServerConfiguration.executeManagementOperation(AbstractManageableServerConfiguration.java:116) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.subsystem.undertow.AddHttpsListener.updateConfiguration(AddHttpsListener.java:71) [jboss-server-migration-wildfly10.1-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.wfly10.config.task.management.subsystem.UpdateSubsystemResourceSubtaskBuilder.lambda$null$1(UpdateSubsystemResourceSubtaskBuilder.java:49) [jboss-server-migration-wildfly10.0-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.ComponentTask$Builder.lambda$buildRunnable$0(ComponentTask.java:129) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.component.ComponentTask.run(ComponentTask.java:46) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
at org.jboss.migration.core.task.TaskExecutionImpl.run(TaskExecutionImpl.java:169) [jboss-server-migration-core-1.10.0.Final-SNAPSHOT.jar:1.10.0.Final-SNAPSHOT]
... 39 more
INFO
----------------------------------------------------------------------------------------------------------
Task Summary
----------------------------------------------------------------------------------------------------------
server .......................................................................................... FAIL
standalone ..................................................................................... FAIL
contents.standalone.migrate-content-dir ....................................................... SUCCESS
contents.standalone.migrate-content(path=cb/ad0797cd528a899f39b1b5ef833e11b8fc3a20/content) .. SUCCESS
contents.standalone.migrate-content(path=12/b1888277a2291a8c370f996bd0b27efa7381ed/content) .. SUCCESS
standalone-configurations ..................................................................... FAIL
standalone-configuration(source=standalone-full-ha.xml) ...................................... SUCCESS
standalone-configuration(source=standalone-full.xml) ......................................... SUCCESS
standalone-configuration(source=standalone-ha.xml) ........................................... SUCCESS
standalone-configuration(source=standalone.xml) .............................................. FAIL
----------------------------------------------------------------------------------------------------------
Migration Result: FAIL
----------------------------------------------------------------------------------------------------------
Can you help me?
Greetings from Stefan
Stefan Harbich
Jan 22, 2021, 1:08:06 AM1/22/21
to WildFly
Hi there,
It's really a shame that nobody can help me here.
Greetings from Stefan
Wolfgang
Jan 22, 2021, 3:24:38 PM1/22/21
to WildFly
Hi,
how does your source standalone.xml look like?
Did you by any chance remove/change the socket binding for HTTPS?
In a default WildFly 10 package, the "socking-bindings" element looks like this:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
Hope this helps
Wolfgang
Stefan Harbich
Jan 23, 2021, 4:18:24 AM1/23/21
to WildFly
Hello Wolfgang,
I don't think it's socking-bindings related. I'm tapping the following message:
"2021-01-23 10:12:52,877 ERROR [management-operation] WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("security-realm" => "ManagementRealm")"
Unfortunately my update still runs on an error. Attached the migration.log file.
Greetings from Stefan
Reply all
Reply to author
Forward
0 new messages