I follow all steps from tutorial and make a umbraco instalation in load balance.
i have to server named below and the website url as "https://www.xyz.com".
1)127.0.0.1
2)127.0.0.2
But, when i update certains contents like media, or creation a new node then the cache dont update in all servers.the images is not avaliable in bot the node...nd the same way node is also not displaying...
please guide me the best way to solve this problem...
When you are using the DistributedCall functionality a log entry is made to the umbracoLog table when content is published. The log is written if the distributed call succeeds or fails, and logs the error message. This might provide some clues to why your content is not being published.
Make sure you place the media directory on a SAN and map it as a virtual directory in your application.
As Dallas says, you'll need to specify each server address in the Distributed Calling section of umbracoSettings.config. You'll also need to verify each server can talk to each other. Do you have wildcard bindings setup on each of your IIS Websites? If not, add http://server-1.xyz.com/ and http://server-2.xyz.com/ to each IIS Website and update Distributed Calling accordingly. Again, verify you can get to http://server-2.xyz.com/ from http://server-1.xyz.com/ by logging on to the box and visiting the domain.
Load balance environment don't update cache.
Hi All..
I follow all steps from tutorial and make a umbraco instalation in load balance.
i have to server named below and the website url as "https://www.xyz.com".
1)127.0.0.1
2)127.0.0.2
But, when i update certains contents like media, or creation a new node then the cache dont update in all servers.the images is not avaliable in bot the node...nd the same way node is also not displaying...
please guide me the best way to solve this problem...
thanks..
Are you by any chance using contour's code first in your website?
nope..
and i jst want which approch i should follow to solve above mentioned issue..
Have you had a look at the umbracoLog table?
When you are using the DistributedCall functionality a log entry is made to the umbracoLog table when content is published. The log is written if the distributed call succeeds or fails, and logs the error message. This might provide some clues to why your content is not being published.
Dallas
127.0.0.1 will point att the server itself, in both cases. Have you tried using the IP of the server?
Make sure you place the media directory on a SAN and map it as a virtual directory in your application.
As Dallas says, you'll need to specify each server address in the Distributed Calling section of umbracoSettings.config. You'll also need to verify each server can talk to each other. Do you have wildcard bindings setup on each of your IIS Websites? If not, add http://server-1.xyz.com/ and http://server-2.xyz.com/ to each IIS Website and update Distributed Calling accordingly. Again, verify you can get to http://server-2.xyz.com/ from http://server-1.xyz.com/ by logging on to the box and visiting the domain.
is working on a reply...