Actions
action #162518
closedUnable to consistently login at stats.openqa-monitor.qa.suse.de
Status:
Resolved
Priority:
Low
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-06-19
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
Links in alert emails contain stats.openqa-monitor.qa.suse.de which is an alias to monitor.qa.suse.de - except I failed to login after several attemps. As I was drafting this ticket I tried again and logging in eventually worked.
See also this Slack thread, others in the team were able to reproduce the error and eventually able to login.
Suggestions¶
- Look into logs on monitor.qa.suse.de to find relevant messages
Jun 19 13:11:18 monitor grafana[18120]: logger=authn.service t=2024-06-19T13:11:18.159015268+02:00 level=warn msg="Failed to authenticate request" client=auth.client.session error="user token not found"- Also noticed these ones, tho they may not be related
Jun 19 12:59:18 monitor grafana[18120]: logger=sqlstore.transactions t=2024-06-19T12:59:18.470555152+02:00 level=info msg="Database locked, sleeping then retrying" error="database is locked" retry=0 code="database is locked"
Workaround¶
- Replace the hostname in alert URL's to get a reliably working link using monitor.qa.suse.de
Updated by livdywan about 2 months ago
- Status changed from New to Feedback
- Assignee set to livdywan
Since I ran into this again and would prefer not to spend that much time looking at a failed login or replacing URLs I'm proposing a change to at least use the URL which works for me:
https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1297
Updated by livdywan about 2 months ago
- Copied to action #169147: Unable to login at Grafana (monitor.qa.suse.de or any other domain) added
Updated by okurz 15 days ago
- Status changed from Feedback to Resolved
https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1297 successfully deployed. This should suffice.
Actions