Skip to main content

Hi on a customer environment which has 3 alliance application servers, when we import customization we have an error message : “cache not running”.

We have checked the configuration editor cache section : all the three servers IP address are set, we have run the astea.redis.configuration.exe everything is ok. when we browse on each server the url  localhost/Asteaalliance150 we are able to import the customization only on the server which is “master”.

According to the customer the port 6379 is opened between the servers.

Have you already encounter this ? what could be the cause ?

thanks for your feedback

Rgds

Christophe

Hi Christophe,
Do you see any errors in the Astea-Cache or Alliance Event Viewer logs on the servers that are marked as ‘slaves’ and not ‘master’?  Look for error entries like ‘Cannot write to a read-only slave’ or anything along those lines…that may help to shed some light on the problem.  Usually it’s when one of the slaves can’t connect to the master so it tries to promote itself to be the new master but the other servers don’t adjust accordingly and you end up with a corrupted cache configuration.
Thanks,
Reid

Hi Reid, i will check on the customer environment but i can’t have access until next week. i will keep you updated thanks

Reply


Terms & ConditionsCookie settings