| Summary: | we should monitor more things such as servers' date | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Thierry Vignaud <thierry.vignaud> |
| Component: | Others | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | sysadmin-bugs, tmb |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Bug Depends on: | 7228 | ||
| Bug Blocks: | |||
|
Description
Thierry Vignaud
2012-08-29 10:41:34 CEST
Thierry Vignaud
2012-08-29 10:41:59 CEST
Depends on:
(none) =>
7228 We already do xymon monitoring wich alerts us on a separate list to not flood sysadm list, and sympa also notified us that it died when it lost db access. But as there was server maintenance in progress in the DC, there was no point in restarting services just to have them fail again. Status:
NEW =>
RESOLVED Do we monitor server's date too? Yep, for example head of a mail yesterday regarding valstar: yellow Tue Aug 28 14:37:48 CEST 2012 up: 18:07, 1 users, 203 procs, load=0.16 &yellow System clock is -7202 seconds off (max 60) |