BookmarkSubscribeRSS Feed
aloou
Obsidian | Level 7
Hello everyone,
Sas cache locator service ins_41415 is not up and i can not start it.
I have stopped sas.servers.mid and then started it now this cache locator is not started.
Help please
5 REPLIES 5
DanielKaiser
Pyrite | Level 9

Hi @aloou,

 

what does the gemfire-log say?

You should find it at SASCONF/Web/gemfire/instances/ins_*

aloou
Obsidian | Level 7
The gemfirecommand.log says :
Could not bind locator to null [41415]
pururshothaman
Fluorite | Level 6
Hi,

1. Stop sas.servers completely

2. Have you checked any dormant SAS process running on the server.
ps -ef |grep SAS would give you the process list that is running if any thing kill them.

3. Under /gemfire/instances/ins_41415/ check if a hidden file is found like .locator if found clean it out and start the instance.

Also
Please check on this there is a solved solution on this.

https://communities.sas.com/t5/Administration-and-Deployment/SAS-Cache-locator-service-is-not-starti...
Zuhdiyah
Fluorite | Level 6

I have the same issue, but there is no .locator file on my server. I have checked if it might be hidden but found out that it does not exist. What should I do to fix this error and start SAS cache locator service?

gwootton
SAS Super FREQ
did you confirm no other process was listening on the gemfire port (41415)?
--
Greg Wootton | Principal Systems Technical Support Engineer

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
  • 5 replies
  • 6445 views
  • 2 likes
  • 5 in conversation