coordination #96447
closed[epic] Failed systemd services and job age alerts
100%
Description
Observation¶
Alertshandled in #96554Disk I/O time for /dev/vdd (/results)
Alerts forJob age (scheduled)
- Alerts for
Failed systemd services
- This is about the alert from 02.08.21 01:17 (the one from 05.08.21 07:26 was caused by a user's misconfiguration).
Suggestion¶
- Bump our thresholds
- Investigate if our average load has increased immensely e.g. new test groups being scheduled
- Look at systemd journal while the alert is running (short of having #96551)
- Check if we have data on reduced heat/ power in server room 2
Job age (scheduled) (median)
is likely due to issues with theWORKER_CLASS
of https://openqa.suse.de/tests/6513484
Updated by livdywan over 3 years ago
Disk I/O time for /dev/vde (/space-slow)
with vde: read 20068.460
was alterting again for a minute
Updated by livdywan over 3 years ago
Disk I/O time for /dev/vdd (/results)
once more alerting with vdd: write 13648.552
for 9 minutes.
Updated by okurz over 3 years ago
- Priority changed from Normal to Urgent
bumping to "urgent" to counter alarm fatigue.
Updated by livdywan over 3 years ago
- Subject changed from Disk I/O and job age schedule alerts to [epic] Disk I/O and job age schedule alerts
- Description updated (diff)
Updated by mkittler over 3 years ago
- Subject changed from [epic] Disk I/O and job age schedule alerts to [epic] Failed systemd services and job age alerts
- Description updated (diff)
Updated by livdywan over 3 years ago
- Related to action #96710: Error `Can't call method "write" on an undefined value` shows up in worker log leading to incompletes added
Updated by livdywan over 3 years ago
- Related to action #96557: jobs run into MAX_SETUP_TIME, one hour between 'Downloading' and 'Download processed' and no useful output in between auto_review:"timeout: setup exceeded MAX_SETUP_TIME":retry added
Updated by livdywan over 3 years ago
- Related to action #96552: Persistent records of I/O usage by process size:M added
Updated by mkittler about 3 years ago
Not sure how workable this ticket is. There's only one point left of the ones mentioned under observation and retrospectively it is hard to tell what was wrong at the time and we handled future alerts of the same kind. I get that this is an epic but the ticket title and description don't relate with the remaining sub tasks in a meaningful way.
Updated by okurz about 3 years ago
- Related to action #99246: Published QCOW images appear to be uncompressed added
Updated by okurz about 3 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
Looks like this could also be related to #99246 . I think see have all the mentioned ideas covered in follow up tasks or resolved already. Tracking remaining subtask
Updated by okurz almost 3 years ago
- Status changed from Blocked to Resolved
All subtasks resolved, all tasks and goals covered.