Actions
action #170083
closed[FIRING:1] (Failed systemd services alert (except openqa.suse.de) Salt Uk02cifVkz) backup-qam failing unit "ypbind" since 2024-11-19 0818Z
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2024-11-19
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
From https://stats.openqa-monitor.qa.suse.de/d/KToPYLEWz/failed-systemd-services
On backup-qam "ypbind" failed since 2024-11-19 0818Z. Maybe a delayed effect due to CC-related network changes
Updated by okurz 3 months ago
- Status changed from New to In Progress
- Priority changed from Urgent to Normal
# journalctl -u ypbind.service
Nov 17 03:31:47 backup-qam systemd[1]: Starting NIS/YP Clients to NIS Domain Binder...
Nov 17 03:33:23 backup-qam systemd[1]: ypbind.service: start-post operation timed out. Terminating.
Nov 17 03:33:23 backup-qam ypbind-systemd-post[2038]: . . . . . .
Nov 17 03:33:23 backup-qam systemd[1]: ypbind.service: Control process exited, code=killed, status=15/TERM
Nov 17 03:33:23 backup-qam systemd[1]: ypbind.service: Failed with result 'timeout'.
Nov 17 03:33:23 backup-qam systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder.
A restart of the service was going fine, reducing prio. Trying to reproduce with reboot or similar.
Actions