Closed Bug 1119249 Opened 9 years ago Closed 9 years ago

dc8.releng.ad.mozilla.com:Windows Memory is WARNING

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rwatson, Assigned: q)

Details

(Whiteboard: [windows])

I had some alerts today for dc8.releng.ad.mozilla.com. I had a poke around and svchost.exe was using up a lot of resources. Can't see anything actionable without digging deeper.
It appears to be stable but is still alerting, can someone take a look?
Assignee: relops → q
Hey Q, I poked at this for a few minutes. It looked like it was the aelookup service was using a large portion of mem. I killed the service and restarted it. The overall mem usage dropped from 83% to 78% and then rose back to 80%. The mem usage seems stable and not climbing at the moment.
Sat 19:09:29 PDT [4040] dc8.releng.ad.mozilla.com:Windows Memory is WARNING: WARNING: physical memory: Total: 6G - Used: 5.1G (85%) - Free: 917M (15%)
Status: NEW → ASSIGNED
Memory cleared and wsus configured to go to wsus01 which should avoid this in the future
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Got this. Host is responsive.


20:24:21 <nagios-releng> Sat 20:24:20 PDT [4192] dc8.releng.ad.mozilla.com:disk - C is CRITICAL: (Return code of 255 is out of bounds) (http://m.mozilla.org/disk+-+C)
20:27:51 <nagios-releng> Sat 20:27:51 PDT [4194] dc8.releng.ad.mozilla.com:Windows Memory is CRITICAL: (Return code of 255 is out of bounds) (http://m.mozilla.org/Windows+Memory)
20:31:11 <nagios-releng> Sat 20:31:11 PDT [4196] dc8.releng.ad.mozilla.com:Windows CPU is CRITICAL: (Return code of 255 is out of bounds) (http://m.mozilla.org/Windows+CPU)
20:32:50 <nagios-releng> Sat 20:32:50 PDT [4198] dc8.releng.ad.mozilla.com:Windows Memory is CRITICAL: (Return code of 255 is out of bounds) (http://m.mozilla.org/Windows+Memory)
20:36:20 <nagios-releng> Sat 20:36:20 PDT [4200] dc8.releng.ad.mozilla.com:Windows CPU is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. (http://m.mozilla.org/Windows+CPU)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Looks like this recovered on it's own, not sure what the intermittent issue was.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Whiteboard: [windows]
You need to log in before you can comment on or make changes to this bug.