Mauro, Glad you're back up and running, I'd suggest trying the remote cache again sometime once you feel confident that it's working well without it. Sounds like it was some old repository making problems!
- Lee On Wednesday, March 14, 2012 at 11:58 AM, Mauro Asprea wrote: > Thanks Lee, I checked the remotes in the server and also removed all old > deployed releases. Now it works at least without remote_cache > > On Friday, 9 March 2012 12:26:15 UTC+1, Lee Hambley wrote: > > Mauro, > > > > I have seen something similar when the remote wasn't changed everywhere, > > just for example on the server, but not locally. Cap relies on your > > workstation and the server both finding the same value for HEAD. Check that > > both your server, and your local machine have the same remotes. When you're > > not using remote_cache, also check that the checked out copy in > > `current_release` has the new remote. > > > > Other than that, check you don't have some buggy/old version of Git on your > > server (1.7.1 looks ok, but what did they fix in the releases up to .6 ?) > > > > - lee > > > > On Friday, March 9, 2012 at 12:16 PM, Mauro Asprea wrote: > > > > > Deploying from Snow Leopard: > > > ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin10.8.0] > > > git version 1.7.6 > > > > > > To CentOS 5 > > > ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux] > > > git version 1.7.1 > > > > > > Rails 3.2.2 > > > > > > On Friday, 9 March 2012 12:11:18 UTC+1, Mauro Asprea wrote: > > > > Weeks ago I have changed the remote git url repo, pull updates into the > > > > "remote_cache" in my server and everything seemed to be working. But > > > > every 2 or 3 "cap deploy" I can see that somewhere capistrano is > > > > failing to fetch the HEAD commit. What I'm seeing is that from time to > > > > time it goes nuts and it tries to deploy the Last "old remote" commit. > > > > Even after I have disabled the "remote_cache" option and deleted the > > > > /shared/cache_copy directory from the server. > > > > > > > > right now I'm just reading the hash deployed and I cancel it if it is > > > > incorrect. And retry. This usually works. > > > > > > > > Ideas? > > > > > > On Friday, 9 March 2012 12:11:18 UTC+1, Mauro Asprea wrote: > > > > Weeks ago I have changed the remote git url repo, pull updates into the > > > > "remote_cache" in my server and everything seemed to be working. But > > > > every 2 or 3 "cap deploy" I can see that somewhere capistrano is > > > > failing to fetch the HEAD commit. What I'm seeing is that from time to > > > > time it goes nuts and it tries to deploy the Last "old remote" commit. > > > > Even after I have disabled the "remote_cache" option and deleted the > > > > /shared/cache_copy directory from the server. > > > > > > > > right now I'm just reading the hash deployed and I cancel it if it is > > > > incorrect. And retry. This usually works. > > > > > > > > Ideas? > > > -- > > > * You received this message because you are subscribed to the Google > > > Groups "Capistrano" group. > > > * To post to this group, send email to [email protected] > > > (mailto:[email protected]) > > > * To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:[email protected]) For more options, visit > > > this group at http://groups.google.com/group/capistrano?hl=en > > > > On Friday, 9 March 2012 12:26:15 UTC+1, Lee Hambley wrote: > > Mauro, > > > > I have seen something similar when the remote wasn't changed everywhere, > > just for example on the server, but not locally. Cap relies on your > > workstation and the server both finding the same value for HEAD. Check that > > both your server, and your local machine have the same remotes. When you're > > not using remote_cache, also check that the checked out copy in > > `current_release` has the new remote. > > > > Other than that, check you don't have some buggy/old version of Git on your > > server (1.7.1 looks ok, but what did they fix in the releases up to .6 ?) > > > > - lee > > > > On Friday, March 9, 2012 at 12:16 PM, Mauro Asprea wrote: > > > > > Deploying from Snow Leopard: > > > ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin10.8.0] > > > git version 1.7.6 > > > > > > To CentOS 5 > > > ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux] > > > git version 1.7.1 > > > > > > Rails 3.2.2 > > > > > > On Friday, 9 March 2012 12:11:18 UTC+1, Mauro Asprea wrote: > > > > Weeks ago I have changed the remote git url repo, pull updates into the > > > > "remote_cache" in my server and everything seemed to be working. But > > > > every 2 or 3 "cap deploy" I can see that somewhere capistrano is > > > > failing to fetch the HEAD commit. What I'm seeing is that from time to > > > > time it goes nuts and it tries to deploy the Last "old remote" commit. > > > > Even after I have disabled the "remote_cache" option and deleted the > > > > /shared/cache_copy directory from the server. > > > > > > > > right now I'm just reading the hash deployed and I cancel it if it is > > > > incorrect. And retry. This usually works. > > > > > > > > Ideas? > > > > > > On Friday, 9 March 2012 12:11:18 UTC+1, Mauro Asprea wrote: > > > > Weeks ago I have changed the remote git url repo, pull updates into the > > > > "remote_cache" in my server and everything seemed to be working. But > > > > every 2 or 3 "cap deploy" I can see that somewhere capistrano is > > > > failing to fetch the HEAD commit. What I'm seeing is that from time to > > > > time it goes nuts and it tries to deploy the Last "old remote" commit. > > > > Even after I have disabled the "remote_cache" option and deleted the > > > > /shared/cache_copy directory from the server. > > > > > > > > right now I'm just reading the hash deployed and I cancel it if it is > > > > incorrect. And retry. This usually works. > > > > > > > > Ideas? > > > -- > > > * You received this message because you are subscribed to the Google > > > Groups "Capistrano" group. > > > * To post to this group, send email to [email protected] > > > (mailto:[email protected]) > > > * To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:[email protected]) For more options, visit > > > this group at http://groups.google.com/group/capistrano?hl=en > > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > (mailto:[email protected]) > * To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]) For more options, visit this > group at http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
