I am not able to start the cache locator service. While checking the gemfire command.log file i have seen as below
[info 2017/08/31 11:52:12.271 AEST <main> tid=0x1] Locator stopped
[severe 2017/08/31 11:52:12.271 AEST <main> tid=0x1] Could not bind locator to null[41,415]
In all the configuration files i have checked for DNS names,every thing looks fine.
Can someone please help me in starting this service.
Thanks & Regards,
I know little about gemfire, so just some things I've picked up over time....
1.) After you've stopped it using the sas.servers script
- Check that no gemfire processes are running (ps -ef | grep gemfire | grep -v grep) for UNIX. Kill if there are.
- Delete the gemfire state file
find /sasconf -name .locator
I can't tell you more, as I have never experienced tese problems, and if it didn't start until now, what bad can happen?
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. Is there anyone have a suggestion for what should I do to fix this error and then be able to start SAS cache locator service?
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.