Apart from your *https://github.com/imduffy15/devcloud4.git <https://github.com/imduffy15/devcloud4.git> *repo, When running the forked *https://github.com/imesh/devcloud4.git <https://github.com/imesh/devcloud4.git>* version, Getting the following message. I was trying with both
*==> management: Thank you for installing Chef!* *==> management: Running provisioner: chef_solo...* *Generating chef JSON and uploading...* *==> management: Running chef-solo...* *==> management: [2015-01-22T05:55:41+00:00] INFO: Forking chef instance to converge...* *==> management: [2015-01-22T05:55:41+00:00] WARN: * *==> management: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** *==> management: SSL validation of HTTPS requests is disabled. HTTPS connections are still* *==> management: encrypted, but chef is not able to detect forged replies or man in the middle* *==> management: attacks.* *==> management: * *==> management: To fix this issue add an entry like this to your configuration file:* *==> management: * *==> management: ```* *==> management: # Verify all HTTPS connections (recommended)* *==> management: ssl_verify_mode :verify_peer* *==> management: * *==> management: # OR, Verify only connections to chef-server* *==> management: verify_api_cert true* *==> management: ```* *==> management: * *==> management: To check your SSL configuration, or troubleshoot errors, you can use the* *==> management: `knife ssl check` command like so:* *==> management: * *==> management: ```* *==> management: knife ssl check -c /tmp/vagrant-chef-2/solo.rb* *==> management: ```* *==> management: * *==> management: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** *==> management: * *==> management: [2015-01-22T05:55:41+00:00] INFO: *** Chef 11.16.0 **** *==> management: [2015-01-22T05:55:41+00:00] INFO: Chef-client pid: 2938* *==> management: [2015-01-22T05:55:47+00:00] INFO: Setting the run_list to ["recipe[nat-router]", "recipe[cloudstack::management-server]"] from CLI options* *==> management: [2015-01-22T05:55:47+00:00] INFO: Run List is [recipe[nat-router], recipe[cloudstack::management-server]]* *==> management: [2015-01-22T05:55:47+00:00] INFO: Run List expands to [nat-router, cloudstack::management-server]* *==> management: [2015-01-22T05:55:47+00:00] INFO: Starting Chef Run for localhost* *==> management: [2015-01-22T05:55:47+00:00] INFO: Running start handlers* *==> management: [2015-01-22T05:55:47+00:00] INFO: Start handlers complete.* *==> management: [2015-01-22T05:55:47+00:00] ERROR: Running exception handlers* *==> management: [2015-01-22T05:55:47+00:00] ERROR: Exception handlers complete* *==> management: [2015-01-22T05:55:47+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out* *==> management: [2015-01-22T05:55:47+00:00] ERROR: Cookbook nat-router not found. If you're loading nat-router from another cookbook, make sure you configure the dependency in your metadata* *==> management: [2015-01-22T05:55:47+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)* *Chef never successfully completed! Any errors should be visible in the* *output above. Please fix your recipes so that they properly complete.* Thank you, Regards *Supun Rasitha Muthutantrige* Software Engineer | Intern WSO2 Inc: http://wso2.com lean.enterprise.middleware Mobile: 0758374608 On Thu, Jan 22, 2015 at 1:09 AM, Ian Duffy <i...@ianduffy.ie> wrote: > Sounds like an issue either downloading the rpms from the repo or > vhd-util. > Do you have a stable and fast internet connection? > > Do vagrant destroy and vagrant up and it may go threw second time. > On 21 Jan 2015 04:09, "Supun Muthutantrige" <sup...@wso2.com> wrote: > >> Hi, >> >> Found a way to overcome the above messages by removing the downloaded >> VM's and starting "vagrant up" all over again. Now getting stuck with the >> following error, >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *==> management: [2015-01-21T03:53:41+00:00] ERROR: yum -d0 -e0 -y >> install cloudstack-management-4.3.2-1.el6 exceeded timeout 900==> >> management: ==> management: >> ==================================================================================> >> management: Error executing action `install` on resource >> 'package[cloudstack-management]'==> management: >> ==================================================================================> >> management: ==> management: ==> management: Timeout::Error==> management: >> --------------==> management: execution expired==> management: ==> >> management: ==> management: Resource Declaration:==> management: >> ---------------------==> management: # In >> /tmp/vagrant-chef-2/chef-solo-1/cookbooks/cloudstack/recipes/management_server.rb==> >> management: ==> management: ==> management: ==> management: 25: package >> 'cloudstack-management' do==> management: ==> management: 26: action >> :install==> management: ==> management: 27: end==> management: ==> >> management: 28: include_recipe 'cloudstack::vhd-util'==> management: ==> >> management: ==> management: ==> management: Compiled Resource:==> >> management: ------------------==> management: # Declared in >> /tmp/vagrant-chef-2/chef-solo-1/cookbooks/cloudstack/recipes/management_server.rb:25:in >> `from_file'==> management: * >> >> >> >> >> >> *==> management: [2015-01-21T03:53:41+00:00] ERROR: yum -d0 -e0 -y >> install cloudstack-management-4.3.2-1.el6 exceeded timeout 900==> >> management: ==> management: >> ==================================================================================> >> management: Error executing action `install` on resource >> 'package[cloudstack-management]'==> management: >> ==================================================================================> >> management: * >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *==> management: [2015-01-21T03:53:41+00:00] ERROR: yum -d0 -e0 -y >> install cloudstack-management-4.3.2-1.el6 exceeded timeout 900==> >> management: ==> management: >> ==================================================================================> >> management: Error executing action `install` on resource >> 'package[cloudstack-management]'==> management: >> ==================================================================================> >> management: ==> management: ==> management: Timeout::Error==> management: >> --------------==> management: execution expired==> management: ==> >> management: ==> management: Resource Declaration:==> management: >> ---------------------==> management: # In >> /tmp/vagrant-chef-2/chef-solo-1/cookbooks/cloudstack/recipes/management_server.rb==> >> management: ==> management: ==> management: ==> management: 25: package >> 'cloudstack-management' do==> management: ==> management: 26: action >> :install==> management: ==> management: 27: end==> management: ==> >> management: 28: include_recipe 'cloudstack::vhd-util'==> management: ==> >> management: ==> management: ==> management: Compiled Resource:==> >> management: ------------------==> management: # Declared in >> /tmp/vagrant-chef-2/chef-solo-1/cookbooks/cloudstack/recipes/management_server.rb:25:in >> `from_file'==> management: ==> management: ==> management: ==> management: >> package("cloudstack-management") do==> management: action [:install]==> >> management: retries 0==> management: retry_delay 2==> management: >> guard_interpreter :default==> management: package_name >> "cloudstack-management"==> management: version "4.3.2-1.el6"==> >> management: timeout 900==> management: cookbook_name :cloudstack==> >> management: recipe_name "management_server"==> management: end==> >> management: ==> management: [2015-01-21T03:53:41+00:00] INFO: Running >> queued delayed notifications before re-raising exception==> management: >> [2015-01-21T03:53:41+00:00] INFO: template[/etc/sysconfig/nfs] sending >> restart action to service[nfs] (delayed)==> management: >> [2015-01-21T03:53:44+00:00] INFO: service[nfs] restarted==> management: >> [2015-01-21T03:53:44+00:00] ERROR: Running exception handlers==> >> management: [2015-01-21T03:53:44+00:00] ERROR: Exception handlers >> complete==> management: [2015-01-21T03:53:44+00:00] FATAL: Stacktrace >> dumped to /var/chef/cache/chef-stacktrace.out==> management: >> [2015-01-21T03:53:44+00:00] ERROR: package[cloudstack-management] >> (cloudstack::management_server line 25) had an error: Timeout::Error: >> execution expired==> management: [2015-01-21T03:53:44+00:00] FATAL: >> Chef::Exceptions::ChildConvergeError: Chef run process exited >> unsuccessfully (exit code 1)Chef never successfully completed! Any errors >> should be visible in theoutput above. Please fix your recipes so that they >> properly complete.==> management: ==> management: Timeout::Error==> >> management: --------------==> management: execution expired==> management: >> ==> management: ==> management: Resource Declaration:==> management: >> ---------------------==> management: # In >> /tmp/vagrant-chef-2/chef-solo-1/cookbooks/cloudstack/recipes/management_server.rb==> >> management: ==> management: ==> management: ==> management: 25: package >> 'cloudstack-management' do==> management: ==> management: 26: action >> :install==> management: ==> management: 27: end==> management: ==> >> management: 28: include_recipe 'cloudstack::vhd-util'==> management: ==> >> management: ==> management: ==> management: Compiled Resource:==> >> management: ------------------==> management: # Declared in >> /tmp/vagrant-chef-2/chef-solo-1/cookbooks/cloudstack/recipes/management_server.rb:25:in >> `from_file'==> management: ==> management: ==> management: ==> management: >> package("cloudstack-management") do==> management: action [:install]==> >> management: retries 0==> management: retry_delay 2==> management: >> guard_interpreter :default==> management: package_name >> "cloudstack-management"==> management: version "4.3.2-1.el6"==> >> management: timeout 900==> management: cookbook_name :cloudstack==> >> management: recipe_name "management_server"==> management: end==> >> management: ==> management: [2015-01-21T03:53:41+00:00] INFO: Running >> queued delayed notifications before re-raising exception==> management: >> [2015-01-21T03:53:41+00:00] INFO: template[/etc/sysconfig/nfs] sending >> restart action to service[nfs] (delayed)==> management: >> [2015-01-21T03:53:44+00:00] INFO: service[nfs] restarted==> management: >> [2015-01-21T03:53:44+00:00] ERROR: Running exception handlers==> >> management: [2015-01-21T03:53:44+00:00] ERROR: Exception handlers >> complete==> management: [2015-01-21T03:53:44+00:00] FATAL: Stacktrace >> dumped to /var/chef/cache/chef-stacktrace.out==> management: >> [2015-01-21T03:53:44+00:00] ERROR: package[cloudstack-management] >> (cloudstack::management_server line 25) had an error: Timeout::Error: >> execution expired==> management: [2015-01-21T03:53:44+00:00] FATAL: >> Chef::Exceptions::ChildConvergeError: Chef run process exited >> unsuccessfully (exit code 1)Chef never successfully completed! Any errors >> should be visible in theoutput above. Please fix your recipes so that they >> properly complete.==> management: ==> management: ==> management: >> package("cloudstack-management") do==> management: action [:install]==> >> management: retries 0==> management: retry_delay 2==> management: >> guard_interpreter :default==> management: package_name >> "cloudstack-management"==> management: version "4.3.2-1.el6"==> >> management: timeout 900==> management: cookbook_name :cloudstack==> >> management: recipe_name "management_server"==> management: end==> >> management: ==> management: [2015-01-21T03:53:41+00:00] INFO: Running >> queued delayed notifications before re-raising exception==> management: >> [2015-01-21T03:53:41+00:00] INFO: template[/etc/sysconfig/nfs] sending >> restart action to service[nfs] (delayed)==> management: >> [2015-01-21T03:53:44+00:00] INFO: service[nfs] restarted==> management: >> [2015-01-21T03:53:44+00:00] ERROR: Running exception handlers==> >> management: [2015-01-21T03:53:44+00:00] ERROR: Exception handlers >> complete==> management: [2015-01-21T03:53:44+00:00] FATAL: Stacktrace >> dumped to /var/chef/cache/chef-stacktrace.out==> management: >> [2015-01-21T03:53:44+00:00] ERROR: package[cloudstack-management] >> (cloudstack::management_server line 25) had an error: Timeout::Error: >> execution expired==> management: [2015-01-21T03:53:44+00:00] FATAL: >> Chef::Exceptions::ChildConvergeError: Chef run process exited >> unsuccessfully (exit code 1)Chef never successfully completed! Any errors >> should be visible in theoutput above. Please fix your recipes so that they >> properly complete.* >> >> This seems like a timeout issue but the Internet connection works fine. >> >> Thank you, >> Regards >> >> >> >> *Supun Rasitha Muthutantrige* >> Software Engineer | Intern >> WSO2 Inc: http://wso2.com >> lean.enterprise.middleware >> Mobile: 0758374608 >> >> On Tue, Jan 20, 2015 at 8:58 PM, Supun Muthutantrige <sup...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I have installed chefdk and think it has helped to overcome the >>> berkshelf issue which I had previously. Now before successfully completing >>> "*Vagrant >>> up*" command steps, getting the following message and halts the process. >>> >>> >>> *==> management: Machine already provisioned. Run `vagrant provision` or >>> use the `--provision`==> management: to force provisioning. Provisioners >>> marked to run always will still run.* >>> >>> When run again with the command "*vagrant up --provision*", get the >>> following console output >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *==> xenserver: A PIF with this specified device name already exists.==> >>> xenserver: device: eth1==> xenserver: The uuid you supplied was invalid.==> >>> xenserver: type: network==> xenserver: uuid: ==> xenserver: The uuid you >>> supplied was invalid.==> xenserver: type: PIF==> xenserver: uuid: ==> >>> xenserver: The uuid you supplied was invalid.==> xenserver: type: PIF==> >>> xenserver: uuid: The SSH command responded with a non-zero exit status. >>> Vagrantassumes that this means the command failed. The output for this >>> commandshould be in the log above. Please read the output to determine >>> whatwent wrong.* >>> >>> Would like to know the reason and a way to overcome this. >>> >>> @Geroff thank you for the link I will look into that as well. >>> >>> Thank you, >>> Regards >>> >>> >>> >>> *Supun Rasitha Muthutantrige* >>> Software Engineer | Intern >>> WSO2 Inc: http://wso2.com >>> lean.enterprise.middleware >>> Mobile: 0758374608 >>> >>> On Sun, Jan 11, 2015 at 10:33 PM, Geoff Higginbottom < >>> geoff.higginbot...@shapeblue.com> wrote: >>> >>>> Hi Supun, >>>> >>>> As an alternative you could try building a test CloudStack system on >>>> Virtualbox using this guide >>>> >>>> http://shapeblue.com/cloudstack/virtualbox-test-env/ >>>> >>>> >>>> Kind Regards >>>> >>>> Geoff Higginbottom >>>> CTO / Cloud Architect >>>> >>>> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 >>>> >>>> geoff.higginbot...@shapeblue.com | www.shapeblue.com | >>>> Twitter:@shapeblue >>>> >>>> ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS >>>> >>>> ________________________________________ >>>> From: Ian Duffy <i...@ianduffy.ie> >>>> Sent: 11 January 2015 16:51:43 >>>> To: users@cloudstack.apache.org >>>> Subject: Re: Cloud-Stack Configuration | Vagrant >>>> >>>> Hey, >>>> >>>> You need to install vagrant berkshelf as I mentioned. Vagrant berkshelf >>>> has >>>> a dependency on chefdk so you'll need that too. >>>> >>>> Documentation really needs to be updated. >>>> On 11 Jan 2015 12:59, "Supun Muthutantrige" <sup...@wso2.com> wrote: >>>> >>>> > Hi, >>>> > >>>> > Cloned from the latest repository. made the network adjustments and >>>> ran the >>>> > "bash scripts/vagrant_prep.sh vbox" command, but due to the above >>>> mentioned >>>> > errors, still haven't been able to configure cloudstack properly. >>>> Would >>>> > highly appreciate your support and suggestions about what might be >>>> going >>>> > wrong. >>>> > >>>> > Thank you, >>>> > Regards. >>>> > >>>> > >>>> > *Supun Rasitha Muthutantrige* >>>> > Software Engineer | Intern >>>> > WSO2 Inc: http://wso2.com >>>> > lean.enterprise.middleware >>>> > Mobile: 0758374608 >>>> > >>>> > On Sat, Jan 10, 2015 at 2:04 PM, Supun Muthutantrige <sup...@wso2.com >>>> > >>>> > wrote: >>>> > >>>> > > As instructed, before running the Vagrant up command, I have run >>>> "bash >>>> > > scripts/vagrant_prep.sh vbox" command and the output as follows >>>> > > >>>> > > >>>> > >>>> /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: >>>> > > warning: Insecure world writable dir >>>> /...../opt/apache-maven-3.2.3/bin in >>>> > > PATH, mode 040777 >>>> > > >>>> > >>>> /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: >>>> > > warning: Insecure world writable dir >>>> /...../opt/apache-maven-3.2.3/bin in >>>> > > PATH, mode 040777 >>>> > > >>>> /opt/vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/runtime.rb:222: >>>> > > warning: Insecure world writable dir >>>> /...../opt/apache-maven-3.2.3/bin in >>>> > > PATH, mode 040777 >>>> > > >>>> > >>>> /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: >>>> > > warning: Insecure world writable dir >>>> /...../opt/apache-maven-3.2.3/bin in >>>> > > PATH, mode 040777 >>>> > > >>>> /opt/vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/runtime.rb:222: >>>> > > warning: Insecure world writable dir >>>> /...../opt/apache-maven-3.2.3/bin in >>>> > > PATH, mode 040777 >>>> > > All plugins are installed! >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > *Supun Rasitha Muthutantrige* >>>> > > Software Engineer | Intern >>>> > > WSO2 Inc: http://wso2.com >>>> > > lean.enterprise.middleware >>>> > > Mobile: 0758374608 >>>> > > >>>> > > On Sat, Jan 10, 2015 at 12:31 PM, Ian Duffy <i...@ianduffy.ie> >>>> wrote: >>>> > > >>>> > >> You need vagrant-berkshelf as the error says. >>>> > >> >>>> > >> vagrant plugin install vagrant-berkshelf >>>> > >> >>>> > >> On 10 January 2015 at 03:50, Supun Muthutantrige <sup...@wso2.com> >>>> > wrote: >>>> > >> > Hi, >>>> > >> > >>>> > >> > I have cloned the latest version. Now when running the vagrant up >>>> > >> command >>>> > >> > getting the following error >>>> > >> > >>>> > >> > *There was an error loading a Vagrantfile. The file being loaded* >>>> > >> > *and the error message are shown below. This is usually caused >>>> by* >>>> > >> > *a syntax error.* >>>> > >> > >>>> > >> > *Path: ..../binary-installation-advanced/Vagrantfile* >>>> > >> > *Message: vagrant-berkshelf is not installed!* >>>> > >> > >>>> > >> > >>>> > >> > Thank you, >>>> > >> > Regards >>>> > >> > >>>> > >> > >>>> > >> > >>>> > >> > *Supun Rasitha Muthutantrige* >>>> > >> > Software Engineer | Intern >>>> > >> > WSO2 Inc: http://wso2.com >>>> > >> > lean.enterprise.middleware >>>> > >> > Mobile: 0758374608 >>>> > >> > >>>> > >> > On Fri, Jan 9, 2015 at 5:38 PM, Supun Muthutantrige < >>>> sup...@wso2.com> >>>> > >> wrote: >>>> > >> > >>>> > >> >> Great Iwill try this out and update the thread >>>> > >> >> >>>> > >> >> >>>> > >> >> Thank you, >>>> > >> >> Regards >>>> > >> >> >>>> > >> >> >>>> > >> >> *Supun Rasitha Muthutantrige* >>>> > >> >> Software Engineer | Intern >>>> > >> >> WSO2 Inc: http://wso2.com >>>> > >> >> lean.enterprise.middleware >>>> > >> >> Mobile: 0758374608 >>>> > >> >> >>>> > >> >> On Fri, Jan 9, 2015 at 2:52 AM, Ian Duffy <i...@ianduffy.ie> >>>> wrote: >>>> > >> >> >>>> > >> >>> That issue should be fixed. Can you confirm your on the latest >>>> > clone? >>>> > >> Just >>>> > >> >>> do a git pull. >>>> > >> >>> >>>> > >> >>> If it still fails remove ~/.berkshelf and try again. >>>> > >> >>> On 8 Jan 2015 14:04, "Supun Muthutantrige" <sup...@wso2.com> >>>> wrote: >>>> > >> >>> >>>> > >> >>> > Hi Ian, >>>> > >> >>> > >>>> > >> >>> > Thank you for the information. When I run the "vagrant up" >>>> command >>>> > >> >>> > in binary-installation-advanced folder the following error >>>> > >> occurred. I >>>> > >> >>> > tried this after stopping and starting the mysql server, >>>> changed >>>> > the >>>> > >> >>> > default mysql 3306 port, but the error seems to be there, >>>> Would >>>> > >> like to >>>> > >> >>> > know the reason >>>> > >> >>> > >>>> > >> >>> > Terminal output as follows, >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> >>>> > >> >>>> > >>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ >>>> > >> >>> > >>>> > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] INFO: Forking >>>> chef >>>> > >> instance >>>> > >> >>> to >>>> > >> >>> > converge... >>>> > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] WARN: >>>> > >> >>> > ==> management: * * * * * * * * * * * * * * * * * * * * * * >>>> * * * >>>> > * >>>> > >> * * >>>> > >> >>> * * >>>> > >> >>> > * * * * * * * * * * >>>> > >> >>> > ==> management: SSL validation of HTTPS requests is disabled. >>>> > HTTPS >>>> > >> >>> > connections are still >>>> > >> >>> > ==> management: encrypted, but chef is not able to detect >>>> forged >>>> > >> >>> replies or >>>> > >> >>> > man in the middle >>>> > >> >>> > ==> management: attacks. >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: To fix this issue add an entry like this to >>>> your >>>> > >> >>> > configuration file: >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: ``` >>>> > >> >>> > ==> management: # Verify all HTTPS connections >>>> (recommended) >>>> > >> >>> > ==> management: ssl_verify_mode :verify_peer >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: # OR, Verify only connections to >>>> chef-server >>>> > >> >>> > ==> management: verify_api_cert true >>>> > >> >>> > ==> management: ``` >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: To check your SSL configuration, or >>>> troubleshoot >>>> > >> errors, >>>> > >> >>> > you can use the >>>> > >> >>> > ==> management: `knife ssl check` command like so: >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: ``` >>>> > >> >>> > ==> management: knife ssl check -c >>>> /tmp/vagrant-chef-2/solo.rb >>>> > >> >>> > ==> management: ``` >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: * * * * * * * * * * * * * * * * * * * * * * >>>> * * * >>>> > * >>>> > >> * * >>>> > >> >>> * * >>>> > >> >>> > * * * * * * * * * * >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] INFO: *** Chef >>>> 11.16.0 >>>> > >> *** >>>> > >> >>> > ==> management: [2015-01-08T13:54:31+00:00] INFO: >>>> Chef-client pid: >>>> > >> 2932 >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Setting the >>>> > >> run_list >>>> > >> >>> to >>>> > >> >>> > ["recipe[nat-router]", >>>> "recipe[cloudstack::management-server]"] >>>> > >> from CLI >>>> > >> >>> > options >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Run List is >>>> > >> >>> > [recipe[nat-router], recipe[cloudstack::management-server]] >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Run List >>>> expands >>>> > >> to >>>> > >> >>> > [nat-router, cloudstack::management-server] >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Starting >>>> Chef >>>> > Run >>>> > >> for >>>> > >> >>> > localhost >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Running >>>> start >>>> > >> handlers >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] INFO: Start >>>> handlers >>>> > >> >>> complete. >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> >>>> > >> >>>> > >>>> ================================================================================ >>>> > >> >>> > ==> management: Recipe Compile Error >>>> > >> >>> > ==> management: >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> >>>> > >> >>>> > >>>> ================================================================================ >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: Chef::Exceptions::RecipeNotFound >>>> > >> >>> > ==> management: -------------------------------- >>>> > >> >>> > ==> management: could not find recipe client for cookbook >>>> mysql >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] ERROR: Running >>>> > exception >>>> > >> >>> > handlers >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] ERROR: Exception >>>> > >> handlers >>>> > >> >>> > complete >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] FATAL: Stacktrace >>>> > >> dumped to >>>> > >> >>> > /var/chef/cache/chef-stacktrace.out >>>> > >> >>> > ==> management: [2015-01-08T13:54:36+00:00] ERROR: could not >>>> find >>>> > >> recipe >>>> > >> >>> > client for cookbook mysql >>>> > >> >>> > ==> management: [2015-01-08T13:54:37+00:00] FATAL: >>>> > >> >>> > Chef::Exceptions::ChildConvergeError: Chef run process exited >>>> > >> >>> > unsuccessfully (exit code 1) >>>> > >> >>> > Chef never successfully completed! Any errors should be >>>> visible in >>>> > >> the >>>> > >> >>> > output above. Please fix your recipes so that they properly >>>> > >> complete. >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> >>>> > >> >>>> > >>>> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> > Thank you, >>>> > >> >>> > Regards >>>> > >> >>> > >>>> > >> >>> > >>>> > >> >>> > *Supun Rasitha Muthutantrige* >>>> > >> >>> > Software Engineer | Intern >>>> > >> >>> > WSO2 Inc: http://wso2.com >>>> > >> >>> > lean.enterprise.middleware >>>> > >> >>> > Mobile: 0758374608 >>>> > >> >>> > >>>> > >> >>> >>>> > >> >> >>>> > >> >> >>>> > >> >>>> > > >>>> > > >>>> > >>>> Find out more about ShapeBlue and our range of CloudStack related >>>> services >>>> >>>> IaaS Cloud Design & Build< >>>> http://shapeblue.com/iaas-cloud-design-and-build//> >>>> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/ >>>> > >>>> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> >>>> CloudStack Software Engineering< >>>> http://shapeblue.com/cloudstack-software-engineering/> >>>> CloudStack Infrastructure Support< >>>> http://shapeblue.com/cloudstack-infrastructure-support/> >>>> CloudStack Bootcamp Training Courses< >>>> http://shapeblue.com/cloudstack-training/> >>>> >>>> This email and any attachments to it may be confidential and are >>>> intended solely for the use of the individual to whom it is addressed. Any >>>> views or opinions expressed are solely those of the author and do not >>>> necessarily represent those of Shape Blue Ltd or related companies. If you >>>> are not the intended recipient of this email, you must neither take any >>>> action based upon its contents, nor copy or show it to anyone. Please >>>> contact the sender if you believe you have received this email in error. >>>> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue >>>> Services India LLP is a company incorporated in India and is operated under >>>> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a >>>> company incorporated in Brasil and is operated under license from Shape >>>> Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of >>>> South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is >>>> a registered trademark. >>>> >>> >>> >>
