similar to: rake db:seed on EC2

Hi there I''m using the latest release (r300) and ''script/backgroundrb start'' works perfectly when executed on the server, but when put inside a Rake task, it doesn''t launch the worker processes. The Rake task is as follows: task :start_backgroundrb do run "cd #{current_path} && ./script/backgroundrb start" end When I run this task, the

Hi, I am learning cucumber. I have integrated the Devise with my rails 3 application. My problem is I have to write a test which will create a project. For that I have to make sure that user should be logged in. So I have written the user login feature first which is working fine. After that I have written the creation of project scenario. Whenever I am running that scenario we are getting an

ok, i was wrong. the failure on deployment using capistrano is 100% using these commands ## Our Handlers desc "Restart BackgrounDrb" task :restart_uploader, :roles => :app do run "#{current_path}/script/backgroundrb stop" run "#{current_path}/script/backgroundrb start" end here is the console post deploy on the remote server ######## [current]$

I''ve created a couple of tasks in my deploy.rb file for starting and stopping backgroundrb on the remote server. The stop task runs fine and kills the process. And the start task *seems* to run successfully, but backgroundrb is never started on the remote host. Has anyone had success with this? Here are my deploy tasks: desc ''Start backgroundrb server (default

Sorry for the newbie question but I''m stumped: I have an app that requires sudo to run mongrel_rails. For my capistrano recipe is do it like this: sudo "mongrel_rails start -e production -p #{application_port} -d -c #{current_path}" Which works famously. Now I have tried several things for my restart task. Here they are: sudo "cd #{current_path} && sudo

Hi, I am new to puppet. I have configured puppet master and agent. 1. Executed this "*puppetca --sign ip-10-194-18-145.ec2.internal*" command in puppet master instance. It returns an output like * notice: Signed certificate request for ip-10-194-18-145.ec2.internal* * notice: Removing file Puppet::SSL::CertificateRequest ip-10-194-18-145.ec2.internal at

It''s sending e-mail every hour, but I changed to sleep for a day, but keep send the e-mail by hour. I don''t know what to do to send daily. Could somebody help me? thanks ############ # mailer.rb ############### #!/usr/bin/env ruby # You might want to change this ENV["RAILS_ENV"] ||= "production" require File.dirname(__FILE__) +

My app is set up without database.yml in version control. I created a shared_path/config dir, and put database.yml in it. After I update the code, I want to link the app''s database.yml file to the shared config. So I added this task desc ''Copy the database config'' task :after_update_code, :roles => :app do run "ln -s #{shared_path}/config/database.yml

If you installed your copy of ruby via DarwinPorts, the hashbang lines at the top of your dispatch.* scripts says "#!/opt/local/bin/ruby". This is a problem, if you''re deployin via Capistrano to a host with a different path to ruby (which would be practially all of them:-) Here''s a fix. Add this "fix_hashbangs.rb" script to your script directory.

Hi, I was previously using an EC2 AMI where i was logging as root, and i could bootstrap nodes. I am now using Amazon AMIs ( http://aws.amazon.com/fr/amazon-linux-ami ) and they require login as ec2-user. The problem is that if i run puppet node bootstrap --login ec2-user, it will detect it and run my install script as with sudo, which is fine, but sudo will not run it because it is configured by

I have a dataset, which contains a day column that I would like to retrieve results on. Is there any reason why daily_stats.where(''day = Date(?)'', dte).first returns and empty set, daily_stats.find(:first, :conditions => [''date(day) = ?'', dte]) returns the correct data and daily_stats.where({:created_at => (date.midnight - 1.day)..date.midnight}).first

Greets, When merging lots of subindexes in batches like so: xapian-compact -m idx1 idx2... dstidx Errors such as: xapian-compact: DatabaseError: Error reading block 0: got end of file present a problem since it does not provide the offending path name (of the broken index) for easy identification/removal in automated/batch scenarios (the way DatabaseOpeningError:.... does, eg). The only way

I have noticed that occasionally (about 50% of the time) when i deploy (using capistrano) my app to a production server, i have to ssh into the box and manually stop and start backgroundrb to get it to load my workers. this is my basic setup i have 2 workers: lib/workers/mp3_worker.rb => takes a hash of params to downsample an mp3 lib/workers/flv_worker.rb => takes a has of

Tomorrow, I intend to push a change to mirrorlist.centos.org nodes that will have a (good) impact to CentOS EC2 instances running from AWS network. Thanks to AWS, sponsoring the required backend infra for this to happen, our mirrorlist nodes will redirect yum/dnf operations internally in the EC2/AWS network. What does that mean for you ? - faster updates (due to Cloudfront caching, and so most

I've created an EC2 AMI for AWS that essentially represents a CentOS 7 "hypervisor" image. I deploy instances of these in AWS and create an number of libvirt based lxc containers on each of these instances. The containers run fine within a single host and have no problem communicating with themselves as well as with their host, and vice versa. However, containers hosted in one

Hi I plan to host Asterisk instances on AWS/EC2 servers. Requirement is to run asterisk instance with transcoding (g.729 + g.711) and full recording. Number of concurrent calls expected are 500+. 2 instances will be configured for 100% redundancy. Heart beat will be used to determine active instance. How should I choose EC2 instance? How many vCPU, RAM should be selected? I am assuming that

On 04/01/2016 07:04 PM, Peter Steele wrote: > On 04/01/2016 02:07 PM, Laine Stump wrote: >> On 03/31/2016 06:43 PM, Peter Steele wrote: >>> I've created an EC2 AMI for AWS that essentially represents a CentOS >>> 7 "hypervisor" image. I deploy instances of these in AWS and create >>> an number of libvirt based lxc containers on each of these

Hi, My puppet master version:- #puppet --version 2.7.19 (Puppet Enterprise 2.7.0) While bootstrapping a new instance with my puppet master on Ec2,I am getting this error #puppet node_aws bootstrap --type t1.micro --image ami-00934969 --keyname ec2 --login root --keyfile ~/.ssh/ec2.pem --mode agent notice: Creating new instance ... notice: Creating new instance ... Done notice: Creating

Has anyone been able to get asterisk 1.6 running under Xen or Amazon EC2? If yes, can you share your experience please? Is it usable in a production environment? How is the sound quality? Am I likely to suffer from latency issues if the extensions are not located in the US? Any pitfall that I should be aware of? Cheers -- Aryan Ameri

On 03/31/2016 06:43 PM, Peter Steele wrote: > I've created an EC2 AMI for AWS that essentially represents a CentOS 7 > "hypervisor" image. I deploy instances of these in AWS and create an > number of libvirt based lxc containers on each of these instances. The > containers run fine within a single host and have no problem > communicating with themselves as well as