Avamar - Il flusso di lavoro di aggiornamento alla versione 19.1.0-38 non riesce restituendo l'errore: "ERROR: ERROR: undefined method `include?' for nil:NilClass" e il menu a discesa Client-Server Communication risulta vuoto

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

Aggiornamento alla versione 19.1

- Impossibile avviare l'aggiornamento alla versione 19.1 con i seguenti errori in workflow.log:
> 2020-02-20 17:18:21 (+0100) 4104240 NOTICE: Path: /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/user-input/collectors/collect_security_settings.rb > 2020-02-20 17:18:21 (+0100) 4104240 NOTICE: Collector: user-input/collectors/collect_security_settings.rb --input_name=session_ticket_setting > 2020-02-20 17:18:21 (+0100) 4104240 INFO: COLLECT CollectSecuritySettings > 2020-02-20 17:18:21 (+0100) 4104240 INFO: input_name: session_ticket_setting > 2020-02-20 17:18:21 (+0100) 4104240 INFO: >>> [make_temp_script] 222 very_current_user=root, as_user=admin, ssh command is: (openssl x509 -text -noout -in /usr/local/avamar/etc/cert.pem | grep Subject: | awk '{print $NF}') >/usr/local/avamar/var/run_command-sysout.15816.4104240 2>&1 > 2020-02-20 17:18:21 (+0100) 4104240 INFO: - - - - - - - BEGIN(output) - - - - - - - > 2020-02-20 17:18:21 (+0100) 4104240 INFO: avamar.domain.com > 2020-02-20 17:18:21 (+0100) 4104240 INFO: - - - - - - - END > 2020-02-20 17:18:21 (+0100) 4104240 INFO: "openssl x509 -text -noout -in /usr/local/avamar/etc/cert.pem | grep Subject: | awk '{print $NF}'", exit status=0 (success) > 2020-02-20 17:18:21 (+0100) 4104240 ERROR: ERROR: undefined method `include?' for nil:NilClass > 2020-02-20 17:18:21 (+0100) 4104240 DETAILS: ERROR: undefined method `include?' for nil:NilClass <NoMethodError> /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/user-input/collectors/collect_security_settings.rb:42:in `obtain_sec_settings' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/user-input/collectors/collect_security_settings.rb:134:in `<main>' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/core/0.2.0/runtime/director.rb:85:in `eval' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/core/0.2.0/runtime/director.rb:85:in `block in load_as_path' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/core/0.2.0/runtime/director.rb:152:in `handle_errors' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/core/0.2.0/runtime/director.rb:83:in `load_as_path' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/app/launch/abstract-runner.rb:22:in `block in process_item' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/app/launch/abstract-redirector.rb:59:in `with_core_director' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/app/launch/abstract-runner.rb:19:in `process_item' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/app/launch/abstract-redirector.rb:32:in `process_redirect' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/launcher:35:in `block (2 levels) in start' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/launcher:34:in `tap' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/launcher:34:in `block in start' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/launcher:32:in `tap' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/launcher:32:in `start' /space/avamar/repo/temp/AvamarUpgrade-19.1.0-38.avp_1582043624093/runtime/apps/workflow/launcher:136:in `<main>' - Nella scheda Security Settings, il menu a discesa Client-Server Communication and Authentication Type è vuoto, per cui è impossibile cliccare sul pulsante Continue.

- Se si esegue manualmente il comando, il risultato viene restituito normalmente:
admin@avamar:/usr/local/avamar/etc/>: openssl x509 -text -noout -in /usr/local/avamar/etc/cert.pem | grep Subject: | awk '{print $NF}' avamar.domain.com 
- Le autorizzazioni delle directory repo e avamar risultano corrette:
admin@avamar:~/>: ls -altk /space/avamar/repo/ total 28 drwxr-xr-x 3 avi avi 4 Feb 20 17:15 temp drwxr-xr-x 3 avi avi 4 Feb 18 16:54 help drwxr-xr-x 7 avi avi 4 Feb 18 16:51 . drwxr-xr-x 2 avi avi 4 Feb 18 16:51 packages drwxr-xr-x 2 avi avi 4 Jan 21 11:57 uploads drwxrwxr-x 7 admin admin 4 Dec 7 2018 .. drwxr-xr-x 2 avi avi 4 Dec 15 2017 downloads admin@avamar:~/>: ls -altk /space/avamar/ total 28 drwxr-xr-x 23 admin admin 4 Feb 20 17:15 var drwxr-xr-x 7 avi avi 4 Feb 18 16:51 repo drwxr-xr-x 6 admin admin 4 Feb 18 15:21 src drwxr-xr-x 2 admin admin 4 Jan 20 16:55 doc drwxrwxr-x 7 admin admin 4 Dec 7 2018 . drwxr-xr-x 2 root root 4 Dec 7 2018 backup drwxr-xr-x 6 root root 4 Dec 7 2018 .. 
 

Cause

Problema di analisi dei nomi comuni quando si utilizza l'utility Openssl nel flusso di lavoro.

Resolution

Soluzione alternativa: fare riferimento al team Avamar L2 presentando una Peer Review per facilitare l'avvio del flusso di lavoro.
Soluzione definitiva: questo codice è stato migliorato nella versione 19.2 per risolvere il problema.

Affected Products

Avamar

Products

Avamar, Avamar Server
Article Properties
Article Number: 000059134
Article Type: Solution
Last Modified: 11 Dec 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.