Closed Bug 476759 Opened 15 years ago Closed 15 years ago

SUMO staging server (support-stage.mozilla.org) no longer appears to be pulling from SVN trunk

Categories

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

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: stephend, Assigned: oremj)

Details

I don't think SUMO's staging server is auto-syncing to SVN trunk; see bug 474871, for instance, where http://viewvc.svn.mozilla.org/vc?view=rev&revision=21904 is checked in but not reflected on the server:

https://bugzilla.mozilla.org/show_bug.cgi?id=474871#c4.

Could someone from IT please see if it's still pulling from SUMO SVN trunk, and if so, that it's got the latest changes?

Thanks!
Severity: major → critical
Assignee: server-ops → phong
It should update every 10 min.  svn info shows:

svn info
Path: .
URL: http://svn.mozilla.org/projects/sumo/trunk
Repository Root: http://svn.mozilla.org
Repository UUID: 4eb1ac78-321c-0410-a911-ec516a8615a5
Revision: 22002
Node Kind: directory
Schedule: normal
Last Changed Author: lthomson@mozilla.com
Last Changed Rev: 22001
Last Changed Date: 2009-02-04 08:26:28 -0800 (Wed, 04 Feb 2009)
Hmm, something weird is going on then.
stephend: oh, SUMO seems to be working again
stephend: https://bugzilla.mozilla.org/show_bug.cgi?id=474871#c4 shows up again for me
firebot: stephend: Bug 474871 tri, --, 0.8.2, paul.craciunoiu@gmail.com, RESO FIXED, Wrong translation of the name of the language in the drop-down list
stephend: Russian is properly localized
stephend: figures; when I have IT look at it, it starts working again
laura: usually works 
laura: ok then
stephend: https://bugzilla.mozilla.org/show_bug.cgi?id=475468#c5 too
stephend: yeah
firebot: stephend: Bug 475468 nor, --, 0.8.2, paul.craciunoiu@gmail.com, RESO FIXED, remove white border from screenshots
laura: yes, and now https://support-stage.mozilla.org/tiki-editpage.php?page=*+food&quickedit=Edit works
laura: as per https://bugzilla.mozilla.org/show_bug.cgi?id=476366#c10

Wish we knew what happened (wasn't reflecting SVN commits for any of us), but I'm glad it's now working; thanks, IT.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Reopening. See bug 475131 comment 12. And bug 459087 comment 7.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee: phong → oremj
Trying to get some attention for this, has been reopened critical for 3 days now.  This is a blocker for stephend to QA any of our bugs.
Severity: critical → blocker
What's the action?  Last comment I saw was, "I'm glad it's now working"
I was told today it's not (via Stephen)...can you check it please?
I think this was not updating, because someone committed to a subdirectory of /trunk/ instead of /trunk/ itself.  It's a limitation of the update script.
(In reply to comment #8)
> I think this was not updating, because someone committed to a subdirectory of
> /trunk/ instead of /trunk/ itself.  It's a limitation of the update script.

Does that mean this is only temporarily fixed, and it'll happen again the next time someone does that?  If so, should this bug be morphed to fix the update script?
+1 for stephend's suggestion (changing the update script a tad).
The script does that, because if I cron svn up on all the staging apps the staging server is constantly io loaded.  By looking at the top level directory I avoid having to look through the whole file tree.  That's not quite the optimal scenario though.  I'll look at other options.
Oops, yeah I did not know about this. After we made the changes on the structure, to move the site into trunk/webroot, I usually commit from there. I'd be happy if you can update the script to work from /trunk and only immediate subdirectories (i.e. webroot and script, really) of trunk, at any rate.
Just a thought, maybe you can put two crons: one on trunk, as is, and one to run every so minutes anyway. That sounds like less load.
support-stage will receive a full svn up every 10 min.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
I still don't seem to have the staging server updated on my commits, and it's been 1h:30. See svn revision 22383
Subject: Cron <root@mrapp-stage02> /usr/local/bin/svn-up.sh /data/www/support-stage.mozilla.com HEAD
Date: Sat, 14 Feb 2009 22:40:01 -0800

Updating /data/www/support-stage.mozilla.com
UPDATE_DIR: /data/www/support-stage.mozilla.com
REVISION: HEAD
URL: http://svn.mozilla.org/projects/sumo/trunk
LOCAL_REV: 22194
REMOTE_REV: 22283
svn: Can't convert string from native encoding to 'UTF-8':
svn: ?\207?\128?\206?\177?\207?\129?\206?\172?\206?\184?\207?\133?\207?\129?\206?\191 ?\206?\187?\206?\172?\206?\184?\206?\191?\207?\133?\207?\130 AUS(200)1?\206?\188?\206?\185?\206?\186?\207?\129?\207?\140.jpg
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Verified FIXED; seen several fixes in the last few days and it's been fine.

Thanks again, oremj.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.