Umbraco.Core.Exceptions.BootFailedException: Boot failed: Umbraco cannot run. See Umbraco's log file for more details.
-> Umbraco.Core.Exceptions.BootFailedException: Boot failed.
-> System.TimeoutException: Cannot acquire MainDom
at Umbraco.Core.Runtime.MainDom.Acquire() in D:\a\1\s\src\Umbraco.Core\Runtime\MainDom.cs:line 172
at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
at Umbraco.Core.Runtime.MainDom.get_IsMainDom() in D:\a\1\s\src\Umbraco.Core\Runtime\MainDom.cs:line 211
at Umbraco.Core.Runtime.CoreRuntime.AcquireMainDom(IMainDom mainDom) in D:\a\1\s\src\Umbraco.Core\Runtime\CoreRuntime.cs:line 460
at Umbraco.Core.Runtime.CoreRuntime.Boot(IRegister register, DisposableTimer timer) in D:\a\1\s\src\Umbraco.Core\Runtime\CoreRuntime.cs:line 185
at Umbraco.Core.Exceptions.BootFailedException.Rethrow(BootFailedException bootFailedException) in D:\a\1\s\src\Umbraco.Core\Exceptions\BootFailedException.cs:line 64
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I believe we have followed the guide from the link above.
Anyone knows why this happens and what we might be missing?
When working with load-balanced setups, there are two differences in Configs that I/we would make between the Umbraco Backoffice server and the Frontend servers.
The first one would be that both type of servers use the following config/transform on their web.config:
Sadly both the documentation and Load Balancing training course mention these properties specifically within the context of load balancing using Azure, and I cannot speak from experience on any on-premise load balanced options. I would however say that it's worth trying out as, while these settings are usually referred to within the concepts of Azure, don't specify themselves to be Azure only, so my best guess would be that these also work on on-premise setups!
I would love to hear back from you if these also function within non-Azure environments! 😄
Boot failed. System.TimeoutException: Cannot acquire MainDom
Hi,
We have a 8.16.0 Umbraco site running on virtual servers in a load balanced setup, on-premise and no Azure.
We have one server for the Umbraco backoffice and two frontend servers with a load balancer in front. Just like the setup here:
https://our.umbraco.com/Documentation/Fundamentals/Setup/Server-Setup/Load-Balancing/index-v8#how-umbraco-load-balancing-works Occasionally the frontend sites gets a Boot failed error and a manual restart of the site is required.
I believe we have followed the guide from the link above.
Anyone knows why this happens and what we might be missing?
Hi Jesper,
When working with load-balanced setups, there are two differences in Configs that I/we would make between the Umbraco Backoffice server and the Frontend servers.
The first one would be that both type of servers use the following config/transform on their web.config:
And second we make a difference in the Examine config, in which the Backoffice Server uses the following web.config transform:
and the Frontend servers use the following web.config transform:
I hope these configs help you resolve your issue!
Kind regards,
Corné Hoskam
Hi Corné,
Thanks for the reply.
You might be correct about the settings, I've been looking at the same settings, however I only found these settings mentioned in the documentation for Load Balancing Azure Web Apps and our site is not running in Azure. https://our.umbraco.com/Documentation/Fundamentals/Setup/Server-Setup/Load-Balancing/azure-web-apps-v8
Can I just assume that these settings are the same for on-premise hosting or do you have a link to the documentation for non-Azure?
Hi Jesper,
Sadly both the documentation and Load Balancing training course mention these properties specifically within the context of load balancing using Azure, and I cannot speak from experience on any on-premise load balanced options. I would however say that it's worth trying out as, while these settings are usually referred to within the concepts of Azure, don't specify themselves to be Azure only, so my best guess would be that these also work on on-premise setups!
I would love to hear back from you if these also function within non-Azure environments! 😄
is working on a reply...