Copied to clipboard

Flag this post as spam?

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


  • Alan Mitchell 30 posts 172 karma points c-trib
    1 week ago
    Alan Mitchell
    0

    Deploying between cloud environments empties the memory cache (unpublishing the site!)

    Hello,

    In the past week (since the upgrade to 8.1.4, may or may not be relevant) we have had odd behaviour when deploying changes between environments on Umbraco cloud.

    Deploying a change from Development to Live is successful, but the public website appears to have all the content unpublished. Looking at nodes in the back office, they will say "This node is published but not in the cache", or "This document is published but its url cannot be routed".

    Pressing Save and Republish on an affected node throws an error the first time, but will work on the second try....

    Unhandled controller exception occurred for request '"https://XXX.s1.umbraco.io/umbraco/backoffice/UmbracoApi/Content/PostSave"'

    Exception System.Exception: panic: failed to get next child with id=-1 at Umbraco.Web.PublishedCache.NuCache.ContentStore.GetLinkedNode(Int32 id, String description) at Umbraco.Web.PublishedCache.NuCache.ContentStore.RemoveNodeLocked(ContentNode content) at Umbraco.Web.PublishedCache.NuCache.ContentStore.SetBranch(Int32 rootContentId, IEnumerable'1 kits) at Umbraco.Web.PublishedCache.NuCache.PublishedSnapshotService.NotifyLocked(IEnumerable'1 payloads, Boolean& draftChanged, Boolean& publishedChanged) at Umbraco.Web.PublishedCache.NuCache.PublishedSnapshotService.Notify(JsonPayload[] payloads, Boolean& draftChanged, Boolean& publishedChanged) at Umbraco.Web.Cache.ContentCacheRefresher.Refresh(JsonPayload[] payloads) at Umbraco.Core.Sync.ServerMessengerBase.DeliverLocal[TPayload](ICacheRefresher refresher, TPayload[] payload)

    There are no errors in the deployment log, but this problem has happened consistently with the past few deployments we have made to Live and I think on development too (but harder to spot).

    The easiest fix is to go into Settings > Published Status and press Reload on the Memory cache. So it doesn't look like it's causing any real harm, but my biggest concern is that an automatic upgrade at a random time on a Tuesday will unpublish a production site without warning ....

    This site was impacted by having inconsistent language settings (trying to change en-us to en-gb) which caused deployment issues I think back on 8.1.2 but I thought that was dealt with.

    Has anyone seen anything similar on their sites? Or have clues as to where to look further to investigate?

Please Sign in or register to post replies

Write your reply to:

Draft