We have successfully:
* set up a client / secret / access token
* obtained a list of contexts from `/compute/contexts`
* performed a POST request to `/compute/contexts/{contextId}/sessions`
The response indicates that the request was successful, JSON is returned eg:
{
"owner": "xxx",
"state": "pending",
"attributes": {
"homeDirectory": "/opt/sas/viya/config/var/run/compsrv/default/92c0b34e-b423-4694-857e-de8d1cc724f3",
"sessionInactiveTimeout": 900
},
"serverId": "92c0b34e-b423-4694-857e-de8d1cc724f3",
"applicationName": "new3FDA16F449B42DE9",
"creationTimeStamp": "2020-05-25T15:54:07.000Z",
"stateElapsedTime": 0,
"sessionConditionCode": 0,
"links": [
{
"method": "GET",
"rel": "self",
Note the state - *pending*.
Subsequent GET requests to this session return:
{"errorCode":5800, "message":"The compute service failed when communicating with another service or server.", "details":["traceId: a1001428b644db83" ,"path: /compute/sessions/92c0b34e-b423-4694-857e-de8d1cc724f3-ses0000" ],"links":[],"version":2,"httpStatusCode":500}
We tried this on the "SAS Studio compute context" and the "sharedcompute" context we created (pooled compute).
How do we get more information? What could be the cause of the session not being properly fired up?
... View more