SAS Viya 3.4 installation - RabbitMQ

[davidvazqueztds]

I cant believe it .... failed again:

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'32468863481.25373', '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/32468863481.25373', '_ansible_ignore_errors': None, '_ansible_no_log': False}) => {"ansible_job_id": "32468863481.25373", "attempts": 11, "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:01:35.610076", "end": "2019-09-11 17:44:01.065790", "finished": 1, "item": {"ansible_job_id": "32468863481.25373", "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/32468863481.25373", "started": 1}, "msg": "non-zero return code", "rc": 1, "start": "2019-09-11 17:42:25.455714", "stderr": "level=warn app=sas-crypto-management timestamp=2019-09-11T15:42:28.380879973Z function=old_commands.UpdateFlagsAndCallActionGenerateCertificate msg=\"req-vault-cert is deprecated. Use certificate generate instead.\"\nlevel=warn app=sas-crypto-management timestamp=2019-09-11T15:42:28.47841717Z function=certificate.GenerateVaultCertificateWithCSR msg=\"passphrase not provided, will not encrypt private key\"\nlevel=warn app=sas-crypto-management timestamp=2019-09-11T15:42:56.22115468Z function=old_commands.UpdateFlagsAndCallActionGenerateCertificate msg=\"req-vault-cert is deprecated. Use certificate generate instead.\"\nlevel=warn app=sas-crypto-management timestamp=2019-09-11T15:42:56.460280127Z function=certificate.GenerateVaultCertificateWithCSR msg=\"passphrase not provided, will not encrypt private key\"\npg_ctl: no se pudo iniciar el servidor.\nExamine el registro del servidor.\nbash: /opt/sas/viya/home/bin/pg_ctl -w -D /opt/sas/viya/config/data/sasdatasvrc/postgres/node0 start -l /opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0/pgstartup_20190911174252.log failed on sas.tecdesoft.es with error code 1\nf_pg_isready ERROR: Expired waiting time. Wait time: 60 seconds.\npgpool_setup.sh exiting with code 1 at mié sep 11 17:44:01 CEST 2019\nConfiguration of pool failed", "stderr_lines": ["level=warn app=sas-crypto-management timestamp=2019-09-11T15:42:28.380879973Z function=old_commands.UpdateFlagsAndCallActionGenerateCertificate msg=\"req-vault-cert is deprecated. Use certificate generate instead.\"", "level=warn app=sas-crypto-management timestamp=2019-09-11T15:42:28.47841717Z function=certificate.GenerateVaultCertificateWithCSR msg=\"passphrase not provided, will not encrypt private key\"", "level=warn app=sas-crypto-management timestamp=2019-09-11T15:42:56.22115468Z function=old_commands.UpdateFlagsAndCallActionGenerateCertificate msg=\"req-vault-cert is deprecated. Use certificate generate instead.\"", "level=warn app=sas-crypto-management timestamp=2019-09-11T15:42:56.460280127Z function=certificate.GenerateVaultCertificateWithCSR msg=\"passphrase not provided, will not encrypt private key\"", "pg_ctl: no se pudo iniciar el servidor.", "Examine el registro del servidor.", "bash: /opt/sas/viya/home/bin/pg_ctl -w -D /opt/sas/viya/config/data/sasdatasvrc/postgres/node0 start -l /opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0/pgstartup_20190911174252.log failed on sas.tecdesoft.es with error code 1", "f_pg_isready ERROR: Expired waiting time. Wait time: 60 seconds.", "pgpool_setup.sh exiting with code 1 at mié sep 11 17:44:01 CEST 2019", "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..."]}

[alexal]

@davidvazqueztds ,

Yes it does, but not on RabbitMQ. Show me /opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0/pgstartup_20190911174252.log, but most likely sas-crypto-management wasn't able to connect to localhost:8501. Are you sure Consul is up and running?

source /opt/sas/viya/config/consul.conf
curl -v localhost:8501

[davidvazqueztds]

[root@sas sas_viya_playbook]# source /opt/sas/viya/consul.conf
bash: /opt/sas/viya/consul.conf: No existe el fichero o el directorio (No exist)
[root@sas sas_viya_playbook]# curl -v localhost:8501
* About to connect() to localhost port 8501 (#0)
* Trying ::1...
* Connected to localhost (::1) port 8501 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: localhost:8501
> Accept: */*
>


* Connection #0 to host localhost left intact
[root@sas sas_viya_playbook]#

[root@sas sas_viya_playbook]# cat /opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0/pgstartup_20190911174252.log
LOG: saltando el archivo de configuración faltante «/some/path/user_mod.conf»
LOG: saltando el archivo de configuración faltante «/some/path/user_mod.conf»
2019-09-11 17:42:58.402 CESTFATAL: could not map anonymous shared memory: Cannot allocate memory
2019-09-11 17:42:58.402 CESTHINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 4541538304 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
[root@sas sas_viya_playbook]#

Actually I dont know if Consul is up and running. I don know exactly what Consul is... 😞

Thank you very much for your help.

[alexal]

@davidvazqueztds ,

How much RAM is available on that server?

[davidvazqueztds]

Its a Virtual Machine. It has 3 GB. Probably I need more, right?

[alexal]

@davidvazqueztds ,

Much more. Please see Baseline Hardware Requirements by Product.

[davidvazqueztds]

so... there´s no way to install it on my own laptop... so much RAM.

Thank you very much for your help.

[alexal]

@davidvazqueztds ,

Nope. 

[davidvazqueztds]

Hello,

Now I moved it to another infrastructure, which fullfil the server requeriments. I got this error running again the playbook command, so now cant be RAM and CPU problem:

ASK [sasdatasvrc-x64_redhat_linux_6-yum : Execute Node Setup] *****************
changed: [deployTarget] => (item={u'SANMOUNT': u'/opt/sas/viya/config/data/sasdatasvrc', u'NODE_TYPE': u'P', u'NODE_NUMBER': u'0', u'PG_PORT': u'5432', u'SERVICE_NAME': u'postgres'})

TASK [sasdatasvrc-x64_redhat_linux_6-yum : Await completion] *******************
FAILED - RETRYING: Await completion (60 retries left).
FAILED - RETRYING: Await completion (59 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'NODE_TYPE': u'P', u'PG_PORT': u'5432', u'SERVICE_NAME': u'postgres', u'NODE_NUMBER': u'0'}, u'ansible_job_id': u'214904346784.78075', 'failed': False, u'started': 1, 'changed': True, 'item': {u'SANMOUNT': u'/opt/sas/viya/config/data/sasdatasvrc', u'NODE_TYPE': u'P', u'PG_PORT': u'5432', u'SERVICE_NAME': u'postgres', u'NODE_NUMBER': u'0'}, u'finished': 0, u'results_file': u'/root/.ansible_async/214904346784.78075', '_ansible_ignore_errors': None, '_ansible_no_log': False}) => {"ansible_job_id": "214904346784.78075", "attempts": 3, "changed": true, "cmd": ["/opt/sas/viya/home/libexec/sasdatasvrc/script/sds_setup_node.sh", "-config_path", "/opt/sas/viya/config/etc/sasdatasvrc/postgres/node0/sds_env_var.sh"], "delta": "0:00:13.929435", "end": "2019-09-13 12:33:47.367773", "finished": 1, "item": {"ansible_job_id": "214904346784.78075", "changed": true, "failed": false, "finished": 0, "item": {"NODE_NUMBER": "0", "NODE_TYPE": "P", "PG_PORT": "5432", "SANMOUNT": "/opt/sas/viya/config/data/sasdatasvrc", "SERVICE_NAME": "postgres"}, "results_file": "/root/.ansible_async/214904346784.78075", "started": 1}, "msg": "non-zero return code", "rc": 1, "start": "2019-09-13 12:33:33.438338", "stderr": "/opt/sas/viya/home/libexec/sasdatasvrc/script/sds_setup_node.sh error executing f_shutdown_consul_template", "stderr_lines": ["/opt/sas/viya/home/libexec/sasdatasvrc/script/sds_setup_node.sh error executing f_shutdown_consul_template"], "stdout": "Started setup of SDS Postgres node\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\nSetup is running on sas.tecdesoft.es\nel modo de «/opt/sas/viya/config/etc/sasdatasvrc/postgres/node0» cambia de 0755 (rwxr-xr-x) a 0700 (rwx------)\nel modo de «/opt/sas/viya/config/data/sasdatasvrc/postgres/node0» permanece como 0700 (rwx------)\nel modo de «/opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0» permanece como 0750 (rwxr-x---)\nService sas-viya-sasdatasvrc-postgres-node0-ct-pg_hba failed to be shut down. Termiating deployment...", "stdout_lines": ["Started setup of SDS Postgres node", "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", "Setup is running on sas.tecdesoft.es", "el modo de «/opt/sas/viya/config/etc/sasdatasvrc/postgres/node0» cambia de 0755 (rwxr-xr-x) a 0700 (rwx------)", "el modo de «/opt/sas/viya/config/data/sasdatasvrc/postgres/node0» permanece como 0700 (rwx------)", "el modo de «/opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0» permanece como 0750 (rwxr-x---)", "Service sas-viya-sasdatasvrc-postgres-node0-ct-pg_hba failed to be shut down. Termiating deployment..."]}

Thank you very much.

[alexal]

@davidvazqueztds ,

Show me the most recent log files from /opt/sas/viya/config/var/log/sasdatasvrc/postgres/node0 directory.

[davidvazqueztds]

I runned cleanup and now I think it worked. No errors.

How can now run the software? Or what should I do? 

Thank you very much

[alexal]

@davidvazqueztds ,

I'm glad that the problem with the deployment has been resolved. You can now access SAS Drive, SAS Environment Manager or SAS Studio in your web-browser.

https://go.documentation.sas.com/?docsetId=dplyml0phy0lax&docsetTarget=p1ah1hdb05bhr5n10l3ncd9nlt1a....

[davidvazqueztds]

Actually, I didnt configure the reverse-proxy because I don´t know how. but I don´t know what to introduce in username and password fields. In the proxy field should I introduce sas.tecdesoft.es:8080 for example?

Thank you very much for your help!

I saw this in doc:

Forward proxy server settings for yum can be configured in /etc/yum.conf. Here is an example of the /etc/yum.conf script:

Could be configured like this?:

proxy=sas.tecdesoft.es:8080/

proxy_username=user

proxy_password=password

[alexal]

@davidvazqueztds ,

Replace reverse-proxy-server with the hostname of your SAS Viya server.

[davidvazqueztds]

Hello,

Please, find attached my new error... Cant deploy the software.

Could you help me please? thank you