New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The culture specified '' was not found in any configured sources for this service - Linux App Service Plan #13980
Comments
Hi there @wtct! Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better. We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
Thanks for reporting this 🐛 Wierd one indeed, this works just fine on windows app service plans, so I'm wondering unsure about whether I like the workaround in the core, or have it documented when using Linux app-service plans with Umbraco. I will bring this up to the team and get back to you (this might take a while) 👍 |
Hi thanks for posting this we also host Umbraco 11 on Azure linux container apps and this error have been bugging us for some time since it's flooding the error log skewing our log rates. We also deduced that it was related to processes on other than the main thread; the culture there is empty. Our workaround was also to manually set the thread culture in those processes. Setting LANG in our web apps did NOT resolve the issue. For context, from what I can see there are just a couple of instances in the codebase that triggers this error, for example: |
Hi @jrunestone, Thanks for letting us know that LANG setting is not working as expected. However, please ensure that you have set the DefaultThreadCurrentCulture in the IComponent which is registered by composer and running as expected :) I'm sure, it solved this issue perfectly :) |
Ran into this issue in both a docker container deployment and in a Github action test step. I wouldn't expect a linux app service plan to behave any different, so might be worth double checking what value the environment variable was set to. |
@vsilvar As mentioned, setting the |
Hi @vsilvar thank you for the tip! Yesterday, I experimented with the LANG setting and noticed that the warning disappeared, which was promising. However, after several deployments, it seems the issue has come back and the LANG setting is still there. |
Has there been any update on this? |
I am using Umbraco 13.1.1 and I am still getting this warning message showing up in the startup logs. I have tried adding the DefaultCultureComponent as suggested, and also have set the Any other suggestions? |
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
11.2.0
Bug summary
Hi Guys,
Together with @piotrbach, we have noticed an issue which occurs at every Umbraco startup and during operations performed through the ContentService in the custom threads or the Hosted Services.
We can see a lot of warnings in our logs, as below:
At the beginning, we were solving this warnings by adding a piece of code to each custom theads and Hosted Services, as below:
In the meantime, I have invented and implemented a tricky solution which takes into account default language configured in the backoffice.
CultureInfo.DefaultThreadCurrentCulture Property
We are just wondering if the solution available on our blog should be built-in the Umbraco or not.
We haven't found any recommendations related to the Umbraco configuration, but we have found this:
https://www.gulla.net/en/blog/change-locale-culture-for-a-linux-based-azure-webapp/
Maybe this issue could be solved by LANG setting of the Azure App Service. However, what about the default languages set in the backoffice? Should it be taken into account?
Specifics
No response
Steps to reproduce
Expected result / actual result
No response
The text was updated successfully, but these errors were encountered: