knife cookbook upload --all returns internal server error
When I run:
This is returned:
I checked the server logs with
But it doesn’t seem like anything is there:
Any suggestions on why I can’t upload cookbooks? Where can I go to see more detailed errors? I’m at a loss. Thank you.
i downloaded the apache2 cookbook in the cookbooks directory from there i am trying to upload it to hosted chef server
This is the error i am getting. Uploading apache2 [1.6.0] ERROR: OpenSSL::SSL::SSLError: SSL_connect returned=6 errno=0 state=SSLv3 read finished A
Any help. Thanks in advance Jayant
Best practices manage multiple projects on open source chef-server
I need to manage multiple projects, should I use one big cookbook for each project?
Cookbook Install error
My Platform : Windows 8 and Git 1.8.0-preview20121022 and Chef Client 10.16.2
When I run knife cookbook site install database, i get the following error,
I get this error only on windows, but when I tried the same command on Linux it works perfectly.
Guessing its an issue with Windows Git ???
Any help in this regard will be of great help.
Latest Windows Cookbook (1.5.0) blows up on tasks
I had to revert to 1.4.0 after I was unable to fix a situation in which no matter what I did, I got this when I attempted to create a task:
undefined method `‘ for false:FalseClass
Something was declaring something false, it appears.
This was with every conceivable variation of the recipe. Reverting to 1.4.0 fixed the problem. Was there something I was doing wrong with a new feature etc, or is this a bug? Thanks.
apache2 with vhost using mod_proxy commands
I have just started using chef and I hit a bit of a stumbling block using the apache2 cookbook for a fresh apache install. My goal is to setup an apache virtual host to proxy to some other web app.
I started by creating a cookbook ‘mysite’ which has a recipe & template as shown below (some details omitted).
recipe mysite – include_recipe “apache2” include_recipe “apache2::mod_proxy” include_recipe “apache2::mod_proxy_http”
web_app “sigdev” do server_name node[‘hostname’] template “mysite.conf.erb” end
template mysite.conf.erb –
<VirtualHost *:80> ServerName <%= @params[:server_name] %> ProxyRequests Off ProxyPreserveHost On
# remote app ProxyPass /app <%= @params[:app_url] %> ProxyPassReverse /app <%= @params[:app_url] %> </VirtualHost>
When chef-client runs, a failure is reported because apache fails to start
[2012-08-30T11:47:21-04:00] ERROR: service[apache2] (apache2::default line 220) has had an error [2012-08-30T11:47:21-04:00] ERROR: service[apache2] (/var/cache/chef/cookbooks/apache2/recipes/default.rb:220:in `from_file') had an error: service[apache2] (apache2::default line 220) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with , but received ‘1’ —— Begin output of /sbin/service httpd start —— STDOUT: Starting httpd: [FAILED] STDERR: Warning: DocumentRoot [/opt/web/home] does not exist Syntax error on line 18 of /etc/httpd/sites-enabled/sigdev.conf: Invalid command ‘ProxyRequests’, perhaps misspelled or defined by a module not included in the server configuration —— End output of /sbin/service httpd start —— Ran /sbin/service httpd start returned 1
I have tried various combinations of including the recipes to enable mod_proxy and using the apache_mod definition in my recipe. No matter what I try, it keeps failing at the end of the apache::default cookbook where it starts the apache service.
I have looked in the mods-enabled directory and mod_proxy was not enabled which is why the service fails to start. However, I can’t seem to get it to enable mod_proxy before starting the service.
I found that there were a few ways to get past this problem.
1) After chef-client fails, manually enable the mod_proxy module. The next run will work without a problem. This requires manual intervention though. 2) Override the default modules using a role. This works without any manual intervention but it feels wrong… 3) Change the apache2 service in the apache2 default recipe to ‘action :nothing’. This still results in the service being started since the initial run queues a restart of the service. I would rather not have to modify the cookbook but it seems like the best option that I can find.
Is there a better way to handle this?
There seem to be cookbooks that have been uploaded at one point in time, and have never been updated, nor respond to any inquiries regarding updates.
I have taken on primary maintenance of one such cookbook, have updated it considerably, and would like to share it back.
Is there a method or process to determine ‘ownership’ of a given cookbook, and delegate that to another interested party if it is neglected?
How to use ark on a node
I included the ark recipe in the recipe of the cookbook that comes right after the ark cookbook. The code looks like this:
subversion “checkout-olio” do
ark “install-faban” do
When i upload this file and run the client the following error occurs: NoMethodError: undefined method `url' for Chef::Resource::Ark
Can somebody please tell me where the problem is?
Correct way to handle cookbooks depenency?
Currently if we specified a cookbook path which contains all the cookbooks, even if we are NOT using it, it still cause you an error. So you need to put the cookbooks you needed ONLY in the folder.
But the problem appear when some cookbooks depends on other (e.g. wordpress depends on php), so we need to copy the cookbooks one by one manually..
Are there better way to do it?
2 cookbooks with the same name?
If I wanted to contribute a cookbook to manage