BookmarkSubscribeRSS Feed
sas_chinmay
Fluorite | Level 6

We are unable to start or check the status of services, and we are getting ‘killed’ as a response to every command query.

Any suggestions on how we can fix these issues?

sas_chinmay_0-1736404484026.png

 

 

 

3 REPLIES 3
gwootton
SAS Super FREQ
Looks like the script is returning a Killed message when it tries to start the subtasks for .pre (WIP data server) and .mid (Middle Tier).
The message "Killed" means that something killed that subprocess. Are you able to run those scripts (sas.servers.pre and sas.servers.mid) in the same path with the status command and receive output?
--
Greg Wootton | Principal Systems Technical Support Engineer
JuanS_OCS
Azurite | Level 17

Do you have the sas.servers script customized from the default one delivered on the installation?

Or the sas.server.pre?

I can imagine there might be an issue with your WIP service. Have you tried to start all services manually, independently, and in order, to see if any of them fail, and which one?

sas_chinmay
Fluorite | Level 6

We have rebooted the server and started the SAS services and found that they are now up and running. We tried to investigate the root cause of the issues, but we did not find any. Therefore, we will keep monitoring to see if the same thing happens again.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 243 views
  • 1 like
  • 3 in conversation