PowerProtect: VMware-tjenesten kan ikke starte.
Riepilogo: På PowerProtect Data Manager-serveren kan en tjeneste med navnet vmware-service ikke starte.
Questo articolo si applica a
Questo articolo non si applica a
Questo articolo non è legato a un prodotto specifico.
Non tutte le versioni del prodotto sono identificate in questo articolo.
Sintomi
Broadcom vCenter/vSphere-relaterede handlinger påvirkes på grund af navngivne tjeneste vcenter-service kan ikke starte på PowerProtect Data Manager-serveren.
# vmware-service start
Starting...
Failed to start Please check log file: /var/log/brs/vmware-service/vmware-service.out
Logfil til vmware-service på PowerProtect Data Manager-tjenesten har hændelse, der ligner følgende, rapporteret i den:
HH:MM:SS.mss [main] INFO c.e.b.v.s.treeview.DatabaseService - Backing up database ... Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... ERROR SpringApplication Application run failed java.lang.IllegalStateException: java.io.FileNotFoundException: config/application.yml (Permission denied) at org.springframework.beans.factory.config.YamlProcessor.handleProcessError(YamlProcessor.java:222) at org.springframework.beans.factory.config.YamlProcessor.process(YamlProcessor.java:214) at org.springframework.beans.factory.config.YamlProcessor.process(YamlProcessor.java:166) at org.springframework.boot.env.OriginTrackedYamlLoader.load(OriginTrackedYamlLoader.java:84) at org.springframework.boot.env.YamlPropertySourceLoader.load(YamlPropertySourceLoader.java:50) at org.springframework.boot.context.config.StandardConfigDataLoader.load(StandardConfigDataLoader.java:54) at org.springframework.boot.context.config.StandardConfigDataLoader.load(StandardConfigDataLoader.java:36) at org.springframework.boot.context.config.ConfigDataLoaders.load(ConfigDataLoaders.java:96) at org.springframework.boot.context.config.ConfigDataImporter.load(ConfigDataImporter.java:132) at org.springframework.boot.context.config.ConfigDataImporter.resolveAndLoad(ConfigDataImporter.java:87) at org.springframework.boot.context.config.ConfigDataEnvironmentContributors.withProcessedImports(ConfigDataEnvironmentContributors.java:115) at org.springframework.boot.context.config.ConfigDataEnvironment.processInitial(ConfigDataEnvironment.java:242) at org.springframework.boot.context.config.ConfigDataEnvironment.processAndApply(ConfigDataEnvironment.java:229) at org.springframework.boot.context.config.ConfigDataEnvironmentPostProcessor.postProcessEnvironment(ConfigDataEnvironmentPostProcessor.java:96) at org.springframework.boot.context.config.ConfigDataEnvironmentPostProcessor.postProcessEnvironment(ConfigDataEnvironmentPostProcessor.java:89) at org.springframework.boot.env.EnvironmentPostProcessorApplicationListener.onApplicationEnvironmentPreparedEvent(EnvironmentPostProcessorApplicationListener.java:109) at org.springframework.boot.env.EnvironmentPostProcessorApplicationListener.onApplicationEvent(EnvironmentPostProcessorApplicationListener.java:94) at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:174) at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:167) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:145) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:133) at org.springframework.boot.context.event.EventPublishingRunListener.multicastInitialEvent(EventPublishingRunListener.java:136) at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:81) at org.springframework.boot.SpringApplicationRunListeners.lambda$environmentPrepared$2(SpringApplicationRunListeners.java:64) at java.base/java.lang.Iterable.forEach(Iterable.java:75) at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:118) at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:112) at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:63) at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:361) at org.springframework.boot.SpringApplication.run(SpringApplication.java:320) at org.springframework.boot.SpringApplication.run(SpringApplication.java:1327) at org.springframework.boot.SpringApplication.run(SpringApplication.java:1316) at com.emc.brs.vmwareservice.application.VmwareServiceApp.main(VmwareServiceApp.java:58) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) at org.springframework.boot.loader.Launcher.launch(Launcher.java:107) at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) at org.springframework.boot.loader.thin.ThinJarLauncher.launch(ThinJarLauncher.java:195) at org.springframework.boot.loader.thin.ThinJarLauncher.main(ThinJarLauncher.java:141) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at org.springframework.boot.loader.wrapper.ThinJarWrapper.launch(ThinJarWrapper.java:139) at org.springframework.boot.loader.wrapper.ThinJarWrapper.main(ThinJarWrapper.java:107) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at com.emc.brs.ThinJarLauncher.directlyRun(ThinJarLauncher.java:33) at com.emc.brs.ThinJarLauncher.main(ThinJarLauncher.java:19) Caused by: java.io.FileNotFoundException: config/application.yml (Permission denied) at java.base/java.io.FileInputStream.open0(Native Method) at java.base/java.io.FileInputStream.open(FileInputStream.java:216) at java.base/java.io.FileInputStream.(FileInputStream.java:157) at java.base/java.io.FileInputStream.(FileInputStream.java:111) at java.base/sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:86) at java.base/sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:189) at org.springframework.core.io.UrlResource.getInputStream(UrlResource.java:231) at org.springframework.boot.origin.OriginTrackedResource.getInputStream(OriginTrackedResource.java:61) at org.springframework.beans.factory.config.YamlProcessor.process(YamlProcessor.java:198) ... 52 moreCausa
Tilladelser til "/usr/local/brs/lib/vmware-service/config/application.config" filen er ikke korrekt. Denne fil findes som standard ikke. Når filen oprettes for at foretage brugerdefinerede konfigurationsændringer, angives tilladelser og ejerskab af filen ikke korrekt.
Risoluzione
Følgende trin kan følges for at løse problemet:
- Log på PowerProtect Data Manager-serveren via administratorkontoen .
- Skift mappe til
"/usr/local/brs/lib/vmware-service/config/"cd /usr/local/brs/lib/vmware-service/config/ - Kontrollér tilladelserne til
application.configFil. - Hvis ikonet
application.cofigFilen er ikke nødvendig til nogen brugerdefineret konfiguration, den kan flyttes ud fra denne mappe. - Hvis denne fil er nødvendig til visse brugerdefinerede konfigurationsindstillinger, skal du bruge følgende kommandoer til at angive forventede tilladelser og ejerskab.
sudo chown admin:app application.yml sudo chmod 750 application.yml - Start
vmware-service.vmware-service start
Prodotti interessati
PowerProtect Data Manager Appliance, PowerProtect Data Manager, PowerProtect Data Manager EssentialsProprietà dell'articolo
Numero articolo: 000394493
Tipo di articolo: Solution
Ultima modifica: 24 dic 2025
Versione: 1
Trova risposta alle tue domande dagli altri utenti Dell
Support Services
Verifica che il dispositivo sia coperto dai Servizi di supporto.