New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 701980 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chromeos-server18.cbf: Resurrect sentinel_service, add ts_mon metrics.

Project Member Reported by dgarr...@chromium.org, Mar 15 2017

Issue description

**** Nagios *****

Notification Type: PROBLEM
Host: chromeos-server18.cbf
State: DOWN
Address: 172.25.66.231
Info: PING CRITICAL - Packet loss = 100%

Date/Time: Tue Mar 14 12:32:15 PDT 2017


Should we stop checking to see if this server is down?

Or do we need to fix it?
 
Cc: -xixuan@chromium.org dshi@chromium.org
Owner: xixuan@chromium.org
chromeos-server18.cbf is already removed nagios, we need a nagios configuration update to take effect the change, assign to deputy.
Owner: pprabhu@chromium.org
Status: Verified (was: Untriaged)
Prathmesh restarted the nagios server, and no new alerts have been generated.

Comment 3 by xixuan@chromium.org, Mar 16 2017

oh smart. How to do it? any document for nagios?

Comment 5 by dshi@chromium.org, Mar 16 2017

Status: Assigned (was: Verified)
Just saw this bug. do we no longer care about db consistency? sentinel service is running in that server.
Cc: akes...@chromium.org
Owner: shuqianz@chromium.org
Owner: pprabhu@chromium.org
Summary: chromeos-server18.cbf: Resurrect sentinel_service, add ts_mon metrics. (was: ** PROBLEM Host Alert: chromeos-server18.cbf is DOWN **)
Labels: -Pri-2 Pri-1
The Nagios alerts for this service are still being generated, though they did stop for a while.
***** Nagios *****

Notification Type: PROBLEM
Host: chromeos-server18.cbf
State: DOWN
Address: 172.25.66.231
Info: PING CRITICAL - Packet loss = 100%

Date/Time: Fri Mar 17 09:00:30 PDT 2017
Labels: -current-issue
Mergedinto: 701471
Status: Duplicate (was: Assigned)

Sign in to add a comment