Opened 7 years ago

Closed 7 years ago

#5488 closed Bug/Something is broken (fixed)

Restarted apache on tresca

Reported by: Nat Meysenburg Owned by: Nat Meysenburg
Priority: Medium Component: Tech
Keywords: tresca apache Cc:
Sensitive: no

Description

Last night a Nagios warning about tresca HTTP went out. Here's the message as relayed to IRC:

21:38 < bender> [Nagios] - tresca HTTP CRITICAL

I logged in to tresca around an hour and a half later (when I noticed the alert, but no corresponding OK notice). Looking around on tresca, I didn't see anything too out of the ordinary -- plenty of memory, no CPU or disk contention, no lag with login.

Though my http connection to tresca.mayfirst.org was never completing.

The one thing out of place was ~40 stalled apache processes that were all of roughly the age of the nagios alert. Assuming that this meant there was a stuck apache process (or several), and that apache hadn't cleared it up in an hour and a half, I went ahead and restarted apache.

That brought me a tresca.mayfirst.org test page (quickly), and this nagios alert:

23:01 < bender> [Nagios] - tresca HTTP OK

I'm assuming that cleared up the issue.

Change History (1)

comment:1 Changed 7 years ago by Nat Meysenburg

Resolution: fixed
Status: newclosed

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.