How to up the cachelocator in middle tier in sas 9.4 m7

[Samdani]

Hi Team,

I tried so many times but the cacheloactor is not up,Please find the screen shot as reference

and when i start the services it shows like this: 

[sas@sas-mid-tier1 ins_41416]$ ./gemfire-locator.sh start
41416
/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/gemfire.jar:/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/antlr.jar:/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/gfsh-dependencies.jar:/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/spring-shell-1.0.0.RELEASE.jar:.:/sasdata/tmp/stand_alone/jars/*:/sasdata/tmp/stand_alone/sitexmls/:
cd /sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/instances/ins_41416; nohup -- /sasdata/sasinst_lev2/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/bin/java -Xms128m -Xmx512m -Dgemfire.log-file=/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/instances/ins_41416/gemfire.log -Dgemfire.mcast-port=0 -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=false -Dgemfire.locators=sas-app-server[41416],taxanalytics.rajasthan.gov.in[41416] -Dgemfire.license-application-cache=6M0C3-4VW9H-M8J40-0D52F-DTM0H -Dgemfire.member-timeout=600000 -classpath /sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/gemfire.jar:/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/antlr.jar:/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/gfsh-dependencies.jar:/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/lib/spring-shell-1.0.0.RELEASE.jar:.:/sasdata/tmp/stand_alone/jars/*:/sasdata/tmp/stand_alone/sitexmls/: com.gemstone.gemfire.distributed.Locator 41416 2>&1 1>/sasdata/sasconf_lev2/Config/Lev2/Web/gemfire/instances/ins_41416/gemfireCommand.log &
[sas@sas-mid-tier1 ins_41416]$ nohup: redirecting stderr to stdout

please do need full to bring it up.

Regards

Samdani

[SASKiwi]

I suggest you check if port 41416 is already in use or not as that appears to be the port used by the cache locator. You can use the netstat or lsof linux commands to do that. If the port is already in use, kill the process using it, then try starting the cache locator again.

[Samdani]

Hi Team,
I am unable to bring up the CacheLocator in the middle tier. Please do
needful. I am sending the log file. please find the attachment of the log
file

Regards
Sandhani

[Ahmed_Dhaoui]

Hi,
 take a backup or snapshot first, then try deleting these files and restart all services.

rm -rf $sasconfig/Lev1/Web/activemq/data/*
rm -rf $sasconfig/Lev1/Web/gemfire/instances/ins_41415/locator41415state.dat
rm -rf $sasconfig/Lev1/Web/gemfire/instances/ins_41415/.locator
rm -rf $sasconfig/Lev1/Web/gemfire/instances/ins_41415/*.log
mv /app/sas/sasconfig/Lev1/Web/gemfire/instances/ins_41415/ConfigDiskDir /app/sas/sasconfig/Lev1/Web/gemfire/instances/ins_41415/ConfigDiskDir_

[AhmedAl_Attar]

@Samdani 

A word of advice, Make sure to stop the services before deleting the log files.

[Samdani]

Hi Ahmed,

I fallow the step what you recommended, even it is not up. i am sharing the gemfire.log and gemfireCommand.log as text files please find as attachment .i am unable to find the root cause why it is not up.

Regards

Samdani

[SASKiwi]

Did you check if the port is already in use or not like I suggested? Rebooting the server would also fix this problem. 

[Sajid01]

I see this in your gemfire log

[severe 2025/05/26 10:33:15.036 IST  <main> tid=0x1] Could not bind locator to null[41,416]

This means that the port 41416 is busy.
Do you have any other instance of SAS running? 

You can perform the following
1. Make sure port 41416 is not being used by any other process. 
2.If it is not, then stop SAS , stop the machine
3.Restart the machine and start SAS
See it works or not.

[Nigel_Pain]

I think this could be a case for Tech. Support. We've had problems with the cache locator before and they've always been able to resolve them.