Do not see sasboot password reset code in /var/log/sas/viya/saslogon/default/sas-saslogon_*.log

[sasdol]

Hi,

Continuing on my previous posts, SAS Viya 3.5 deployment on Red Hat 8 completed with one error for sas-viya-rabbitmq-server-default; but, that service is active(running) after a restart following deployment.

For the next steps in the Post-installation task, I am following SAS Help Center: Configure Security and have changed the administrative user password for SAS Message Broker. 

Next, trying to reset pasword for sasboot; however, I do not see the password reset code in the log file /var/log/sas/viya/saslogon/default/sas-saslogon_*.log. Have tried to restart sas-viya-saslogon-default 2-3 times as well as restarted all services (using sudo /etc/init.d/sas-viya-all-services stop & start) but no difference. Any suggestion?

Thank you.

=============See following message many times in /var/log/sas/viya/saslogon/default/sas-saslogon_*.log (though it is appearing as INFO so not sure if it is relevant or not)

2022-05-07 22:07:22.149 INFO 298097 --- [ main] c.s.c.r.boot.initialization.test.Jdbc : service [JDBC_NODATABASE_REGISTRY_FOUND] Database service name 'postgres' not found in Consul service registry.
2022-05-07 22:07:32.074 INFO 298097 --- [ Timer-0] c.r.b.i.SasApplicationContextInitializer : service [INITIALIZER_CONSUL_PROPERTY_SOURCES_INITIALIZED] All consul property sources have been initialized.

[gwootton]

SASLogon relies on the SAS Infrastructure Data Server postgres database to be up and running, so it will ask consul for the connection information to postgres repeatedly before proceeding. It sounds like your postgres is not up so SASLogon never gets past that point, where it provides the link to reset the sasboot password.

SAS Infrastructure Data Server
https://go.documentation.sas.com/doc/en/calcdc/3.5/calsrvinf/n00000sasinfrdatasrv000admin.htm

[sasdol]

Thank you for replying @gwootton .

I don't see any of following directories/scripts as referenced in SAS Help Center: SAS Infrastructure Data Server.

/opt/sas/viya/config/data/sasdatasvrc/

/etc/init.d/sas-viya-sasdatasvrc*

# ls -ltr /opt/sas/viya/config/data/ | grep data
drwxr-x--- 2 sas sas 4096 Sep 10 2021 dmdataservices
drwxr-x--- 2 sas sas 4096 Sep 10 2021 dataplans
drwxr-x--- 2 sas sas 4096 Sep 10 2021 datastudio
drwxr-x--- 2 sas sas 4096 Sep 15 2021 dataexplorer
drwxr-x--- 2 sas sas 4096 Jan 6 16:15 web-data-access
drwxr-x--- 2 sas sas 4096 Jan 21 10:08 report-data
drwxr-x--- 2 sas sas 4096 Feb 1 15:10 dataprofiles

# ls -ltr /etc/init.d/ | grep data
-rwxr-xr-x 1 sas sas 6617 Sep 10 2021 sas-viya-dmdataservices-default
-rwxr-xr-x 1 sas sas 6546 Sep 10 2021 sas-viya-dataplans-default
-rwxr-xr-x 1 sas sas 6564 Sep 10 2021 sas-viya-datastudio-default
-rwxr-xr-x 1 sas sas 6582 Sep 15 2021 sas-viya-dataexplorer-default
-rwxr-xr-x 1 sas sas 6594 Jan 6 16:15 sas-viya-web-data-access-default
-rwxr-xr-x 1 sas sas 6561 Jan 21 10:08 sas-viya-report-data-default
-rwxr-xr-x 1 sas sas 6573 Feb 1 15:10 sas-viya-dataprofiles-default

Seems that might be because the document is still referring to old version of PostgreSQL whereas I see service named sas-postgresql11

[root@sildevdeapetan05 avipani]# ls -ltr /etc/init.d/*post*
-rwxr-xr-x 1 sas sas 6545 Dec 1 16:40 /etc/init.d/sas-postgresql11

[root@sildevdeapetan05 avipani]# /etc/init.d/sas-postgresql11 status
● sas-postgresql11.service - LSB: start and stop PostgreSQL server
Loaded: loaded (/etc/rc.d/init.d/sas-postgresql11; generated)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)

# ls -ltr /opt/sas/viya/config/var/log/sasdatasvrc
ls: cannot access '/opt/sas/viya/config/var/log/sasdatasvrc': No such file or directory

[root@sildevdeapetan05 avipani]# /etc/init.d/sas-postgresql11 start
Starting sas-postgresql11 (via systemctl): Job for sas-postgresql11.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status sas-postgresql11.service" and "journalctl -xe" for details.
[FAILED]
[root@sildevdeapetan05 avipani]# systemctl status sas-postgresql11.service
● sas-postgresql11.service - LSB: start and stop PostgreSQL server
Loaded: loaded (/etc/rc.d/init.d/sas-postgresql11; generated)
Active: failed (Result: protocol) since Mon 2022-05-09 11:59:48 EDT; 19s ago
Docs: man:systemd-sysv-generator(8)
Process: 2548652 ExecStart=/etc/rc.d/init.d/sas-postgresql11 start (code=exited, status=5)

May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: Starting LSB: start and stop PostgreSQL server...
May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: sas-postgresql11.service: Can't open PID file /var/run/postmaster.5432.>
May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: sas-postgresql11.service: Failed with result 'protocol'.
May 09 11:59:48 sildevdeapetan05.dol.gov systemd[1]: Failed to start LSB: start and stop PostgreSQL server.
lines 1-10/10 (END)

[gwootton]

It sounds like you may not have successfully completed the installation and configuration of postgres.

The /etc/init.d/sas-postgres11 one of several scripts in that path, but you would use the scripts to start them as you need to start up pgpool as well:

$ ls -ltr /etc/rc.d/init.d | grep -E '(postgres|pool|datasvr)'
-rwxr-xr-x. 1 sas sas 6543 Sep 20 2019 sas-postgresql11
-rwxr-xr-x. 1 sas sas 3854 Sep 20 2019 sas-pgpool-II40
-rwxr-xr-x. 1 root root 2248 Nov 22 2019 sas-viya-sasdatasvrc-postgres-node0-consul-template-operation_node
-rwxr-xr-x. 1 root root 3144 Nov 22 2019 sas-viya-sasdatasvrc-postgres-node0
-rwxr-xr-x. 1 root root 2200 Nov 22 2019 sas-viya-sasdatasvrc-postgres-node0-consul-template-pg_hba
-rwxr-xr-x. 1 root root 2266 Nov 22 2019 sas-viya-sasdatasvrc-postgres-pgpool0-consul-template-operation_node
-rwxr-xr-x. 1 root root 2849 Nov 22 2019 sas-viya-sasdatasvrc-postgres-pgpool0
-rwxr-xr-x. 1 root root 2230 Nov 22 2019 sas-viya-sasdatasvrc-postgres-pgpool0-consul-template-pool_hba

$ ls -ltr /opt/sas/viya/config/data/sasdatasvrc/postgres/
total 8
drwx------. 19 sas sas 4096 May 9 05:32 node0
drwx------. 3 sas sas 4096 May 9 05:33 pgpool0

[sasdol]

@gwootton 

Do I need to install PostgreSQL as a prereq before running the ansible playbook site.yml for deployment or the playbook will install and configure it?

Thank you.

[gwootton]

No, this is installed and configured as part of the ansible playbook site.yml.

[sasdol]

Thank you @gwootton ... have gone through the deployment process 3 times, each time going through the pre-installation tasks to ensure not missing any pre-req items. Also, didn't notice any specific step for PostgreSQL installation and configuration. All 3 times it failed with only one error (or that's the only one I noticed) related to rabbitmq and that too the service comes up without any error on first restart after setting the admin password. So, not sure what should I do differently... any hint? 

======= 

        "Tue Apr 26 19:01:58 EDT 2022 setup_rabbit_cluster Starting sas-viya-rabbitmq-server-default",

        "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster The RabbitMQ service sas-viya-rabbitmq-server-default could not be started.",

        "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster Returned status was 1",

        "Tue Apr 26 19:03:04 EDT 2022 setup_rabbit_cluster Setup failed. Beware of independent Rabbit hosts running with different shared secrets."

    ]

}

NO MORE HOSTS LEFT ************************************************************************************************************************************************************

PLAY RECAP ********************************************************************************************************************************************************************

deployTarget               : ok=369  changed=136  unreachable=0    failed=1    skipped=853  rescued=0    ignored=0

localhost                  : ok=12   changed=2    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0

================== after changing admin password and restarting all services 

sas_viya_playbook]# systemctl status sas-viya-rabbitmq-server-default
● sas-viya-rabbitmq-server-default.service - LSB: start and stop sas-rabbitmq-server server
Loaded: loaded (/etc/rc.d/init.d/sas-viya-rabbitmq-server-default; generated)
Active: active (running) since Sun 2022-05-01 22:46:13 EDT; 1 day 19h ago
Docs: man:systemd-sysv-generator(8)
Process: 91371 ExecStop=/etc/rc.d/init.d/sas-viya-rabbitmq-server-default stop (code=exited, status=0/SUCCESS)
Process: 94438 ExecStart=/etc/rc.d/init.d/sas-viya-rabbitmq-server-default start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 410046)
Memory: 1.6M
CGroup: /system.slice/sas-viya-rabbitmq-server-default.service
└─16408 /bin/bash /opt/sas/viya/home/sbin/rabbitmq-server

May 01 22:44:40 sildevdeapetan05.dol.gov su[94928]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:45:22 sildevdeapetan05.dol.gov sas-viya-rabbitmq-server-default[94438]: sas-viya-rabbitmq-server-default service is registered
May 01 22:45:36 sildevdeapetan05.dol.gov su[98503]: (to sasrabbitmq) root on none
May 01 22:45:36 sildevdeapetan05.dol.gov su[98503]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:45:37 sildevdeapetan05.dol.gov su[98575]: (to sasrabbitmq) root on none
May 01 22:45:37 sildevdeapetan05.dol.gov su[98575]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:45:59 sildevdeapetan05.dol.gov su[99775]: (to sasrabbitmq) root on none
May 01 22:45:59 sildevdeapetan05.dol.gov su[99775]: pam_unix(su-l:session): session opened for user sasrabbitmq by (uid=0)
May 01 22:46:13 sildevdeapetan05.dol.gov sas-viya-rabbitmq-server-default[94438]: sas-viya-rabbitmq-server-default service is started
May 01 22:46:13 sildevdeapetan05.dol.gov systemd[1]: Started LSB: start and stop sas-rabbitmq-server server.
[sas_viya_playbook]#

======= all data related services are down

sas-viya-dataplans-default down N/A N/A N/A
sas-viya-report-data-default down N/A N/A N/A
sas-viya-web-data-access-default down N/A N/A N/A
sas-viya-dataexplorer-default down N/A N/A N/A
sas-viya-dataprofiles-default down N/A N/A N/A
sas-viya-datastudio-default down N/A N/A N/A
sas-viya-dmdataservices-default down N/A N/A N/A

================ ports open

[sas_viya_playbook]# netstat -ntpl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 10.50.12.103:50846 0.0.0.0:* LISTEN 28358/java
tcp 0 0 10.50.12.103:10334 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:40799 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:43139 0.0.0.0:* LISTEN 15722/objspawn
tcp 0 0 0.0.0.0:5671 0.0.0.0:* LISTEN 17075/beam.smp
tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN 1933/snmpd
tcp 0 0 10.50.12.103:47816 0.0.0.0:* LISTEN 28358/java
tcp 0 0 0.0.0.0:25672 0.0.0.0:* LISTEN 17075/beam.smp
tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 10921/vault
tcp 0 0 0.0.0.0:8201 0.0.0.0:* LISTEN 10921/vault
tcp 0 0 0.0.0.0:14443 0.0.0.0:* LISTEN 28358/java
tcp 0 0 0.0.0.0:8300 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 0.0.0.0:8301 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 10.50.12.103:56431 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:8591 0.0.0.0:* LISTEN 15722/objspawn
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 14117/httpd
tcp 0 0 127.0.0.1:43473 0.0.0.0:* LISTEN 15722/objspawn
tcp 0 0 0.0.0.0:4369 0.0.0.0:* LISTEN 15110/epmd
tcp 0 0 10.50.12.103:59570 0.0.0.0:* LISTEN 28357/java
tcp 0 0 0.0.0.0:37459 0.0.0.0:* LISTEN 28358/java
tcp 0 0 0.0.0.0:8500 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 0.0.0.0:8501 0.0.0.0:* LISTEN 8542/consul
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1922/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1939/cupsd
tcp 0 0 0.0.0.0:15672 0.0.0.0:* LISTEN 17075/beam.smp
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 4872/master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 14117/httpd
[sas_viya_playbook]#

[gwootton]

I suspect your deployment is failing at rabbitmq and stopping (skipped=853) before postgres gets deployed. My deployment lines look like this in my deployment.log (no skipped):

2019-11-22 17:14:53,118 p=15130 u=cloud-user | deployTarget : ok=1442 changed=819 unreachable=0 failed=0
2019-11-22 17:14:53,118 p=15130 u=cloud-user | localhost : ok=14 changed=1 unreachable=0 failed=0

You'll need your install to complete before you can go on to anything else.

[sasdol]

Thank you @gwootton . Sincerely appreciate your help.

[teolly]

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

[gwootton]

What error are you encountering? The setup failure of rabbitmq during deployment, or was it another service? It doesn't look like you have the rabbitmq service deployed yet.

[teolly]

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

[gwootton]

Sounds like an issue with your inventory.ini file not specifying a host for all of the components. By default this file specifies the different components with deployTarget under it. If that was removed from some of the components, they would not get deployed. I suspect you will need to deploy again after correcting your inventory.ini file.

[teolly]

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.