Closed
Bug 399491
Opened 17 years ago
Closed 17 years ago
litmus.mozilla.org is down
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: marcia, Assigned: coop)
Details
I am getting unable to connect errors.
Comment 1•17 years ago
|
||
Verified, I get the same.
Comment 2•17 years ago
|
||
From the logs:
[Thu Oct 11 12:53:07 2007] [notice] caught SIGTERM, shutting down
Oct 11 12:53:08 dm-litmus01 httpd: httpd shutdown succeeded
Looks like someone shut it down manually.
Zach/coop?
Updated•17 years ago
|
Group: infra
Updated•17 years ago
|
Component: Server Operations: Tinderbox Maintenance → Server Operations
Comment 3•17 years ago
|
||
13:33:19 < justdave> coop: see bug 399491 if you haven't already. I see you doing stuff on the shell, is that your doing?
13:33:35 < coop> yes, that's me
Assignee: server-ops → ccooper
Component: Server Operations → Server Operations: Tinderbox Maintenance
Updated•17 years ago
|
Component: Server Operations: Tinderbox Maintenance → Server Operations
Assignee | ||
Comment 4•17 years ago
|
||
Yes, I'm landing bug 320156. Should be back in ~5min.
Status: NEW → ASSIGNED
Comment 5•17 years ago
|
||
Should we be tagging downtime like this in nagios to avoid setting off alarms and wasting sysadmins' time? I don't think I have access to do so in nagios--coop might?
Assignee | ||
Comment 6•17 years ago
|
||
(In reply to comment #5)
> Should we be tagging downtime like this in nagios to avoid setting off alarms
> and wasting sysadmins' time? I don't think I have access to do so in
> nagios--coop might?
Perhaps. Is the nagios script for Litmus in CVS?
(Litmus is back up now, BTW)
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•