Load Balanced Environment - Not Refreshing Cache on "slave"
Hey
Umbraco Version 7.1.8
Load Balancer sitting on top of 2 sites - web01 and web02.
The distributedCall functionality was not enabled when the sites were setup so the content team have been manually logging in to each site and publishing / republishing content to ensure the umbraco.config cache is syncronised.
I have today tried activating the distrbutedCall functionality to rectify this but it isn't working. :-(
The intended solution is to use web01 as the master and push changes to web02.
So I updated the umbracoSettings. config with the following:
The Application Pool on WEB02 uses the "NETWORK SERVICE" account this has correct permissions on the app_data so don't see permissions as being the problem.
Can anyone please suggest other places to look / try.
Yep the APPID was the problem - had previously glanced at the posts but never fully read / understood, so now taking the time to do so paid off - the cache is updated on the slave. YAY !
Load Balanced Environment - Not Refreshing Cache on "slave"
Hey
Umbraco Version 7.1.8
Load Balancer sitting on top of 2 sites - web01 and web02.
The distributedCall functionality was not enabled when the sites were setup so the content team have been manually logging in to each site and publishing / republishing content to ensure the umbraco.config cache is syncronised.
I have today tried activating the distrbutedCall functionality to rectify this but it isn't working. :-(
The intended solution is to use web01 as the master and push changes to web02.
So I updated the umbracoSettings. config with the following:
The following is from web01 logs:
The following is from DEBUG mode in log4net on web02:
The Application Pool on WEB02 uses the "NETWORK SERVICE" account this has correct permissions on the app_data so don't see permissions as being the problem.
Can anyone please suggest other places to look / try.
Thanks
Nigel
bump !!!
Hi Nigel,
can this be related to your issue?
http://issues.umbraco.org/issue/U4-5491
Hey
Yep the APPID was the problem - had previously glanced at the posts but never fully read / understood, so now taking the time to do so paid off - the cache is updated on the slave. YAY !
Cheers Nigel
is working on a reply...