cachelocator has duplicate old instance - can not find it

agrawalved — Thu, 07 Jan 2021 10:45:22 GMT

Hi,

After applying HotFixes in Viya 3.4 I am getting issue with cachelocator-listner-v1 service. Two instance of the services can be seen in Dashboard on different port with one being old and in RED.

After checking the log for cachelocator I find "Other Locator" instance, which is infact an older instance of the cache locator (before restart).

Snapshot of Log:

2021-01-05 12:17:48.822 INFO cache --- [ main] o.a.g.d.i.m.g.l.GMSLocator : GemFire peer location service starting. Other locators: 10.245.13.187[38565] Locators preferred as coordinators: false Network partition detection enabled: false View persistence file: /opt/sas/viya/config/tmp/sas-cachelocator/locator43355view.dat

I have cleared the logs and other files in tmp directory of cache locator, clear consul checks, restarted cachec controller several time and also twice complete Viya services. But none of this is getting rid of the old cachelocator instance. Moreover I have verified open connection (with netstat - tunlp) but could not find any connection on old port.

I also verified the .pid files and they have the latest pid which is connecting to a fresh port.

The Hot fix installation completed successfully with no Errors reported by just after that cachelocator is not able to respond.

Would be great if someone shares experience of a similar issue faced and the solution applied.

Thanks

Ved

Re: cachelocator has duplicate old instance - can not find it

agrawalved — Thu, 28 Jan 2021 12:06:19 GMT

I have got solution to this, it can be achieved by doing below:

a. Stop All Viya services

b. stop httpd

c. kill any instance of httpd /apache left

d. de-register port which is blocking

e. start httpd

f. start all viya services

topic Re: cachelocator has duplicate old instance - can not find it in Administration and Deployment

cachelocator has duplicate old instance - can not find it

Re: cachelocator has duplicate old instance - can not find it