SAS Cache locator service is not starting

[sathya66]

how can we check this. I have done the grep on it (ps -ef | grep 41415) but no other process is running .

[gwootton]

You would want to use netstat or lsof to check for processes listening on a port, rather than ps. For example: netstat -nlp | grep 41415, or lsof -i:41415.

[sathya66]

Yes, I have tried netstat . it is showing as ESTABLISHED with two entries on the screen. what is this mean?

[gwootton]

If there is not a LISTEN entry (and you used the -l option to netstat) that suggests that no process is listening on the port. ESTABLISHED means that a connection exists, but that could be a connection from this host to another, so the server listening on port 41415 could be a different host.

[sathya66]

Thanks for this. How can we resolve this now? Do we need check/update security groups (inbound/outbound) ?

[gwootton]

Are you getting the same message saying it could not bind to port 41415?

[sathya66]

Yes, I am getting the same message as this

[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]

[gwootton]

You may want to take a closer look at your netstat output. If it is reporting established with the host where you are running the command's IP listed as the host connected at port 41415, then you have an existing process using that port. Killing that process should allow the cache locator to bind to the port.

[sathya66]

Tried this

netstat -an|grep 41415 (see the two entries )
tcp 0 0 11.193.80.23:35847 11.193.80.23:41415 ESTABLISHED
tcp 0 0 11.193.80.23:41415 11.193.80.23:35847 ESTABLISHED

Tried this

netstat -nlp|grep 41415

 and see nothing

[gwootton]

The second listing would be the process that was using that port. I believe the netstat -p option includes the process id.

[sathya66]

Terminated the Mid-tier instance and
once instance is up. Started the services and it worked . Not sure what went wrong . Could be some hidden process is using that port

[sathya66]

Is this resolved?