08-27-2014 07:09 AM
Error in validating pooled workspace which in turn affects the reports in the IDP portal.
Unable to fetch the reports which shows the same error. Expecting this to be an error with pooled worksapce error or something related to ports utilisation.
Could anyone please help me with this.Appreciate your response.
08-27-2014 10:31 AM
any log information?
any steps done in SMC?
Verified Object spawner restarted after changes.
The non personal account like sassrv is correct etc etc.
Checked metadataserver logs?
Verified the check on the service using SMC?
09-01-2014 07:30 AM
The Error states "Failed to start the server".
Over SMC tried validating Stored process server, Workspace server , but unable to validate.For Stored process server validation the error shown is "The Load balancing Object Spawner timed out". and for Workspace server and pooled workspace server the error is "Failed to restart the server".
Object spawner is up but the sassrv process are not available with the Unix boxes.
Is there a need to go for a retstart of Object spwaner which in turn may help in restarting Workspace and pooled workspace server. or is there any other options available without restart?
09-01-2014 07:54 AM
The validation with SMC is telling you there is something wrong.
There must be logs having more information the metadata server log is the one to start at.
The object spawner log must have the same errors as you have experienced but should have some additional information.
The sassrv account should be an operational Unix account capable of running the sas processes.
- The password could be configured wrong. If you are ale to verify that...
SAS(R) 9.4 Intelligence Platform: Installation and Configuration Guide ( Troubleshooting the SAS Server Tier)
39891 - Using PROC PERMTEST to diagnose UNIX host authentication issues in SAS® 9.2 and later releas...
- In the metadata server log you should find the objectspawner has read those.
The objectspawner can be started to early and the metadataserver does not react or come changes have been made on the metadataserver sassrv/application server(s).
A restart of the object-spawner is necessary. (since 9.3 in SMC)
Not all metadata settings are allowed for all users.
- the sasauth, sasperm modules are configured not correctly. SAS(R) 9.4 Intelligence Platform: Application Server Administration Guide
09-03-2014 02:17 AM
The issue has been resolved now.
The ERROR with the pooled workspace server said "Library WORK does not exist" , which made us to check for the WORK path location , which was in turn pointing to two paths , of which one was mounted . We found the problem to be with the mount path and changed accordingly in sasv9_locale.cfg file and got it resolved.
Thanks a lot for your support. Appreciate your response
09-03-2014 02:42 AM
That is good news. And as almost always it was something not been thought of.
After the installation you can verify that part using SAS foundation with a terminal (x11) approach. There are several SAS config settings related tot the OS/hardware to get tuned well.
As you have found the SAS work as being the root cause. Rethink about this resource. With heavy loads it can be a bottleneck. Segregation by users/usage is possible.
There is an option: utilloc that is meant to segregate the sort and proc sql temporary files (#Util... namings). All for performance reasons.