distributed publishing not working

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Matt Painter 5 posts 76 karma points

Aug 16, 2017 @ 00:51

After upgrading from v6 to v7, distributed publishing has stopped working in our environment.

I can verify that umbraco/webservices/cacheRefresher.asmx is being invoked on the child nodes and is returning HTTP 200.

The only errors in the backoffice logs after publishing are about the newly-reserved key key is specified more than once:

2017-08-16 12:01:25,975 [P5024/D2/T18] INFO  Umbraco.Core.Publishing.PublishingStrategy - Content 'Home' with Id '3764' has been published.
2017-08-16 12:01:26,302 [P5024/D2/T18] INFO  Umbraco.Core.PluginManager - Starting resolution types of umbraco.interfaces.ICacheRefresher
2017-08-16 12:01:26,304 [P5024/D2/T18] INFO  Umbraco.Core.PluginManager - Completed resolution of types of umbraco.interfaces.ICacheRefresher, found 0 (took 2ms)
2017-08-16 12:01:26,738 [P5024/D2/T21] INFO  UmbracoExamine.DataServices.UmbracoLogService - Field "key" is listed multiple times in the index set "InternalIndexSet". Please ensure all names are unique, Provider=InternalIndexer, NodeId=3764
2017-08-16 12:01:27,505 [P5024/D2/T18] INFO  Coop.ContentAPI.EventHandlers.ContentEventHandler - Clearing page cache after published cache refresh
2017-08-16 12:01:27,507 [P5024/D2/T18] INFO  Coop.ContentAPI.Services.CacheService - Clearing cache
2017-08-16 12:01:27,538 [P5024/D2/T21] INFO  UmbracoExamine.DataServices.UmbracoLogService - Field "key" is listed multiple times in the index set "InternalIndexSet". Please ensure all names are unique, Provider=InternalIndexer, NodeId=3764
2017-08-16 12:01:27,560 [P5024/D2/T21] INFO  UmbracoExamine.DataServices.UmbracoLogService - Field "key" is listed multiple times in the index set "ExternalIndexSet". Please ensure all names are unique, Provider=ExternalIndexer, NodeId=3764
2017-08-16 12:01:27,608 [P5024/D2/T18] INFO  Coop.ContentAPI.Services.CacheService - Clearing cache
2017-08-16 12:01:27,802 [P5024/D2/T18] INFO  Umbraco.Core.Sync.WebServiceServerMessenger - Submitting calls to distributed servers
2017-08-16 12:01:31,532 [P5024/D2/T20] INFO  umbraco.content - Save Xml to file...
2017-08-16 12:01:31,613 [P5024/D2/T20] INFO  umbraco.content - Saved Xml to file.

There is nothing in the logs on the child nodes.

I have also verified that the app pool user, NETWORK SERVICE has full access to the App_Data folder on the child nodes.

On the child nodes, umbraco.config remains unchanged after publishing - should this be updated after publishing a page?

The following config is on the parent node and, as a precaution, in the child nodes:

<distributedCall enable="true">
  <user>0</user>
  <servers>
    <server forceProtocol="https">uads01</server>
    <server forceProtocol="http" forcePortnumber="2344">uaib01</server>
    <server forceProtocol="http" forcePortnumber="2344">uaib02</server>
  </servers>
</distributedCall>

Copy Link

Matt Painter 5 posts 76 karma points

Aug 16, 2017 @ 01:03

1

Less than two minutes after raising this, I've identified the issue - or at least, a fix.

I changed the distributedCall user to a different user id and publishing is now working.

It appears that something in the upgrade process has broken this user. They no longer appear in the user list in the Umbraco backoffice but are in the dbo.UmbracoUser table, aren't disabled, and look similar to all other active users.

Copy Link
is working on a reply...

Please Sign in or register to post replies