Closed Bug 678527 Opened 13 years ago Closed 13 years ago

MXR not updating in > 2 weeks

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: khuey, Assigned: justdave)

References

Details

MXR for mozilla-central hasn't updated since before the beginning of the month.
Do you have an exact date?
Well, I have a lower bound.

http://hg.mozilla.org/mozilla-central/pushloghtml?changeset=eee7a94c44e2 was pushed on July 28th and added browser/devtools, which is not in MXR.
If I write a shell script that returns a success code for a fresh-enough mozilla-central database, and a failure code for one that's too old, will someone wire it into nagios for us?
the fix for this has more to do with bug 676432 and the fact that glimpse is not able to finish indexing..  I/O is hanging too much

We are working a -possible- issue with Dell that may be to blame for this, MXR slowness, and Tinderbox issues.  No ETA but we are working on it as we speak.
Assignee: server-ops → cshields
fwiw, this is something of a blocker for developer documentation work, since all our tools and processes are centered around MXR.
(In reply to Eric Shepherd [:sheppy] from comment #6)
> fwiw, this is something of a blocker for developer documentation work, since
> all our tools and processes are centered around MXR.

We've been focused on fixing tinderbox first, since that has been something of a blocker to, well, development..

the issue behind tinderbox and mxr are the same, and data for mxr is being moved to trays that are not oversubscribed as we speak.
(In reply to Corey Shields [:cshields] from comment #7)
> (In reply to Eric Shepherd [:sheppy] from comment #6)
> > fwiw, this is something of a blocker for developer documentation work, since
> > all our tools and processes are centered around MXR.
> 
> We've been focused on fixing tinderbox first, since that has been something
> of a blocker to, well, development..

Ah, I hadn't been aware that tinderbox is broken (I don't use it personally). Obviously that's the priority, yes.
Yeah..  I haven't been updating everything too clearly either (sorry - we have been a couple of people down and I've been dealing with this issue while traveling to do interviews and new hire training)..  I'll toss an update into 676432 since that is the more relevant to the root problem.
Is this still out of date?  How do I test?

I don't see the cron jobs stuck per se but if we are out of date still I will kill them all off and this should resolve itself within a day.
We're still out of date.  My test has been to load http://mxr.mozilla.org/mozilla-central/source/browser/ and see if there's a 'devtools' directory in there.
I have run the index updates by hand (both the nightly and the */4 hr cron) and although they succeed, devtools is not showing up.

Going to ask justdave for help on this one, I believe he has more tribal knowledge on MXR.
[root@dm-webtools04 mozilla-central]# cat cvs.log
Thu Aug 18 08:55:56 PDT 2011
/var/www/webtools/mxr
pulling from http://hg.mozilla.org/mozilla-central
searching for changes
abort: abandoned transaction found - run hg recover!
/data/mxr-data/mozilla-central/mozilla-central
982a5835fba1
Thu Aug 18 08:56:53 PDT 2011

So it's been stuck like that for who knows how long...
Running recover on it now.  I'll grep the logs for all the trees to see if this happened to any of the others.
[root@dm-webtools04 mozilla-central]# hg recover 
rolling back interrupted transaction
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
76980 files, 73041 changesets, 335599 total revisions

[root@dm-webtools04 mxr-data]# find . -maxdepth 2 -name cvs.log -exec grep -q 'hg recover' {} \; -print
./mozilla-central/cvs.log

And that appears to have been the only one.

I'm manually updating mozilla-central right now, should be up-to-date in an hour or so.
Assignee: cshields → justdave
http://mxr.mozilla.org/mozilla-central/source/browser/ is now up-to-date.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
(In reply to Dave Miller [:justdave] from comment #15)
> http://mxr.mozilla.org/mozilla-central/source/browser/ is now up-to-date.

You, sir, are my hero.
Status: RESOLVED → VERIFIED
Depends on: 704374
Depends on: 705760
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.