BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
sandeep_reddy
Quartz | Level 8

Hi There,

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,

Sandeep

1 ACCEPTED SOLUTION

Accepted Solutions
sandeep_reddy
Quartz | Level 8
Hi All,
I don't know what went wrong. I have found .locator file as hidden file , I have deleted this file and restarted the sevices . Now Cache locator service came up.

View solution in original post

26 REPLIES 26
nhvdwalt
Barite | Level 11

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

 

PWC2018_1
Fluorite | Level 6
What do mean exactly by: Delete the gemfire state file

Is it a rename of all files under .../Web/gemfire/instances/ins_41415/ will be Ok ?
gwootton
SAS Super FREQ
You would not want to rename all the files there. There is a file called "locator41415state.dat" which I suspect is the state file being referenced here.
--
Greg Wootton | Principal Systems Technical Support Engineer
anja
SAS Employee

Hi,

 

looks like there is a process already running on 41415, meaning, the port is already used.

Can you check this?

 

Thanks

Anja

 

 

 

sandeep_reddy
Quartz | Level 8
Hi All,
I don't know what went wrong. I have found .locator file as hidden file , I have deleted this file and restarted the sevices . Now Cache locator service came up.
MariaD
Barite | Level 11

Hi @sandeep_reddy,

 

I have the same situation, could you please advice me where the hidden file is located?

 

Regards,

MariaD
Barite | Level 11

Thanks! So, after I deleted this file, I can start the cache service locator without any problem, right?

 

Regards, 

TrueNorthLLC
Fluorite | Level 6

Thanks. I had this issue after doing a system image restore in WinSvr2012r2.

SASKiwi
PROC Star

@sandeep_reddy - Much appreciated. I had exactly the same problem and your solution fixed it.

celikzeki
Calcite | Level 5

Hello eb,

Even though solution work, problem repeats itself. So if specified files are deleted then it starts again. But real issue is how to prevent these problem iterating.  So any idea or real solution.

Zuhdiyah
Fluorite | Level 6

Hi,

 

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?

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 

CLI in SAS Viya

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.

Discussion stats
  • 26 replies
  • 26556 views
  • 3 likes
  • 12 in conversation