12-04-2017 03:19 AM
12-04-2017 03:50 AM
for my own info: do you have SAS Token Authentication on the Workspace Server? With sassrv? Have you checked permissions on the SAS metadata for SAS General Servers account and in the OS folders for the sassrv account?
Did you checked your umask configurations? http://support.sas.com/kb/38/040.html
12-04-2017 04:22 AM
I'd like to sask uoy some question!
1. Is sas envirentment manager agent is related to below error?? (because it is not UP).
2. I have just restart sas.service stop/start sas service, I can logon logical workspace servser, Why??? But sometimes I met above error.
3. how to "checked permissions on the SAS metadata for SAS General Servers account and in the OS folders for the sassrv account"???
Thanks so much!
12-04-2017 04:35 AM
12-04-2017 04:47 AM
12-04-2017 04:52 AM
in config/Lev1/ObjectSpawner/Logs and config/Lev1/WorkspaceServer/Logs if you have not set up single log directories, or the logs directory.
As previously mentioned, for the Workspace Server, you would need to enable logs, at least temporary, as on the URL link previously shared/
12-04-2017 10:12 PM
I have fixed this abow error following your instruction, everythings is OK, But after some hours The old error was launch.
I think that we didn't still fix all errors related to it, I have sent logs of workspace server, stored process, spawner and error image as attached file.
Please see again and help to me to fix them!
Thanks so much.
12-04-2017 10:56 PM
It's seems that It is here: "ERROR: No disk space is available for the write operation. Filename = /tmp/SAS_util00010091005C_zvneanprd02/ut005C000003.utl." and I have added addidtional disk size of /tmp folder and It works as before.
Although It's OK, please explain to me why related to disk szie of folder /tmp.
Thanks so much.
12-05-2017 05:11 AM - edited 12-05-2017 05:13 AM
this is actually a great question.
SAS creates every SAS session with a temporary space location, named SASWORK and UTILLOC (config parameter WORK and UTILLOC).
So it stores temporary tables, intermediate tables (for sorting, and joins), etc. Meaning, it can grow quite fast and have intensive I/O.
By default, SASWORK and UTILOC are on the same location under a parameter named WORK, and by default this location is on the /tmp folder.
It is highly recommended by SAS to change this location to a different one (such as /saswork), actually, a different mount/volume with higher specifications regarding performance on I/O Throughput.
You will find how to change this on (see also http://support.sas.com/kb/24/548.html ):
Also, some periodic cleanup of the /tmp of any SASWORK mount sounds like a good idea