A Technical I.T./DevOps Blog
Problem scenario: You are using knife commands and getting errors. For example, you try to run this: knife client list
As a result, you get this error:
“WARN: Failed to read the private key /root/.chef/continual.pem: #<Errno::ENOENT: No such file or directory @ rb_sysopen – /root/.chef/continual.pem>
ERROR: Your private key could not be loaded from /root/.chef/continual.pem
Check your configuration file and ensure that your private key is readable”
What should you do?
…
Problem scenario: You recently installed Chef server on a Linux t2.micro instance (an AWS virtual server with 1 vCPU and 1 GB of RAM). You ran this command “chef-server-ctl reconfigure” and received this error:
“Errno::ENOMEM occurred in delayed notification: runit_service[opscode-solr4] ( private-chef::opscode-solr4 line 37) had an error: Errno::ENOMEM: Cannot allocate memory – fork(2)”
What should you do?
Solution
Root cause: A t2.micro instance has insufficient RAM.
…
Continue reading “How do you handle a “ENOMEM” error when trying to run a Chef command?”
Problem scenario
When you are configuring a server to be a Chef client, you run this command:
/usr/bin/chef-client
But you get this error:
“Chef encountered an error attempting to create the client <hostnameOfChefClientServer>”
Solution
Verify you have a client.pem file in this directory on the server you are running the command on: /etc/chef/
The Chef documentation says this:
“Every request made by the chef-client to the Chef server must be an authenticated request using the Chef server API and a private key.
…
Continue reading “Troubleshooting An Initial Run Chef Client”
Problem scenario: You are trying to set up a Chef Client on a VM to be configured to communicate with your Chef Server (version 12). The OS of both servers (the Chef server and the server that will be the Chef client) is RHEL 7.3.
You run this command from a server that you want to be a Chef client:
knife client list
You get this:
…
Continue reading “Connection Refused Error When Trying to Configure Chef Server on RedHat”
Question: How Do You Find What Version of Chef That You Are Using On A Linux Server? If you are not sure if Chef is installed or not on your Linux server, see this article.
Answers (one for Chef client and one for Chef server)
To find the version of Chef client that is installed, run this:
chef-client -v
If the response is “command not found” chef-client is not installed. If chef-client is installed, the above command will result in a display of the version of chef-client.
[Sassy_Social_Share]There are many different configuration management tools. These programs promote the management of servers either through the release of code or through the deployment of infrastructure patches. They can do more than that. Commonly their utilization facilitates the transfer of files as well as the modification of existing files. Four of these configuration management (CM) tools that are very popular among modern enterprises include Puppet, Chef, Ansible, and SaltStack. This post will briefly compare and contrast some aspects of the tools themselves.
…