Skip to content
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

PostgresSQL error #2775

Closed
james-1987 opened this issue Jan 7, 2022 · 1 comment · Fixed by #2776
Closed

PostgresSQL error #2775

james-1987 opened this issue Jan 7, 2022 · 1 comment · Fixed by #2776
Labels
area/storage SQL Storage related features/bugs type/bug Confirmed Bugs

Comments

@james-1987
Copy link

Description

(100% cpu usage on 1 thread on Authelia once, that's why i started to look for problems)

Got an error from PostgreSQL log when i login on Authelia. Repeats every time i login. Not a SQL expert. But feels like something is not coded right in Authelia for PostgreSQL.
But Authelia is still working fine. Nothing in Authelias (on debugging) log.

My setup

Docker Container on both PostgreSQL and Authelia.
Same user-defined bridge.
Linux slackware/unraid.

Things i tried to mitigate the problem

Updated Nginx/swag config file for authelia. Think that was the high CPU usage. But i'm not certain. Not seen it again (4 hour)

Updated from postgreSQL 13 -> 14. Nothing changed.

Purged the whole Authelia Database and started a brand new. Nothing changed.

Additional Information

From postgres log:

2022-01-07 05:53:50.975 CET [264] ERROR: operator does not exist: boolean = integer at character 134

2022-01-07 05:53:50.975 CET [264] HINT: No operator matches the given name and argument types. You might need to add explicit type casts.
2022-01-07 05:53:50.975 CET [264] STATEMENT:
SELECT time, successful, username
FROM authentication_logs
WHERE time > $1 AND username = $2 AND auth_type = '1FA' AND banned = 0
ORDER BY time DESC
LIMIT $3
OFFSET $4;

@james-d-elliott
Copy link
Member

This should be fixed by #2776 feel free to try it but I'll release it soon anyway.

@james-d-elliott james-d-elliott added type/bug Confirmed Bugs and removed type/bug/unconfirmed Unconfirmed Bugs labels Feb 17, 2022
@james-d-elliott james-d-elliott added the area/storage SQL Storage related features/bugs label Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage SQL Storage related features/bugs type/bug Confirmed Bugs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants