Charlie,
If this was your first deploy, the restart will fail because there is
nothing to restart. You'll need to go in and manually fire up your
fcgi processes (or mongrel processes, or whatever you're using).
Subsequent restarts should work correctly after that.
- Jamis
On Jun 14, 2007, at 3:52 PM, charlie caroff wrote:
>
> Success? Below is my output, with what looks like what might be just
> a warning at the end. I'm looking on my remote server, and I see,
> under /releases, my working copy. I've got a simple mongrel setup on
> my remote server (for now), and when browse to my site, I can see it.
> WOO HOO
>
> I think I had two problems. First, the one you pointed out, Jamis,
> where I had, for my repository, /foo/bar, and I should have had /foo/
> bar/trunk
>
> I might have had a umask problem, too, where I set the umask for user
> svn on my local server to 002, but then su'd to other user names, and
> when I su'd back to svn, umask was reset to 022. So this time I made
> sure that I had umask set to 002 when I created my repository.
>
> Anyway, I think it looks good.
>
> Thanks very much, Jamis. I've never used deployment scripts like
> this, and I'm really looking forward to it.
>
> Charlie
>
> cap deploy:setup
> * executing `deploy:setup'
> * executing "umask 02 && mkdir -p /u/apps/project /u/apps/project/
> releases /u/apps/project/shared /u/apps/project/shared/system /u/apps/
> project/shared/log /u/apps/project/shared/pids"
> servers: ["www.project.com"]
> [www.project.com] executing command
> command finished
> [EMAIL PROTECTED] ~/project/trunk/config]$ cap deploy
> * executing `deploy'
> * executing `deploy:update'
> ** transaction: start
> * executing `deploy:update_code'
> * executing "svn checkout -q -r3 svn+ssh://[local ip]/usr/home/svn/
> repository/project/trunk /u/apps/project/releases/20070614213744 &&
> (echo 3 > /u/apps/project/releases/20070614213744/REVISION)"
> servers: ["www.project.com"]
> [www.project.com] executing command
> command finished
> * executing `deploy:finalize_update'
> * executing "chmod -R g+w /u/apps/project/releases/20070614213744"
> servers: ["www.project.com"]
> [www.project.com] executing command
> command finished
> * executing "rm -rf /u/apps/project/releases/20070614213744/log /u/
> apps/project/releases/20070614213744/public/system /u/apps/project/
> releases/20070614213744/tmp/pids &&\n ln -s /u/apps/project/
> shared/log /u/apps/project/releases/20070614213744/log &&\n ln -
> s /u/apps/project/shared/system /u/apps/project/releases/
> 20070614213744/public/system &&\n ln -s /u/apps/project/shared/
> pids /u/apps/project/releases/20070614213744/tmp/pids"
> servers: ["www.project.com"]
> [www.project.com] executing command
> command finished
> * executing "find /u/apps/project/releases/20070614213744/public/
> images /u/apps/project/releases/20070614213744/public/stylesheets /u/
> apps/project/releases/20070614213744/public/javascripts -exec touch -t
> 200706142138.03 {} \\;; true"
> servers: ["www.project.com"]
> [www.project.com] executing command
> command finished
> * executing `deploy:symlink'
> * executing "rm -f /u/apps/project/current && ln -s /u/apps/project/
> releases/20070614213744 /u/apps/project/current"
> servers: ["www.project.com"]
> [www.project.com] executing command
> command finished
> ** transaction: commit
> * executing `deploy:restart'
> * executing "sudo /u/apps/project/current/script/process/reaper"
> servers: ["www.project.com"]
> [www.project.com] executing command
> ** [out :: www.project.com] Couldn't find any pid file in '/u/apps/
> project/current/tmp/pids' matching 'dispatch.[0-9]*.pid'
> ** [out :: www.project.com]
> ** [out :: www.project.com] (also looked for processes matching "/u/
> apps/project/current/public/dispatch.fcgi")
> ** [out :: www.project.com]
> command finished
>
>
>
>
> On Jun 14, 6:54 am, Jamis Buck <[EMAIL PROTECTED]> wrote:
>> If all else fails, the best way to troubleshoot these things is to
>> take the commands that cap is trying to execute, and run them
>> yourself. Just log into your server, and copy and paste the commands
>> in, one at a time.
>>
>> It really looks like the problem is with your public/ or /u/apps/
>> project/shared/system directory. One or the other doesn't exist, or
>> has the wrong permissions, or something.
>>
>> A fairly common mistake is to specify the wrong path in your svn
>> repository. Make sure that your repository setting points to the root
>> of your project, and not the root of your repository. In other words,
>> if your public/ directory is in /foo/bar/trunk/public, make sure the
>> repository points to /foo/bar/trunk, and not just /foo/bar.
>>
>> - Jamis
>>
>> On Jun 13, 2007, at 9:43 PM, charlie caroff wrote:
>>
>>
>>
>>>> That's the error, right there. Do you have a /u/apps/project/
>>>> shared/
>>>> system directory on your target servers? In your project, do you
>>>> have
>>>> a public/ directory? Is it checked into your svn repository?
>>
>>> Jamis, yes, yes, and yes. I thought that perhaps setting up and
>>> deploying
>>> with an old version of capistrano might have something to do with
>>> it,
>>> so
>>> I deleted my directory structure on my remote server, then
>>> rebuilt it
>>> with
>>> deploy:setup, with capistrano 1.99.
>>
>>> Then, I ran cap deploy:cold, and here's what I got
>>
>>> cap deploy:cold
>>> [DEPRECATION] Capistrano.configuration is deprecated. Use
>>> Capistrano::Configuration.instance instead
>>> * executing `deploy:cold'
>>> * executing `deploy:update'
>>> ** transaction: start
>>> * executing `deploy:update_code'
>>> * executing "svn checkout -q -r5 svn+ssh://[local ip]/usr/home/
>>> svn/
>>> repository/project /u/apps/project/releases/20070614033859 &&
>>> (echo 5
>>>> /u/apps/project/releases/20070614033859/REVISION)"
>>> servers: ["www.project.com"]
>>> [www.project.com] executing command
>>> command finished
>>> * executing `deploy:finalize_update'
>>> * executing "chmod -R g+w /u/apps/project/releases/20070614033859"
>>> servers: ["www.project.com"]
>>> [www.project.com] executing command
>>> command finished
>>> * executing "rm -rf /u/apps/project/releases/20070614033859/
>>> log /u/
>>> apps/project/releases/20070614033859/public/system /u/apps/project/
>>> releases/20070614033859/tmp/pids &&\n ln -s /u/apps/project/
>>> shared/log /u/apps/project/releases/20070614033859/log &&\n
>>> ln -
>>> s /u/apps/project/shared/system /u/apps/project/releases/
>>> 20070614033859/public/system &&\n ln -s /u/apps/project/shared/
>>> pids /u/apps/project/releases/20070614033859/tmp/pids"
>>> servers: ["www.project.com"]
>>> [www.project.com] executing command
>>> ** [out ::www.project.com] ln: /u/apps/project/releases/
>>> 20070614033859/public/system: No such file or directory
>>> command finished
>>> *** [deploy:update_code] rolling back
>>> * executing "rm -rf /u/apps/project/releases/20070614033859; true"
>>> servers: ["www.project.com"]
>>> [www.project.com] executing command
>>> command finished
>>> command "rm -rf /u/apps/project/releases/20070614033859/log /u/apps/
>>> project/releases/20070614033859/public/system /u/apps/project/
>>> releases/
>>> 20070614033859/tmp/pids &&\\\n ln -s /u/apps/project/shared/
>>> log /
>>> u/apps/project/releases/20070614033859/log &&\\\n ln -s /u/
>>> apps/
>>> project/shared/system /u/apps/project/releases/20070614033859/
>>> public/
>>> system &&\\\n ln -s /u/apps/project/shared/pids /u/apps/
>>> project/
>>> releases/20070614033859/tmp/pids" failed onwww.project.com
>>
>>> Any ideas?
>>
>>> Charlie
>>
>>>> - Jamis
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
