We are moving infrastructure from one Azure tenant to another.
Everyting is working, except publishing. When we publish the frontend server is not updated accordingly.
We have separated backoffice and frontend instances.
We are running 8.18.1.
On the frontend this exception is thrown:
{"@t":"2024-04-05T08:04:50.2780387Z","@mt":"DISTRIBUTED CACHE IS NOT UPDATED. Failed to execute instructions ({DtoId}: '{DtoInstructions}'). Instruction is being skipped/ignored","@l":"Error","@x":"System.NotSupportedException: Umbraco.Web.PublishedCache.NuCache.DataSource.JsonContentNestedDataSerializer does not support byte[] serialization\r\n at Umbraco.Web.PublishedCache.NuCache.DataSource.JsonContentNestedDataSerializer.Deserialize(IReadOnlyContentBase content, String stringData, Byte[] byteData, Boolean published) in D:\\a\\1\\s\\src\\Umbraco.Web\\PublishedCache\\NuCache\\DataSource\\JsonContentNestedDataSerializer.cs:line 30\r\n at Umbraco.Web.PublishedCache.NuCache.DataSource.DatabaseDataSource.CreateContentNodeKit( dto, IContentCacheDataSerializer serializer) in D:\\a\\1\\s\\src\\Umbraco.Web\\PublishedCache\\NuCache\\DataSource\\DatabaseDataSource.cs:line 418\r\n at Umbraco.Web.PublishedCache.NuCache.DataSource.DatabaseDataSource.GetContentSource(IScope scope, Int32 id) in D:\\a\\1\\s\\src\\Umbraco.Web\\PublishedCache\\NuCache\\DataSource\\DatabaseDataSource.cs:line 218\r\n at Umbraco.Web.PublishedCache.NuCache.PublishedSnapshotService.NotifyLocked(IEnumerable`1 payloads, Boolean& draftChanged, Boolean& publishedChanged) in D:\\a\\1\\s\\src\\Umbraco.Web\\PublishedCache\\NuCache\\PublishedSnapshotService.cs:line 719\r\n at Umbraco.Web.PublishedCache.NuCache.PublishedSnapshotService.Notify(JsonPayload[] payloads, Boolean& draftChanged, Boolean& publishedChanged) in D:\\a\\1\\s\\src\\Umbraco.Web\\PublishedCache\\NuCache\\PublishedSnapshotService.cs:line 651\r\n at Umbraco.Web.Cache.ContentCacheRefresher.NotifyPublishedSnapshotService(IPublishedSnapshotService service, AppCaches appCaches, JsonPayload[] payloads) in D:\\a\\1\\s\\src\\Umbraco.Web\\Cache\\ContentCacheRefresher.cs:line 133\r\n at Umbraco.Web.Cache.ContentCacheRefresher.Refresh(JsonPayload[] payloads) in D:\\a\\1\\s\\src\\Umbraco.Web\\Cache\\ContentCacheRefresher.cs:line 105\r\n at Umbraco.Core.Cache.PayloadCacheRefresherBase`2.Refresh(String json) in D:\\a\\1\\s\\src\\Umbraco.Core\\Cache\\PayloadCacheRefresherBase.cs:line 41\r\n at Umbraco.Core.Sync.DatabaseServerMessenger.NotifyRefreshers(IEnumerable`1 instructions, HashSet`1 processed) in D:\\a\\1\\s\\src\\Umbraco.Core\\Sync\\DatabaseServerMessenger.cs:line 642\r\n at Umbraco.Core.Sync.DatabaseServerMessenger.ProcessDatabaseInstructions(IReadOnlyCollection`1 instructionBatch, CacheInstructionDto dto, HashSet`1 processed, Int32& lastId) in D:\\a\\1\\s\\src\\Umbraco.Core\\Sync\\DatabaseServerMessenger.cs:line 407","DtoId":102098,"DtoInstructions":"[{\"RefreshType\":4,\"RefresherId\":\"900a4fbe-df3c-41e6-bb77-be896cd158ea\",\"GuidId\":\"00000000-0000-0000-0000-000000000000\",\"IntId\":0,\"JsonIds\":null,\"JsonIdCount\":1,\"JsonPayload\":\"[{\\\"Id\\\":65459,\\\"Key\\\":\\\"50587ba4-f852-4e6f-935a-7473dbb364f2\\\",\\\"ChangeTypes\\\":2}]\"}]","SourceContext":"Umbraco.Core.Sync.DatabaseServerMessenger","ProcessId":9140,"ProcessName":"w3wp","ThreadId":47,"AppDomainId":2,"AppDomainAppId":"LMW3SVC428067279ROOT","MachineName":"DW0MDWK0001VT","Log4NetLevel":"ERROR"}
DISTRIBUTED CACHE IS NOT UPDATED
Hi,
We are moving infrastructure from one Azure tenant to another. Everyting is working, except publishing. When we publish the frontend server is not updated accordingly.
We have separated backoffice and frontend instances.
We are running 8.18.1.
On the frontend this exception is thrown:
Any suggestions or advice?
check your Explicit Master Scheduling server - maybe you need to clean UmbracoServer table and follow https://our.umbraco.com/Documentation/Fundamentals/Setup/Server-Setup/Load-Balancing/flexible-advanced#explicit-master-scheduling-server
Thanks, we found the issue. It was a mis Config configuration on that server. :(
is working on a reply...