Service failed to start NoClassDefFoundError: log4j.LogManager
search cancel

Service failed to start NoClassDefFoundError: log4j.LogManager

book

Article ID: 253947

calendar_today

Updated On:

Products

CA Process Automation Base

Issue/Introduction

After adding the new node to existing cluster, service failed to start. The boot.log contains below error:
01:07:10,202 ERROR [AbstractKernelController] Error installing to Instantiated: name=c2o.system:service=StartUPInterceptor state=Described mode=Manual requiredState=Configured
java.lang.NoClassDefFoundError: org.apache.logging.log4j.LogManager

Environment

Release : 4.3.05 

Cause

Existing nodes in the cluster has CP06 patch installed and the new node is missing the CP06 patch.

Resolution

Apply the CP06 patch on top of 4.3.05 in the newly installed node.

Additional Information

Whenever new node got added/installed to existing cluster, need to apply the Hotfixes (HF) or Cumulative (CP) patches same as the existing nodes as the installer won't be aware of the HF/CP's that were applied.