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

Issue 696732 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Check whether there're more devserver out of disk space

Project Member Reported by johndhong@chromium.org, Feb 27 2017

Issue description

Something is going with this devserver and it is almost full...

chromeos-test@chromeos4-devserver2:~/images$ df -h
Filesystem                                  Size  Used Avail Use% Mounted on
/dev/mapper/chromeos4--devserver2--vg-root  5.4T  5.1T   15G 100% /

If this is the new normal then I'm going to need to order more equipment.
 

Comment 1 by xixuan@chromium.org, Feb 27 2017

It's the second time that we find a devserver without any space because it doesn't run repo sync.

I will fix this devserver first, then check all devservers to see whether they has this problem.

Comment 3 by xixuan@chromium.org, Feb 27 2017

Summary: Check whether there're more devserver out of disk space (was: chromeos4-devserver2 is out of disk space)
this devserver should be good now.

I will change the intent of this bug to 'check whether we still have out-of-disk-space devservers'.

Comment 4 by xixuan@chromium.org, Feb 28 2017

Based on all devserver's disk usage and my checking on the top-N devservers, I believe there's no devserver suffering full disk problem.

172.25.65.217 usage is: 0.2
100.115.219.133 usage is: 0.16
100.115.219.134 usage is: 0.15
100.115.219.132 usage is: 0.14
100.115.219.131 usage is: 0.14
100.115.219.130 usage is: 0.03
172.24.184.161 usage is: 0.01
100.107.126.160 usage is: 0.01
172.27.215.252 usage is: 0.01
100.115.219.136 usage is: 0.01
100.115.219.135 usage is: 0.01
100.115.185.228 usage is: 0.01
172.22.39.163 usage is: 0.01
100.107.126.164 usage is: 0.01
100.107.126.165 usage is: 0.01
172.24.184.160 usage is: 0.01
100.120.7.236 usage is: 0.01
100.115.185.227 usage is: 0.01
100.115.185.226 usage is: 0.01
100.107.126.162 usage is: 0.01
100.107.126.163 usage is: 0.01
100.115.99.246 usage is: 0.01
100.115.99.247 usage is: 0.01
100.115.245.198 usage is: 0.01
100.115.245.197 usage is: 0.01
100.115.99.249 usage is: 0.01
100.107.225.252 usage is: 0.01
172.25.65.235 usage is: 0.01
172.27.215.245 usage is: 0.01
100.107.227.251 usage is: 0.01
100.107.227.252 usage is: 0.01
172.27.215.246 usage is: 0.01
100.115.219.129 usage is: 0.01
172.27.215.249 usage is: 0.01
100.115.99.236 usage is: 0.01
100.107.126.159 usage is: 0.01
172.25.65.106 usage is: 0.01
100.115.24.253 usage is: 0.01
100.107.126.137 usage is: 0.01
100.107.126.136 usage is: 0.01
100.107.225.251 usage is: 0.01
100.115.245.200 usage is: 0.01
172.22.39.162 usage is: 0.01
100.120.7.235 usage is: 0.01
172.22.39.161 usage is: 0.01
100.115.99.251 usage is: 0.01
100.115.99.250 usage is: 0.01
172.22.39.164 usage is: 0.01
100.115.99.252 usage is: 0.01

Furthermore I find a list of devservers which cannot be sshed:
'100.107.127.227', '100.107.127.228', '100.107.127.229', '172.24.190.169', '172.27.215.248'], one of which is involved in apache's error log: Issue 696783. 

Could I have englab to check whether we can remove these devservers from prod?
Cc: dschimmels@chromium.org
englab-sys-cros' devservers are start with 100.115.x.x so those might be under the control of dschimmel's team
Hi,

You may remove 100.107.127.227, 100.107.127.228, 100.107.127.229 and 172.27.215.248.

I do not know this one 172.24.190.169

Thanks
David

172.24.190.169 = chromeos-server59.hot.corp.google.com.
I'm assuming there was an experiment using ganeti instances as devservers....

Project Member

Comment 8 by bugdroid1@chromium.org, Feb 28 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/a61a765bf01230409dfece7e3e6903fad75466aa

commit a61a765bf01230409dfece7e3e6903fad75466aa
Author: xixuan <xixuan@chromium.org>
Date: Tue Feb 28 07:07:58 2017

Project Member

Comment 9 by bugdroid1@chromium.org, Feb 28 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/a61a765bf01230409dfece7e3e6903fad75466aa

commit a61a765bf01230409dfece7e3e6903fad75466aa
Author: xixuan <xixuan@chromium.org>
Date: Tue Feb 28 07:07:58 2017

Cc: akes...@chromium.org
Cc: pho...@chromium.org
This is a good candidate for an alert. We want the alert only for in-lab devservers (IP address starts with 100 rather than 172).
Hi, @dschimmels, is 100.115.24.253 still used?
To clarify my 100.115.x.x statement
2081 uses 100.115.128.1 to 100.115.255.254

2081 Devservers specifically use 
100.115.185.225 - 100.115.185.254
100.115.219.129 - 100.115.219.158
100.115.245.193 - 100.115.245.222
I will remove 100.115.24.253 if no one have comments in 10 minutes... since this devserver is not well configured (need password to ssh in devserver push). I assume it cannot be used in such configuration.
Cc: nsylvain@chromium.org jerrycorrigan@google.com
100.115.24.253 is vrlab-autotest-dev1.mtv


Nicolas can you help these guys figure out why your devserver requires a password?
Project Member

Comment 16 by bugdroid1@chromium.org, Mar 1 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/c3f9c12164e62775421bdfac513e70099a2da99d

commit c3f9c12164e62775421bdfac513e70099a2da99d
Author: Dan Shi <dshi@google.com>
Date: Wed Mar 01 19:54:15 2017

Project Member

Comment 17 by bugdroid1@chromium.org, Mar 1 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/c3f9c12164e62775421bdfac513e70099a2da99d

commit c3f9c12164e62775421bdfac513e70099a2da99d
Author: Dan Shi <dshi@google.com>
Date: Wed Mar 01 19:54:15 2017

Project Member

Comment 18 by bugdroid1@chromium.org, Mar 1 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/fd4f4cda16007548afb231f9d88a00c82b4b2251

commit fd4f4cda16007548afb231f9d88a00c82b4b2251
Author: xixuan <xixuan@chromium.org>
Date: Wed Mar 01 20:05:20 2017

Update:

100.115.24.253 is set back to use port 8082 (its 8080 is still listening by redirection), sysmon is running again, and puppet update is set.
Status: Fixed (was: Untriaged)

Comment 21 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 23 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment