Not sure what just happened. The db server freaked out for about a half hour: Time (UTC) runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 06:30:01 AM 0 157 1.00 1.27 1.70 06:40:06 AM 0 275 62.13 26.97 11.17 06:50:07 AM 0 270 52.43 55.90 35.88 07:00:06 AM 1 235 36.48 43.22 39.26 07:10:01 AM 0 169 1.96 17.56 29.83 Time (UTC) pswpin/s pswpout/s 06:40:06 AM 0.00 0.07 06:50:07 AM 717.03 803.21 07:00:06 AM 381.30 46.78 07:10:01 AM 82.42 0.67 By the time I got the alerts and got to my workstation everything was fine. Something to keep an eye on.. -Mike ---------- Forwarded message ---------- Date: Wed, 30 Apr 2008 06:42:08 GMT From: Nagios Monitoring User <nagios@xxxxxxxxxxxxxxxxx> To: sysadmin-members@xxxxxxxxxxxxxxxxx Subject: ** PROBLEM alert - 209.132.176.98-phx/koji is CRITICAL ** ***** Nagios ***** Notification Type: PROBLEM Service: koji Host: 209.132.176.98-phx Address: 209.132.176.98 State: CRITICAL Date/Time: Wed Apr 30 06:42:08 UTC 2008 Additional Info: CRITICAL - Socket timeout after 29 seconds _______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
