Avamar 19.7: PDM smette di funzionare con errore 404 dopo l'upgrade dovuto, preferences.dtd errato

Dopo l'upgrade alla versione 19.7, PDM smette di funzionare e riporta il seguente messaggio:

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

Questo errore può essere associato ad autorizzazioni errate per il file:

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

Confermare il problema controllando il connectionmanger.log e il tasto deploymanager.log

Connectionmanager.log è mostrato di seguito.
 

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

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)

1. Su Avamar come root, controllare le autorizzazioni dei file:

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

Il risultato è simile al seguente:

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

2. Modificare le autorizzazioni di preferences.dtd.

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

Le autorizzazioni per i file sono ora simili a queste:

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

3. Verificare che non siano in esecuzione backup, quindi riavviare il servizio tomcat:

emwebapp.sh --restart

Proxy Deployment Manager può ora essere utilizzato per implementare nuovamente i proxy.
Se i proxy non sono stati implementati di recente, non sarà disponibile alcuna opzione per aggiornarli in PDM.
Implementarli manualmente ed eliminare i proxy precedenti.

Articolo della KB correlato:
Avamar: Proxy Deployment Manager (PDM) smette subito di funzionare e riporta il messaggio: "Error while fetching tasks. Failed with HTTP error code:404 additional information" HTTP Status 404 - Not Found (in inglese)