PPDM: Services down with "Could not initialize Logback logging from config-logback.xml"

Summary: After PowerProtect Data Manager runs out of space, all services are down and it restarts.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

All PowerProtect Data Manager services cannot be started.

In the var/log/brs/"service"/"service".out such as /usr/local/brs/adm/adm.out as an example: 
2024-10-09T07:44:40.397Z INFO [] [main] [][][][][] c.e.d.e.adm.server.app.Application.main(74) -  Application:main ready, set, go! 
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
Logging system failed to initialize using configuration from 'config/logback.xml'
java.lang.IllegalStateException: Could not initialize Logback logging from config/logback.xml
	at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:168)
        []
	at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:298)
	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:246)
	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:223)
	[]
	at com.emc.brs.ThinJarLauncher.main(ThinJarLauncher.java:19)
Caused by: ch.qos.logback.core.joran.spi.JoranException: Problem parsing XML document. See previously reported errors.
        []
	at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:165)
	... 43 more
Caused by: org.xml.sax.SAXParseException; systemId: file:/usr/local/brs/lib/adm/config/logback.xml; lineNumber: 1; columnNumber: 1; Premature end of file.
	at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1251)
	at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:637)
	at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:326)
	at ch.qos.logback.core.joran.event.SaxEventRecorder.recordEvents(SaxEventRecorder.java:59)

ERROR SpringApplication Application run failed
 java.lang.IllegalStateException: java.lang.IllegalStateException: Could not initialize Logback logging from config/logback.xml
Caused by: java.lang.IllegalStateException: Could not initialize Logback logging from config/logback.xml
Caused by: ch.qos.logback.core.joran.spi.JoranException: Problem parsing XML document. See previously reported errors.
Caused by: org.xml.sax.SAXParseException; systemId: file:/usr/local/brs/lib/adm/config/logback.xml; lineNumber: 1; columnNumber: 1; Premature end of file.

2024-10-09T07:46:49.961Z INFO [] [main] [][][][][] c.e.d.e.adm.server.app.Application.main(74) -  Application:main ready, set, go! 
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

Cause

The files /usr/local/brs/lib/*/config/logback.xml were all empty, and so the service could not be initialized.

Resolution

From another PowerProtect Data Manager, get the equivalent file for /usr/local/brs/lib/*/config/logback.xml or for the service that is down, and copy and paste it to the location where the logback.xml file is empty.

If another PowerProtect Data Manager host is not available, contact Dell Support.

Affected Products

PowerProtect Data Manager
Article Properties
Article Number: 000247554
Article Type: Solution
Last Modified: 05 Dec 2024
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.