how to bring a service up when died -sas viya 3.2

[AmitSri]

sas-viya-saslogon-default service started and died 3 times. After rectifying the error, How to bring up any service which is died .

[alexal]

@AmitSri,

I would like to see the most recent log file from /opt/sas/viya/config/var/log/saslogon/default.

[AmitSri]

Hi Alex,

Please find th attached latest log of saslogon.

Thanks,

Sri

[alexal]

@AmitSri,

Is this a multi-tenant environment? How did you configure LDAP authentication?

[AmitSri]

Its a single-machine deployment and we configured an OpenLdap using ansible we had set it up. Thanks!!

[alexal]

@AmitSri,

we configured an OpenLdap using ansible we had set it up

Please provide more details about what you did. Also, why have you decided not to use SAS Environment Manager for LDAP configuration?

[AmitSri]

Hi Alex, No we had not setit up now. We initially configured LDAP settings using env manager. The current scenario in our project is, our client wants us to use 3.3 version. Since, 3.2 is running fine, We had created a new vm to install 3.3 without disturbing 3.2. But, since both are using the same IP, to work on one VM, we have to bring the other vm down.And as in 3.3 we are currently facing ODBC connection issue, we had broght the 3.2 vm bak for the business perspective. When we brought the 3.2vm back, I am not sure what the admin had done on this, however all the ldapservices were not running. So he had just set it back (the all.yml file and sitedefault.yml files of OpenLdap), Then we tried starting the services and facing the current issue.

Thanks!!

[dpage]

the settings put into EV or sitedefault look like they are corrupt, it looks like placeholders have been intermingled with actual values.

Have you opened a tech support track?

[AmitSri]

Thank you for looking into it. Yes, I had raised a request at tech support on this.