Last modified: 2014-06-02 13:46:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67978, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65978 - Pageviews dumps stalled
Pageviews dumps stalled
Status: RESOLVED FIXED
Product: Analytics
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: High major
: ---
Assigned To: christian
u=caistleitner@wikimedia.org c=Genera...
: ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-31 17:23 UTC by metatron
Modified: 2014-06-02 13:46 UTC (History)
11 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description metatron 2014-05-31 17:23:19 UTC
Pageviews dumps dried out. Last dump provided:  pagecounts-20140530-150000
Comment 1 Andre Klapper 2014-05-31 21:24:07 UTC
metatron: Please provide a URL to reproduce / see the problem.
I assume this is some page somewhere on http://dumps.wikimedia.org/
Comment 3 christian 2014-06-02 07:36:18 UTC
The files are still there on gadolinium, so it looks like we're not loosing data,
but "only" copying the data files around is failing.
Comment 4 Gerrit Notification Bot 2014-06-02 09:28:22 UTC
Change 136735 had a related patch set uploaded by QChris:
Provide default shell to datasets user

https://gerrit.wikimedia.org/r/136735
Comment 5 Gerrit Notification Bot 2014-06-02 09:30:12 UTC
Change 136735 abandoned by QChris:
Provide default shell to datasets user

Reason:
Beaten by Change 136734

https://gerrit.wikimedia.org/r/136735
Comment 6 christian 2014-06-02 09:35:52 UTC
It seems Ops' cleanup around accounts reset the datasets user's shell,
so rsync failed. Apergos set rsync's shell again in

  https://gerrit.wikimedia.org/r/#/c/136734

. That should fix the issue upon the next cron run and bring the missing
files over.
I'll report back when that happened.
Comment 7 christian 2014-06-02 10:39:08 UTC
The fix worked.
Files are back.
No missing data.
Comment 8 Andrew Otto 2014-06-02 13:46:26 UTC
Thanks Christian and Ariel (and all)!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links