The login is now fixed. It was SELinux issue.
Michal
On 19. 10. 22 18:12, Mattia Verga wrote:
Il 19/10/22 14:45, Michal Konecny ha scritto:
1) I noticed that the queue is still growing, so I added 3 more workers.
Hopefully this will be enough to catch up.
Looking at the latest batch I received, it seems it is now running with
kinda default filters for everyone: I am receiving notifications for
things I had previously disabled, thus increasing traffic and queue load.
I am, however, unable to login and reset filters. Maybe it would be best
to review the default filter applied to reduce load, while the frontend
is being fixed.
Mattia
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue