Skip to main content
14 events
when toggle format what by license comment
Apr 13, 2017 at 12:49 history edited CommunityBot
replaced http://tridion.stackexchange.com/ with https://tridion.stackexchange.com/
Oct 8, 2013 at 17:00 history edited Nuno Linhares CC BY-SA 3.0
added 871 characters in body
Oct 8, 2013 at 11:03 comment added Anupam Baksi Thanks again for your valuable inputs, I will try to produce something like you have stated and will let you know for any help.
Oct 8, 2013 at 10:15 comment added Nuno Linhares OK, then the only way is to start checking logs in DEBUG mode. The Cache clients will log when they connect and when they fail to connect. If correctness of data is more important than performance I would start by turning the cache OFF and put a couple of machines aside to test configuration.
Oct 8, 2013 at 10:09 comment added Anupam Baksi Hi Nuno, this is the one from where (deployer in this case) CCS is running, in the app servers it is pointing to the server IP of the deployer in "RemoteSynchronization Host" section. Sorry for not mentioning that earlier.
Oct 8, 2013 at 10:02 comment added Nuno Linhares Your app servers have the wrong IP in the config - according to your sample they're pointing to 127.0.0.1, they should point to the machine running the CCS service (deployer).
Oct 8, 2013 at 9:54 comment added Anupam Baksi Thanks for the explanation Quirijn. I have checked the connectivity from the deployer server, where CCS is present to the web servers (netstat to the 1099 port from webservers is listening). Is there any way to check if CCS is working properly. I have checked the configuration files/ tried restating the service but no results. Strange thing is, it works fine for staging where the configuration is almost same and also after around 24 Hrs the issue gets resolved in Prod as well automatically. Thanks in advance for your time.
Oct 8, 2013 at 8:21 comment added Quirijn If the problem is with the connection to the CCS, one would expect a restart of IIS to solve it, at least until you publish something again. After a restart, the cache is empty and all items (content, links) have to be retrieved from the broker again.
Oct 7, 2013 at 9:12 comment added Anupam Baksi Just adding some more information, I have looked into this for a time now, and restarting IIS is solving the issues for time being. If this is caching problem, then it might be with the IIS/Load balancer end. Please correct me if I am wrong. Is the problem still can be with CCS as restating APP server solves the issue. Kindly suggest.
Sep 30, 2013 at 12:06 comment added Nuno Linhares Well, it's slightly more complicated than that. The CCS service must be running on port 1099 on the deployer server and the app servers must be connecting to that one, not to a local one, and yes changing configuration requires a restart, the configuration is only read once.
Sep 30, 2013 at 6:38 comment added Anupam Baksi Thanks again. Yes, I have checked that from the server that port 1099 is in listening mode (using 'netstat -anv'). Also, one thing, we have CCS configured in broker configurations which reside in the web servers, there 'Remote Synchronization host' is also pointing to the server from where the CCS windows service is running, is there a change required there? After changing the configuration file (logger mode), do I need to restart any service, I guess not. Please suggest. Any other indications.
Sep 28, 2013 at 11:05 history edited Nuno Linhares CC BY-SA 3.0
added 304 characters in body
Sep 27, 2013 at 13:20 comment added Anupam Baksi Many thanks for explaining Nuno. I have edited the question with CCS configuration for your reference, can you please have a kind look into it?
Sep 24, 2013 at 13:06 history answered Nuno Linhares CC BY-SA 3.0