-
-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to upload cookbook using Knife #411
Comments
This is not a problem with the apache2 cookbook specifically. Take a look at issues like this: chef-boneyard/chef-dk#492 for more information. |
Good question. I do not see anything specific in the Regardless, I would recommend you update to a newer chef server. |
I do not have metadata.rb in my cookbook. there is only metadata.json file. |
--concurrency set to 1 works. thanks a lot for the response. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I am able to upload every other cookbook but apache2 upload fails with following error.
I am running my chef-server in Azure (its open source version 11.x)
Uploading apache2 [3.1.0]
ERROR: SSL Validation failure connecting to host: xx.xx.xx.xx - SSL_read: cert already in hash table
ERROR: Could not establish a secure connection to the server.
Use knife ssl check to troubleshoot your SSL configuration.
If your Chef Server uses a self-signed certificate, you can use
knife ssl fetch to make knife trust the server's certificates.
Original Exception: OpenSSL::SSL::SSLError: SSL_read: cert already in hash table
I am unable to understand why specifically for apache2 cookbook.
The text was updated successfully, but these errors were encountered: