Please run these two commands on your deployment target and show me the output:
ls -ld /tmp ls -ld /tmp/.root.ansible/
Here you are:
Thank you very much
I deleted it as you said.
I got same error than before... "failed to create remote module tmp...."
there are no results for that command...
What about "mount"?
[user@sas ~]$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=41650460k,nr_inodes=10412615,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,seclabel,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,memory)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,cpuacct,cpu)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,hugetlb)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,net_prio,net_cls)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,pids)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,devices)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mapper/rhel-root on / type xfs (rw,relatime,seclabel,attr2,inode64,noquota)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel)
/dev/sda1 on /boot type xfs (rw,relatime,seclabel,attr2,inode64,noquota)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run/user/42 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=8333500k,mode=700,uid=42,gid=42)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=8333500k,mode=700)
gvfsd-fuse on /run/user/0/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=528169)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=8333500k,mode=700,uid=1000,gid=1000)
Change the permissions on /tmp directory to 777 and delete /tmp/.root.ansible/ directory again. Will that change anything?
I got error here after new deployment try:
TASK [pgpoolc-x64_redhat_linux_6-yum : Await completion] ***********************
FAILED - RETRYING: Await completion (60 retries left).
failed: [deployTarget] (item={'_ansible_parsed': True, '_ansible_item_result': True, '_ansible_item_label': {u'SANMOUNT': u'/opt/sas/viya/config/data/sasdatasvrc', u'PCP_PORT': u'5430', u'PGPOOL_PORT': u'5431', u'SERVICE_NAME': u'postgres'}, u'ansible_job_id': u'240600225592.107704', 'failed': False, u'started': 1, 'changed': True, 'item': {u'SANMOUNT': u'/opt/sas/viya/config/data/sasdatasvrc', u'PCP_PORT': u'5430', u'PGPOOL_PORT': u'5431', u'SERVICE_NAME': u'postgres'}, u'finished': 0, u'results_file': u'/root/.ansible_async/240600225592.107704', '_ansible_ignore_errors': None, '_ansible_no_log': False}) => {"ansible_job_id": "240600225592.107704", "attempts": 2, "changed": true, "cmd": ["/opt/sas/viya/home/libexec/sasdatasvrc/script/sds_setup_pool.sh", "-config_path", "/opt/sas/viya/config/etc/sasdatasvrc/postgres/pgpool0/sds_env_var.sh"], "delta": "0:00:11.048952", "end": "2019-09-30 18:18:39.150065", "finished": 1, "item": {"ansible_job_id": "240600225592.107704", "changed": true, "failed": false, "finished": 0, "item": {"PCP_PORT": "5430", "PGPOOL_PORT": "5431", "SANMOUNT": "/opt/sas/viya/config/data/sasdatasvrc", "SERVICE_NAME": "postgres"}, "results_file": "/root/.ansible_async/240600225592.107704", "started": 1}, "msg": "non-zero return code", "rc": 1, "start": "2019-09-30 18:18:28.101113", "stderr": "level=warn app=sas-crypto-management timestamp=2019-09-30T16:18:31.863683702Z function=old_commands.UpdateFlagsAndCallActionGenerateCertificate msg=\"req-vault-cert is deprecated. Use certificate generate instead.\"\nlevel=warn app=sas-crypto-management timestamp=2019-09-30T16:18:31.897725157Z function=certificate.GenerateVaultCertificateWithCSR msg=\"passphrase not provided, will not encrypt private key\"\nError: Unable to perform the ssh key validation. Until the \"sas\" user can ssh from the \"localhost\" machine to the \"sas.tecdesoft.es\" machine, this setup will continue to fail.\n/opt/sas/viya/home/libexec/sasdatasvrc/script/sds_pool_config.sh ERROR: /opt/sas/viya/home/libexec/sasdatasvrc/script/sds_ssh_key_validation.sh \"sas.tecdesoft.es sas.tecdesoft.es\" failed. Terminating deployment...\nConfiguration of pool failed", "stderr_lines": ["level=warn app=sas-crypto-management timestamp=2019-09-30T16:18:31.863683702Z function=old_commands.UpdateFlagsAndCallActionGenerateCertificate msg=\"req-vault-cert is deprecated. Use certificate generate instead.\"", "level=warn app=sas-crypto-management timestamp=2019-09-30T16:18:31.897725157Z function=certificate.GenerateVaultCertificateWithCSR msg=\"passphrase not provided, will not encrypt private key\"", "Error: Unable to perform the ssh key validation. Until the \"sas\" user can ssh from the \"localhost\" machine to the \"sas.tecdesoft.es\" machine, this setup will continue to fail.", "/opt/sas/viya/home/libexec/sasdatasvrc/script/sds_pool_config.sh ERROR: /opt/sas/viya/home/libexec/sasdatasvrc/script/sds_ssh_key_validation.sh \"sas.tecdesoft.es sas.tecdesoft.es\" failed. Terminating deployment...", "Configuration of pool failed"], "stdout": "Started setup of SDS Postgres pool\nCalling sds_set_env_variable.sh...\n CONSUL_HTTP_ADDR=https://localhost:8501\n CONSUL_TEMPLATE_OPTIONS=-consul-addr localhost:8501 -consul-ssl -consul-ssl-ca-cert /opt/sas/viya/config/etc/SASSecurityCertificateFramework/cacerts/trustedcerts.pem\nel modo de «/opt/sas/viya/config/etc/sasdatasvrc/postgres/pgpool0» cambia de 0755 (rwxr-xr-x) a 0700 (rwx------)\nel modo de «/opt/sas/viya/config/data/sasdatasvrc/postgres/pgpool0» cambia de 0755 (rwxr-xr-x) a 0700 (rwx------)\nel modo de «/opt/sas/viya/config/var/log/sasdatasvrc/postgres/pgpool0» cambia de 0755 (rwxr-xr-x) a 0750 (rwxr-x---)\n f_output_consul_short_service output:\n \"serviceAddress\": \"sas.tecdesoft.es\",\n \"serviceID\": \"postgres-datanode0\",\n \"servicePort\": 5432,\n \"primary\"\n\nCalling sds_pool_config.sh...", "stdout_lines": ["Started setup of SDS Postgres pool", "Calling sds_set_env_variable.sh...", " CONSUL_HTTP_ADDR=https://localhost:8501", " CONSUL_TEMPLATE_OPTIONS=-consul-addr localhost:8501 -consul-ssl -consul-ssl-ca-cert /opt/sas/viya/config/etc/SASSecurityCertificateFramework/cacerts/trustedcerts.pem", "el modo de «/opt/sas/viya/config/etc/sasdatasvrc/postgres/pgpool0» cambia de 0755 (rwxr-xr-x) a 0700 (rwx------)", "el modo de «/opt/sas/viya/config/data/sasdatasvrc/postgres/pgpool0» cambia de 0755 (rwxr-xr-x) a 0700 (rwx------)", "el modo de «/opt/sas/viya/config/var/log/sasdatasvrc/postgres/pgpool0» cambia de 0755 (rwxr-xr-x) a 0750 (rwxr-x---)", " f_output_consul_short_service output:", " \"serviceAddress\": \"sas.tecdesoft.es\",", " \"serviceID\": \"postgres-datanode0\",", " \"servicePort\": 5432,", " \"primary\"", "", "Calling sds_pool_config.sh..."]}
NO MORE HOSTS LEFT *************************************************************
PLAY RECAP *********************************************************************
Error: Unable to perform the ssh key validation. Until the \"sas\" user can ssh from the \"localhost\" machine to the \"sas.tecdesoft.es\" machine, this setup will continue to fail.
How did you create a SAS user? Manually or automatically? Either that user got locked or his SSH keys broked down on your deployment target machine.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.