Hi Folks,
Sometimes you are trying to troubleshoot one thing and end up solving another :), How many of you have ended up same?
Well, I was actually troubleshooting the high CPU and no. of requests on CD was trying to find some error patterns from Sitecore logs for one of the issues we were facing, there was one specific error which we kept observing was below
Exception
and if you drill further down into it, Sitecore was looking for master DB on CD servers, which is not possible, so definitely, this is bugI previously faced the same error but for other assembly and to troubleshoot and resolving that the approaches were different but for both meaning of the error is same, for 10.3 where i got the error is drafted here Error in Sitecore 10.3 XM with CDs - Could not find configuration node: database/database[@id='master']
Troubleshooting
It was clear that because some the code which is in "VersionInitializer" class of "SItecore.XA.Foundation.Upgrade.dll" is referring to "master" database on a CD server.
So, I just tried dissembling the DLL to understand what's going on and you can see below
It is clearly seen that code is referring to wrong DB instead of the context DB, it is "master" DB and that is the reason of the error
Solution
Further troubleshooting and research suggested that this can be safely ignored, and this comes only when the instance is starting, but just to keep our logs clean we just commented out below lines from "\App_Config\Modules\SXA\Foundation\Sitecore.XA.Foundation.Upgrade.config" of CD instance
and that is the suggested approach from Sitecore.
Comments
Post a Comment