PPDM: Servizi inattivi con "Could not initialize Logback logging from config-logback.xml"

Summary: Una volta esaurito lo spazio di PowerProtect Data Manager, tutti i servizi sono inattivi e il sistema si riavvia.

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.

Symptoms

Non è possibile avviare tutti i servizi di PowerProtect Data Manager.

Nel var/log/brs/"service"/"service".out come /usr/local/brs/adm/adm.out A titolo di esempio:
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

I file /usr/local/brs/lib/*/config/logback.xml erano tutti vuoti e quindi non è stato possibile inizializzare il servizio.

Resolution

Da un altro PowerProtect Data Manager, ottenere il file equivalente per /usr/local/brs/lib/*/config/logback.xml o per il servizio inattivo, copiarlo e incollarlo nella posizione in cui il logback.xml Il file è vuoto.

Se un altro host PowerProtect Data Manager non è disponibile, contattare il supporto Dell.

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.