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

Issue 682376 link

Starred by 1 user
Status: Fixed
Owner:
lazyboy@chromium.org
Closed: Jan 2017
Cc:
█ roc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Docserver not updating again

Project Member Reported by lazyboy@chromium.org, Jan 18 2017 
I just noticed
https://developer.chrome.com/apps/manifest/sandbox
has not updated to my CL:
https://chromium.googlesource.com/chromium/src/+/c0304f6696623d76672a4c8fbefa16378c3137b8

https://developer.chrome.com/_query_commit/master
is hinting stale docserver cache:
"""
Current commit: a7bb5795f41d2465fdd2dd5855fab304e166ea1b

Most recent commits:
2016-12-14 19:12:01.728898: a7bb5795f41d2465fdd2dd5855fab304e166ea1b
"""

That explains why the documentation is behind.

Started investigating the git-processor VM instance.

~/chrome/src git repo is up to date (Jan 18), however docserver cache is behind
ls -al ~/.docserver_cache
-rw-r--r-- 1 git-processor git-processor 392755857 Dec 14 19:13 /home/git-processor/.docserver_cache

Looking at /var/logs, git-processor has run ~/.update_docs.sh, but somehow
didn't update/write .docserver_cache. No obvious error logs I can find yet.

Will keep looking...

Comment 1 by lazyboy@chromium.org, Jan 19 2017

Cc: roc...@chromium.org
More fun, it seems the cron job to update cache didn't finish and it is holding file
lock (see updates-docs-full.sh for details):

ps -e -o  lstart,pid,ppid,cmd | grep update-docs
Sat Oct  1 15:00:00 2016 10230 10229 /bin/sh -c /usr/bin/env bash /home/git-processor/update-docs-full.sh 2>&1 | /usr/bin/logger
Sat Oct  1 15:00:00 2016 10231 10230 bash /home/git-processor/update-docs-full.sh
Wed Dec 14 19:50:01 2016 10744 10743 /bin/sh -c /usr/bin/env bash /home/git-processor/update-docs-full.sh 2>&1 | /usr/bin/logger [1]
Wed Dec 14 19:50:01 2016 10745 10744 bash /home/git-processor/update-docs-full.sh

[1] One instance is still running from around the time (Dec 14) cache stopped updating.

Talked to rockot@ about killing process 10744, sounds safe (what could go wrong? ;)),
so that cache update can continue.

Comment 2 by lazyboy@chromium.org, Jan 19 2017 

Killed them (comment #1), now will wait for cron to start the update script and hopefully cache will be updated and fixed.

Why the script hanged is still unknown. Ken says he has seen that happening before too.

Comment 3 by lazyboy@chromium.org, Jan 19 2017

Status: Fixed (was: Started)
Turned out just killing those processes wasn't enough, processes arriving later weren't able to get hold of the lock, so I deleted the lock file. It just finished one update cache run and docs are updated again!

Comment 4 by rdevlin....@chromium.org, Jan 23 2017 

Glad it's updating again.  If this is closed, should we file a separate bug for investigating why the script didn't finish in the first place?  Or should we reopen this?
Project Member

Comment 5 by bugdroid1@chromium.org, Jan 23 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/160744aec412ad50764ad679d6ef050d671c56a9

commit 160744aec412ad50764ad679d6ef050d671c56a9
Author: lazyboy <lazyboy@chromium.org>
Date: Mon Jan 23 22:42:58 2017

Add some documentation about docserver VM troubleshooting.

I'm summarizing mostly what I've done yesterday to diagnose crbug 682376.

BUG= 682376 

Review-Url: https://codereview.chromium.org/2646443009
Cr-Commit-Position: refs/heads/master@{#445522}

[modify] https://crrev.com/160744aec412ad50764ad679d6ef050d671c56a9/chrome/common/extensions/docs/server2/README
►

Sign in to add a comment