I'll try to recreate playbook from Linux's x64 orchestration files. ... View more

Before to follow your suggestion, i tried to launch "ansible-playbook deploy-cleanup.yml" and it had ending positive, after that i tried to relaunch "system-assesment.yml" and i got another error (never seen before), pls look below:   fatal: [deployTarget]: FAILED! => {"changed": false, "module_stderr": "Shared connection to test-interni.internal.cloudapp.net closed.\r\n", "module_stdout": "su: invalid option -- 'H'\r\n\r\nUsage:\r\n su [options] [-] [USER [arg]...]\r\n\r\nChange the effective user id and group id to that of USER.\r\nA mere - implies -l. If USER not given, assume root.\r\n\r\nOptions:\r\n -m, -p, --preserve-environment do not reset environment variables\r\n -g, --group <group> specify the primary group\r\n -G, --supp-group <group> specify a supplemental group\r\n\r\n -, -l, --login make the shell a login shell\r\n -c, --command <command> pass a single command to the shell with -c\r\n --session-command <command> pass a single command to the shell with -c\r\n and do not create a new session\r\n -f, --fast pass -f to the shell (for csh or tcsh)\r\n -s, --shell <shell> run shell if /etc/shells allows it\r\n\r\n -h, --help display this help and exit\r\n -V, --version output version information and exit\r\n\r\nFor more details see su(1).\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}   I ran all command as "root". I don't understand if it fails for the system settings corrupted or eventually modifying (weeks ago) or if is SAS's software the problem. Glad to your support, i really appreciate. 🙏 I'll try to re ... View more

sorry me too, i didn't recognize. Here command: [root@test-interni sas_viya_playbook]# ssh -C -o ControlMaster=auto -o ControlPersist=60s -o 'IdentityFile="/root/.ssh/id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -tt test-interni.internal.cloudapp.net '/bin/sh -c '"'"'sudo -H -S -n -u sas /bin/sh'"'"'' sh-4.2$ ... View more

I tried to launch the command: [root@test-interni sas_viya_playbook]# ssh -C -o ControlMaster=auto -o ControlPersist=60s -o 'IdentityFile="/root/.ssh/id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o -tt test-interni.internal.cloudapp.net '/bin/sh -c '"'"'sudo -H -S -n -u sas /bin/sh'"'"'' command-line: line 0: Bad configuration option: -tt and then i tried to launch without "-tt" option: [root@test-interni sas_viya_playbook]# ssh -C -o ControlMaster=auto -o ControlPersist=60s -o 'IdentityFile="/root/.ssh/id_rsa"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o test-interni.internal.cloudapp.net '/bin/sh -c '"'"'sudo -H -S -n -u sas /bin/sh'"'"'' command-line: line 0: Bad configuration option: test-interni.internal.cloudapp.net   ... View more

Hi, yes it does. Here below feedback:   [root@test-interni ~]# cd /opt/sas/install/sas_viya_playbook/ [root@test-interni sas_viya_playbook]# sudo -H -S -n -u sas /bin/sh sh-4.2$ ... View more

Hi, thank for your answer. Yes, it was an older version:  [root@test-interni install]# zipgrep -m1 x64 SAS_Viya_deployment_data.zip | cut -d"-" -f3 125 It's my first training installation. Here i found somenthing usuful but i didn't resolve the issue but i'm not sure is the correct way. I think a part of software is installed because i  have seen disk space increasing during the installation. /dev/mapper/data-data_lv 252G 108G 132G 46% /opt/sas   ... View more

Ok, usually i used to add into inventory.ini file the following string: deployTarget ansible_host=hostname.net ansible_user=root ansible_ssh_private_key_file=/root/.ssh/id_rsa After that i have launched system-assesment.yml without shown error and then i checked the folder for start resetting password but it doesn't existed there.   I will try again. Thanks for your time, Kind regards, M. ... View more

The original error was the folder ("saslogon") doesn't existing. Deployment si been ending positive. After deploy i got any errors. ... View more

Hi All, i've got the same error on a test machine with OS Rhel7.9 after software installation of viya 3.5. I don't have the same directory ("saslogon") indicated in this post. postgre service is UP: postgresql.service - PostgreSQL database server Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2023-10-18 07:22:35 UTC; 2h 36min ago Process: 1067 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS) Process: 1047 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=0/SUCCESS) Main PID: 1292 (postgres) CGroup: /system.slice/postgresql.service ├─1292 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432 ├─1381 postgres: logger process ├─1461 postgres: checkpointer process ├─1462 postgres: writer process ├─1463 postgres: wal writer process ├─1464 postgres: autovacuum launcher process └─1465 postgres: stats collector process Viya services are also UP but i have only theese below instead of those products present on licence.txt (more than this below): sas-viya-cascontroller-default up N/A N/A 1983 sas-viya-connect-default up N/A N/A 1821 sas-viya-spawner-default up N/A N/A 1635 sas-viya-sasstudio-default up N/A N/A 2332 Can anyone help me to solve theese two issues? Thx in advance ... View more