Actions
action #105900
openo3 logreports - Unable to wakeup scheduler: Request timeout
Start date:
2022-02-03
Due date:
% Done:
0%
Estimated time:
Description
We see the following warnings on o3:
# /var/log/openqa
[2022-02-01T02:30:07.684500Z] [warn] [pid:5085] Unable to wakeup scheduler: Request timeout
[2022-02-01T02:30:09.862049Z] [warn] [pid:31785] Unable to wakeup scheduler: Request timeout
[2022-02-01T02:30:10.899165Z] [warn] [pid:32767] Unable to wakeup scheduler: Request timeout
Updated by okurz almost 3 years ago
- Project changed from openQA Infrastructure (public) to openQA Project (public)
These are all things that could be better handled by the software itself, not infrastructure issues
Updated by okurz almost 3 years ago
- Parent task deleted (
#105828)
All of these issues can be fixed but the alert ticket is addressed by preventing the alert so better not treat as subtask
Updated by okurz almost 3 years ago
- Related to action #105828: 4-7 logreport emails a day cause alert fatigue size:M added
Actions