yeah...it didn't work.(ran it from both my local machine and the server)
what do you suggest i run? do you run nginx?
thanks,
joanthan
On May 15, 2008, at 12:44 PM, Jamis Buck wrote:
> Have you tried running "mongrel_rails cluster::configure" as it
> suggests? I don't have any experience with mongrel_rails, so I guess
> I'm hoping someone else will pipe up if there's a more obvious answer.
>
> - Jamis
>
> On May 15, 2008, at 9:24 AM, JoeRails wrote:
>
>>
>> thanks for the tip. just looked into that and since i couldn't change
>> the file's perssions beacuse it wasen't there. i had to create it
>> manually...hope that's alright. the error disappeared.
>>
>> but started getting new ones. when i got o the location of the
>> following files, they seem to be missing. don't know if these need to
>> be created manually too?
>>
>> /etc/mongrel_cluster/[yourapp].conf
>> /etc/httpd/conf/apps/[yourapp].conf
>>
>>
>> here is the output for running a cap deploy:cold
>>
>> * executing `deploy:migrate'
>> * executing "ls -x /var/www/apps/my_app_name/releases"
>> `deploy:migrate' is only run for servers matching
>> {:only=>{:primary=>true}, :roles=>:db}, but no servers matched
>> MBPro:ville jtarud$ cap app:stop
>> * executing `app:stop'
>> * executing `mongrel:cluster:stop'
>> * executing "mongrel_rails cluster::stop -C /etc/mongrel_cluster/
>> my_app_name.conf"
>> servers: ["example.com"]
>> [example.com] executing command
>> ** [out :: example.com] ** Ruby version is not up-to-date; loading
>> cgi_multipart_eof_fix
>> ** [out :: example.com]
>> ** [out :: example.com] !!! Configuration file does not exist. Run
>> mongrel_rails cluster::configure.
>> ** [out :: example.com]
>> ** [out :: example.com] cluster::stop reported an error. Use
>> mongrel_rails cluster::stop -h to get help.
>> ** [out :: example.com]
>> command finished
>> command "mongrel_rails cluster::stop -C /etc/mongrel_cluster/
>> my_app_name.conf" failed on example.com
>>
>>
>> thanks for your help!
>>
>> On May 15, 9:27 am, Jamis Buck <[EMAIL PROTECTED]> wrote:
>>> I'd start by making sure the /var/www/apps/application/shared/log
>>> directory is writable by the user doing the deploy.
>>>
>>> - Jamis
>>>
>>> On May 15, 2008, at 12:41 AM, JoeRails wrote:
>>>
>>>
>>>
>>>> I am trying to deploy an application in railsmachine that has
>>>> ferret
>>>> installed. when i run the cap deploy:cold i get the following
>>>> errors.
>>>> has Not sure what type of errors i am getting, since i tried to
>>>> look
>>>> up the files it says that need permissions changed or missing and
>>>> not
>>>> sure if i would have to upload them or something. i am using this:
>>>> http://zilkey.com/2008/5/4/starting-ferret-at-reboot-using-capistrano
>>>> in order to get ferret working. thanks in advanced. jonathan(nuby
>>>> to
>>>> capistrano)
>>>
>>>> $ cap deploy:cold
>>>> * executing `deploy:cold'
>>>> * executing `deploy:update'
>>>> ** transaction: start
>>>> triggering before callbacks for `deploy:update_code'
>>>> * executing `app:symlinks:setup'
>>>> * executing "mkdir -p /var/www/apps/application/shared/public/
>>>> assets"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> * executing `deploy:update_code'
>>>> * executing "svn checkout -q -r65https://svn.example.com/repo/
>>>> trunk
>>>> /var/www/apps/application/releases/20080515062911 && (echo 65 > /
>>>> var/
>>>> www/apps/application/releases/20080515062911/REVISION)"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> * executing `deploy:finalize_update'
>>>> * executing "chmod -R g+w /var/www/apps/application/releases/
>>>> 20080515062911"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> * executing "rm -rf /var/www/apps/application/releases/
>>>> 20080515062911/log /var/www/apps/application/releases/
>>>> 20080515062911/
>>>> public/system /var/www/apps/application/releases/20080515062911/
>>>> tmp/
>>>> pids &&\n mkdir -p /var/www/apps/application/releases/
>>>> 20080515062911/public &&\n mkdir -p /var/www/apps/application/
>>>> releases/20080515062911/tmp &&\n ln -s /var/www/apps/
>>>> application/
>>>> shared/log /var/www/apps/application/releases/20080515062911/log &&
>>>> \n ln -s /var/www/apps/application/shared/system /var/www/
>>>> apps/
>>>> application/releases/20080515062911/public/system &&\n ln -s /
>>>> var/
>>>> www/apps/application/shared/pids /var/www/apps/application/
>>>> releases/
>>>> 20080515062911/tmp/pids"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> * executing "find /var/www/apps/application/releases/
>>>> 20080515062911/
>>>> public/images /var/www/apps/application/releases/20080515062911/
>>>> public/
>>>> stylesheets /var/www/apps/application/releases/20080515062911/
>>>> public/
>>>> javascripts -exec touch -t 200805150629.16 {} ';'; true"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> * executing `deploy:symlink'
>>>> * executing "rm -f /var/www/apps/application/current && ln -s /var/
>>>> www/apps/application/releases/20080515062911 /var/www/apps/
>>>> application/
>>>> current"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> triggering after callbacks for `deploy:symlink'
>>>> * executing `app:symlinks:update'
>>>> * executing "ln -nfs /var/www/apps/application/shared/public/
>>>> assets /
>>>> var/www/apps/application/current/public/assets"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> command finished
>>>> * executing `ferret:restart'
>>>> * executing `ferret:stop'
>>>> * executing "/etc/init.d/ferret_application_ctl stop"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> Password:
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] Stopping ferret DRb server.
>>>> ** [out :: example.com] Rails Error: Unable to access log file.
>>>> Please ensure that /var/www/apps/application/releases/
>>>> 20080515062911/
>>>> log/production.log exists and is chmod 0666. The log level has been
>>>> raised to WARN and the output directed to STDERR until the
>>>> problem is
>>>> fixed.
>>>> ** [out :: example.com] Stopping ferret_server...
>>>> ** [out :: example.com] no pid file found
>>>> command finished
>>>> * executing `ferret:start'
>>>> * executing "/etc/init.d/ferret_application_ctl start"
>>>> servers: ["example.com"]
>>>> [example.com] executing command
>>>> ** [out :: example.com] Starting ferret DRb server.
>>>> ** [out :: example.com] Rails Error: Unable to access log file.
>>>> Please ensure that /var/www/apps/application/releases/
>>>> 20080515062911/
>>>> log/production.log exists and is chmod 0666. The log level has been
>>>> raised to WARN and the output directed to STDERR until the
>>>> problem is
>>>> fixed.
>>>> ** [out :: example.com] Error starting ferret DRb server: No such
>>>> file or directory - /var/www/apps/application/releases/
>>>> 20080515062911/
>>>> log/ferret_server.log
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/open-uri.rb:32:in
>>>> `initialize'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/open-uri.rb:32:in
>>>> `open_uri_original_open'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/open-uri.rb:32:in `open'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/logger.rb:525:in
>>>> `create_logfile'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/logger.rb:520:in
>>>> `open_logfile'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/logger.rb:487:in
>>>> `initialize'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/logger.rb:263:in `new'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /usr/lib/ruby/1.8/logger.rb:263:in
>>>> `initialize'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /var/www/apps/application/releases/
>>>> 20080515062911/vendor/plugins/acts_as_ferret/lib/ferret_server.rb:
>>>> 45:in `new'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] /var/www/apps/application/releases/
>>>> 20080515062911/vendor/plugins/acts_as_ferret/lib/ferret_server.rb:
>>>> 45:in `start'
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] script/ferret_start:59
>>>> ** [out :: example.com]
>>>> ** [out :: example.com] Starting ferret DRb server...
>>>> command finished
>>>> ** transaction: commit
>>>> * executing `deploy:migrate'
>>>> * executing "ls -x /var/www/apps/example.com/releases"
>>>> `deploy:migrate' is only run for servers matching
>>>> {:only=>{:primary=>true}, :roles=>:db}, but no servers matched
>>>
>>>>>
>>>
>>>
>>> smime.p7s
>>> 3KDownload
>>
>> >>
>
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
