Buffer logs not getting created
search cancel

Buffer logs not getting created


Article ID: 9082


Updated On:


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


The CA Workload Automation DE may not be capturing or update the buffer and other logs.  When issuing a spinlog command or other CLI commands, the user may see the following error:

Unsupported logging configuration. Rolling appender is not attached to the root logger.

If DE is running on UNIX/Linux OS, then check the <de_install_directory>/logs/stdout.txt file.  It may show error like this:

The server PID file is /opt/CA/DE_R12/serverPID

log4j:ERROR Unable to create RetainRequestManager for appender BUFFER

org.jdom2.input.JDOMParseException: Error on line -1: Premature end of file.

at org.jdom2.input.sax.SAXBuilderEngine.build(SAXBuilderEngine.java:232)

at org.jdom2.input.SAXBuilder.build(SAXBuilder.java:1065)

at com.ca.wa.core.engine.log.buffer.RetainRequestMarshaller.read(RetainRequestMarshaller.java:115)

at com.ca.wa.core.engine.log.buffer.BufferManager.readRequestsFromFile(BufferManager.java:235)

at com.ca.wa.core.engine.log.buffer.BufferManager.initialize(BufferManager.java:143)

at com.ca.wa.core.engine.log.buffer.BufferManager.<init>(BufferManager.java:128)

at com.ca.wa.core.engine.log.buffer.BufferFileAppender.activateOptions(BufferFileAppender.java:359)

at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:257)

at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:285)

at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:171)

…snip….. com.ca.wa.core.engine.bootstrap.ServerMain.loadCommandLineProperties(ServerMain.java:700)

at com.ca.wa.core.engine.bootstrap.ServerMain.loadProperties(ServerMain.java:467)

at com.ca.wa.core.engine.bootstrap.ServerMain.main(ServerMain.java:271)

Caused by: org.xml.sax.SAXParseException; Premature end of file.

at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)

at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)

at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)


For Windows OS, check the Event Viewer for any errors.



CA Workload Automation DE R12OS - AnyDB - Any


The logs may stop due to corruption in the logging configuration files.  If any changes were made to the following files, then you may either revert changes or restore the old configuration files.







Check to see if the <de_install_directory>/logs/buffer/index.xml file has been changed.  If it is empty, then it will need to be replaced.  By default, the index.xml has the following contents.

<?xml version="1.0" encoding="UTF-8"?>


<requests xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />


You may remove or rename the old index.xml and restart the DE server.

Once the DE service has been restarted it will create a new index.xml. Check to see if it is present and the logs are getting created properly.