Closed
Bug 1019051
Opened 10 years ago
Closed 10 years ago
SVN isn't synced with getfirebug.com
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Honza, Unassigned)
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/180] [firebug-p1])
I have done some image updates and I still can't see them live on getfirebug.com (it's been about 6 hours since the first commit) Here is getfirebug.com SVN: http://svn.mozilla.org/projects/getfirebug.com/tags/production Should be synced with: http://getfirebug.com --- Can anyone have a look please? Honza
Reporter | ||
Comment 1•10 years ago
|
||
I am marking as firebug-p1 since it's blocking our Firebug 2 release (we need to update the site before the release) Honza
Whiteboard: [firebug-p1]
Comment 2•10 years ago
|
||
Updating code... svn: warning: W155019: Cannot relocate '/data/genericrhel6/src/blog.getfirebug.com/wordpress/getfirebug_content/plugins/akismet' as it is not the root of a working copy; try relocating '/data/genericrhel6/src/blog.getfirebug.com/wordpress/getfirebug_content' instead svn: E205011: Failure occurred processing one or more externals definitions Gonna move over to WebOps since it's not a VCS issue and I'm not at all familiar with the wordpress stuff.
Component: WebOps: Source Control → WebOps: Other
Comment 3•10 years ago
|
||
:fubar - you were looking at blog.getfirebug.com, not getfirebug.com. the following is the error we're seeing and is why this isn't updating... [root@genericadm.private.phx1 getfirebug]# svn up svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted [root@genericadm.private.phx1 getfirebug]# svn cleanup svn: E000018: Can't move '/data/genericrhel6/src/getfirebug.com/getfirebug/.svn/tmp/svn-KRk0uN' to '/data/genericrhel6/src/getfirebug.com/getfirebug/perch/resources/enablingfirebug.png': Invalid cross-device link i did a little google searching about this error and might have hit a pretty big issue as result of this feature in subversion 1.7 -> http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng i just tried to do a fresh svn co and push to prod, but when that was deployed the site was malformed. i haven't gotten to the root of either of those, but i do find it odd that i cannot deploy a fresh svn co.
Comment 4•10 years ago
|
||
Aha, found the issue. A number of the files were symlinks to an NFS mount: lrwxrwxrwx 1 apache apache 43 Jun 4 09:12 ./perch/resources -> /mnt/netapp/getfirebug.com/perch/resources/ lrwxrwxrwx 1 apache apache 32 Jun 4 09:12 ./cache -> /mnt/netapp/getfirebug.com/cache lrwxrwxrwx 1 root root 9 Jun 4 09:12 ./releases/swarms -> ../swarms lrwxrwxrwx 1 apache apache 38 Jun 4 09:12 ./wiki/cache -> /mnt/netapp/getfirebug.com/wiki/cache/ lrwxrwxrwx 1 apache apache 38 Jun 4 09:12 ./wiki/images -> /mnt/netapp/getfirebug.com/wiki/images 'svn cleanup' works after removing them, and then 'svn up' recreates some of them: Updating '.': Restored 'cache' Restored 'perch/resources/cl-thumb.gif' Restored 'perch/resources/errors.gif' ... Restored 'wiki/cache' Restored 'wiki/cache/.htaccess' The following are NOT re-created: releases/swarms wiki/images I've put back the missing symlinks for the moment. The site doesn't appear to be broken, but I haven't a clue how important those links are, or whether it should be using the data from SVN or the NFS mount. Honza, can you verify the site is ok and provide input on the links?
Flags: needinfo?(odvarko)
Reporter | ||
Comment 5•10 years ago
|
||
Thanks the syncing now works! (all the images are live) > Restored 'cache' > Restored 'perch/resources/cl-thumb.gif' > Restored 'perch/resources/errors.gif' > Restored 'wiki/cache' > Restored 'wiki/cache/.htaccess' Hm..., I don't know why these files are there, but I tend to agree that they can be removed. > releases/swarms This directory is needed. But I don't understand what you mean by "NOT re-created". I can still see it... One more problem with Perch (the CMS for getfirebug.com), when I am trying to upload an image there is an error message: Your resources folder is not writable. Make this folder (/perch/resources) writable if you want to upload files and images. (it's not new I know the problem has been there for some time). Honza
Flags: needinfo?(odvarko)
Comment 6•10 years ago
|
||
(In reply to Jan Honza Odvarko from comment #5) > Your resources folder is not writable. Make this folder (/perch/resources) > writable if you want to upload files and images. > > (it's not new I know the problem has been there for some time). i pushed a change to the user permissions on this directory for you. let us know if that gets you back on track with writable access to /perch/resource
Flags: needinfo?(odvarko)
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to Chris Turra [:cturra] from comment #6) > i pushed a change to the user permissions on this directory for you. let us > know if that gets you back on track with writable access to /perch/resource Works like a charm, thanks Chris! I think this bug can be closed. Honza
Flags: needinfo?(odvarko)
Comment 8•10 years ago
|
||
Ignore what I said about releases/swarms. It's not a cross-device link like the others, and it's still there as expected. I suspect that the symlinks for cache and wiki/cache were there to share the data across the web heads. Willing to bet the same for wiki/images. I'm not sure what is the best way to maintain those links, but they should probably be there. Maybe the deploy script could recreate them?
Updated•10 years ago
|
Whiteboard: [firebug-p1] → [kanban:https://kanbanize.com/ctrl_board/4/180] [firebug-p1]
Reporter | ||
Comment 9•10 years ago
|
||
I have done some more commits (last week) to getfirebug.com SVN and they are still not online. http://svn.mozilla.org/projects/getfirebug.com/tags/production Revision: 129555 Author: odvarko@gmail.com Date: 13:00:06, 11. června 2014 Message: Fix install link and feed.png image ---- Modified : /projects/getfirebug.com/tags/production/blog/wp-content/themes/firebug/footer.html Modified : /projects/getfirebug.com/tags/production/blog/wp-content/themes/firebug/footer.php Modified : /projects/getfirebug.com/tags/production/blog/wp-content/themes/firebug/index.php Modified : /projects/getfirebug.com/tags/production/blog/wp-content/themes/firebug/sidebar.php The commit should fix broken image and line at the bottom of this page: https://blog.getfirebug.com/ Honza
Reporter | ||
Comment 10•10 years ago
|
||
My previous comment could be related to bug 941621 Honza
Comment 11•10 years ago
|
||
I made some changes to https://getfirebug.com/testresults/ yesterday, though they are not synced yet. @gozer: How is the kanban link related to this issue? Sebastian
Reporter | ||
Comment 12•10 years ago
|
||
Hi, we have more and more troubles with this. New Firebug release is not even online :-( Could somebody please make this a priority? Thanks! Honza
Comment 13•10 years ago
|
||
:Honza - it looks like there was a lock file left over from a previous run causing the cron to "hang." i have manually cleaned that up and ran the update for you to get the latest release out. can you please confirm everything looks as expected now?
Flags: needinfo?(odvarko)
Reporter | ||
Comment 14•10 years ago
|
||
(In reply to Chris Turra [:cturra] from comment #13) > :Honza - it looks like there was a lock file left over from a previous run > causing the cron to "hang." i have manually cleaned that up and ran the > update for you to get the latest release out. can you please confirm > everything looks as expected now? Both firebug-2.0.4.xpi and firebug-2.0.4b1.xpi are now online, thanks! Sebastian, are your changes visible now? Honza
Flags: needinfo?(odvarko) → needinfo?(sebastianzartner)
Comment 15•10 years ago
|
||
Yes, my changes are online again and syncing works again. Thanks Chris! Sebastian
Flags: needinfo?(sebastianzartner)
Comment 16•10 years ago
|
||
thnx guys. i am going to mark this bug as r/fixed since it has been sorted. this does however seem like a reoccurring issue. if this happens again, please file a new bug and reference this one for background information. at this point, i don't see any obvious reasons why this would return, but history has shown otherwise and in a "broken" state, we can evaluate if something should be changed/done differently.
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Windows 7 → All
Hardware: x86_64 → All
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•