CA Workload Automation DE : Unsupported logging configuration. Rolling appender is not attached to the root logger.
search cancel

CA Workload Automation DE : Unsupported logging configuration. Rolling appender is not attached to the root logger.

book

Article ID: 69200

calendar_today

Updated On:

Products

DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries) CA Workload Automation DE CA Workload Automation DE - Business Agents (dSeries)

Issue/Introduction

The DE server is not able to write or create new logs.  The following message may be seen in stdout:

Log file contains error message “Unsupported logging configuration. Rolling appender is not attached to the root logger.”


 

Environment

Component:  CA Workload Automation DE R12.x

OS Any

Cause

The XML related to logging is corrupted.

Resolution

  • Navigate to the dSeries installation directory.
  • Change directory to the logs directory for the dSeries server.
  • Backup and remove the buffer folder (or remove index.xml file in buffer subdirectory).
  • Restart the dSeries server processes.
  • Check the logs to verify the error is resolved.
  • Additional: Check startServer in bin directory has misconfigured log4j file location.
    • Check startServer (Linux) or startServer.lax (Windows) for following:

Linux

ARGS=" -Xms${MIN_HEAP_SIZE}m -Xmx${MAX_HEAP_SIZE}m -Duser.dir=${CAWA_HOME} -Dserver.pidfile=${PID_FILE} -Duser.language=en -Dlog4j.configurationFile=file:///${CAWA_HOME}/conf/server.log4j.xml -Dlog.directory=${CAWA_HOME}/logs -Dlax.root.install.dir=${CAWA_HOME}/"

Windows

lax.nl.java.option.additional=-Xms8M -Xmx1024M -Duser.language=en -Djava.rmi.server.hostname=de.example.com -Duser.dir="C:\\Program Files\\CA\\ESPdSeriesWAServer" -Djava.library.path="C:\\Program Files\\CA\\ESPdSeriesWAServer\\lib" -Dlog4j2.configurationFile="file:///C:\\Program Files\\CA\\ESPdSeriesWAServer\\conf\\server.log4j.xml" -Dlog.directory="C:\\Program Files\\CA\\ESPdSeriesWAServer\\logs" -Djdk.lang.Process.allowAmbigousCommands=true