virtual appliance Identity manager will not start after upgrade to 14.5

Products

• CA Identity Manager

Issue/Introduction

After upgrade of 14.4 to 14.5 of the virtual appliance 

IM will not start due to this error:

024-03-22 23:53:08,183 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/root-logger=ROOT' are not available:
    org.wildfly.logging.handler.FILE; Possible registration points for this capability: 
        /subsystem=logging/async-handler=*
        /subsystem=logging/console-handler=*
        /subsystem=logging/file-handler=*
        /subsystem=logging/periodic-rotating-file-handler=*
        /subsystem=logging/periodic-size-rotating-file-handler=*
        /subsystem=logging/size-rotating-file-handler=*
        /subsystem=logging/custom-handler=*
        /subsystem=logging/syslog-handler=*
        /subsystem=logging/socket-handler=*
        /subsystem=logging/logging-profile=*/async-handler=*
        /subsystem=logging/logging-profile=*/console-handler=*
        /subsystem=logging/logging-profile=*/file-handler=*
        /subsystem=logging/logging-profile=*/periodic-rotating-file-handler=*
        /subsystem=logging/logging-profile=*/periodic-size-rotating-file-handler=*
        /subsystem=logging/logging-profile=*/size-rotating-file-handler=*
        /subsystem=logging/logging-profile=*/custom-handler=*
        /subsystem=logging/logging-profile=*/syslog-handler=*
        /subsystem=logging/logging-profile=*/socket-handler=*

 

2024-03-22 23:53:08,183 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=logging/logger=ims.TelemetryJob' are not available:
    org.wildfly.logging.handler.Telemetry; Possible registration points for this capability: 
        /subsystem=logging/async-handler=*
        /subsystem=logging/console-handler=*
        /subsystem=logging/file-handler=*
        /subsystem=logging/periodic-rotating-file-handler=*
        /subsystem=logging/periodic-size-rotating-file-handler=*
        /subsystem=logging/size-rotating-file-handler=*
        /subsystem=logging/custom-handler=*
        /subsystem=logging/syslog-handler=*
        /subsystem=logging/socket-handler=*
        /subsystem=logging/logging-profile=*/async-handler=*
        /subsystem=logging/logging-profile=*/console-handler=*
        /subsystem=logging/logging-profile=*/file-handler=*
        /subsystem=logging/logging-profile=*/periodic-rotating-file-handler=*
        /subsystem=logging/logging-profile=*/periodic-size-rotating-file-handler=*
        /subsystem=logging/logging-profile=*/size-rotating-file-handler=*
        /subsystem=logging/logging-profile=*/custom-handler=*
        /subsystem=logging/logging-profile=*/syslog-handler=*
        /subsystem=logging/logging-profile=*/socket-handler=*
2024-03-22 23:53:08,189 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

Environment

virtual appliance 14.5 14.4

Cause

This does not happen in all upgrades from 14.4 to 14.5

There is a wide spread patch for logging, that may or may not have been applied to the vApp 

Resolution

This issue was identified and fixed in 14.5.1, currently it is being tested.