Avamar 19.7: O PDM falha com o erro 404 após o devido upgrade, as preferências.dtd estão incorretas

Summary: Após o upgrade para a versão 19.7, o Proxy Deployment Manager (PDM) falha com um erro 404 devido a permissões incorretas no arquivo preferences.dtd.

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

Após o upgrade para a versão 19.7, o PDM falha, com a mensagem:

Error while fetching tasks. Failed with HTTP error code: 404 additional information
HTTP Status 404 - Not Found.


Error while fetching tasks

Cause

Esse erro pode estar associado a permissões incorretas no arquivo:

/usr/local/avamar/var/mc/server_data/prefs/preferences.dtd


Confirme o problema verificando o connectionmanger.log e o deploymanager.log

Connectionmanager.log é mostrado abaixo.
 

2023-01-18T15:41:57.410+0000 INFO  [ost-startStop-1][util.MCCipherUtil#getDocument]: getDocument: mcserverXMLFile:/usr/local/avamar/var/mc/server_data/prefs/mcserver.xml
2023-01-18T15:41:57.412+0000 ERROR [ost-startStop-1][util.MCCipherUtil#getDocument]: getDocument fail: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:41:57.412+0000 ERROR [ost-startStop-1][   util.MCCipherUtil#cryptValueByXPath]: Decrypt failed at: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:41:57.412+0000 ERROR [ost-startStop-1][util.MCCipherUtil#   getResultValue]: Error found for decrypt: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:41:57.413+0000 ERROR [ost-startStop-1][             util.RabbitMQUtil#ConnectionFactory]: getConnectionFactory Exception====
2023-01-18T15:41:57.413+0000 ERROR [ost-startStop-1][             util.RabbitMQUtil#ConnectionFactory]: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:41:57.413+0000 INFO  [ost-startStop-1][             util.RabbitMQUtil#ConnectionFactory]: cf.isSSL():false

 

O seguinte é visto no final de Deploymanager.log. 
2023-01-18T15:42:03.262+0000 INFO  [ost-startStop-1][util.MCCipherUtil#   getResultValue]: getResultValue:rabbitmqAP
2023-01-18T15:42:03.262+0000 INFO  [ost-startStop-1][             util.MCCipherUtil#cryptValueByXPath]: xPath://entry[@key='rabbitmqAP']
2023-01-18T15:42:03.263+0000 INFO  [ost-startStop-1][util.MCCipherUtil#      getDocument]: getDocument: mcserverXMLFile:/usr/local/avamar/var/mc/server_data/prefs/mcserver.xml
2023-01-18T15:42:03.265+0000 ERROR [ost-startStop-1][             util.MCCipherUtil#      getDocument]: getDocument fail: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:42:03.265+0000 ERROR [ost-startStop-1][             util.MCCipherUtil#cryptValueByXPath]: Decrypt failed at: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:42:03.265+0000 ERROR [ost-startStop-1][             util.MCCipherUtil#   getResultValue]: Error found for decrypt: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)
2023-01-18T15:42:03.266+0000 ERROR [ost-startStop-1][             util.RabbitMQUtil#ConnectionFactory]: getConnectionFactory Exception====
2023-01-18T15:42:03.266+0000 ERROR [ost-startStop-1][             util.RabbitMQUtil#ConnectionFactory]: /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd (Permission denied)

Resolution

1. No Avamar como raiz, verifique as permissões de arquivo:

ls -ltrh /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd

O resultado fica assim:

-r-------- 1 admin admin 4.5K /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd

2. Alterar as permissões do preferences.dtd.

chmod 444 /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd

As permissões de arquivo agora ficam assim:

 r--r--r-- 1 admin admin 4.5K /usr/local/avamar/var/mc/server_data/prefs/preferences.dtd

3: Certifique-se de que nenhum backup esteja em execução e reinicie o serviço Tomcat:

emwebapp.sh --restart


Agora, o Proxy Deployment Manager pode ser usado para implementar proxies novamente.
Se os proxies não foram implementados recentemente, não haverá nenhuma opção para atualizá-los no PDM.
Implemente-os manualmente e exclua os proxies antigos.

Artigos relacionados:
Avamar: O Proxy Deployment Manager (PDM) falha imediatamente, com a mensagem: "Error while fetching tasks. Failed with HTTP error code:404 additional information" HTTP Status 404 - Not Found

Article Properties
Article Number: 000208959
Article Type: Solution
Last Modified: 10 Jun 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.