-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
Invalid SQL query error in logs #8923
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
Can you please enable logging of full database queries and post here the problematic query? Setting |
Thanks for the quick response, I also had to set
|
That's a different query failing with the same error now. What makes me think that there is some issue in the PostgreSQL server rather than in Weblate. The one failing now is the statistics query, which is executed frequently on each Weblate instance, and we haven't seen any such failure so far. PS: The problematic query also works fine on testing PostgreSQL servers I have… |
I see, perhaps it's the PSQL Version. I'm just headed home as I'm not feeling well, I'll check it out tomorrow, thank you. Sent from my phone-------- Original message --------From: Michal Čihař ***@***.***>Date: Tue, 14 Mar 2023, 9:24 amTo: WeblateOrg/weblate ***@***.***>Cc: Eren ***@***.***>, Author ***@***.***>Subject: Re: [WeblateOrg/weblate] Invalid SQL query error in logs (Issue #8923)
That's a different query failing with the same error now. What makes me think that there is some issue in the PostgreSQL server rather than in Weblate. The one failing now is the statistics query, which is executed frequently on each Weblate instance, and we haven't seen any such failure so far.
PS: The problematic query also works fine on testing PostgreSQL servers I have…
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hey, sorry for the late reply, we got the DB working on PSQL 11 and decided to give 14 another try coz I figured I might've done a mistake when migrating. I believe I imported the dump as the root user after creating the weblate user which might've caused the issue. We now created the weblate user & db and then gave the weblate user the admin role (to be able to install the extensions) and started loading the SQL dump. After that everything works fine! Closing the ticket, appreciate your help <3 |
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
|
Describe the issue
I'm receiving the following error when I try to open the dashboard or a project.
I migrated Weblate from Linux installation (git checkout) to Kubernetes using the official chart. PostgreSQL is a managed database from Microsoft Azure.
Error log
I already tried
Steps to reproduce the behavior
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
weblate@weblate-f448467cd-czqjl:/$ weblate list_versions
weblate@weblate-f448467cd-czqjl:/$
Weblate deploy checks
Additional context
No response
The text was updated successfully, but these errors were encountered: