Hi ,
I am running chef client on couple nodes , on all nodes the recipe is
executed fine , but i get this error in last,
please help
- execute “bash” “/tmp/chef-script20130915-22201-a8yb3p”
[2013-09-15T11:34:23-07:00] ERROR: Running exception handlers
[2013-09-15T11:34:23-07:00] FATAL: Saving node information to
/var/chef/cache/failed-run-data.json
[2013-09-15T11:34:23-07:00] ERROR: Exception handlers complete
Chef Client failed. 6 resources updated
[2013-09-15T11:34:23-07:00] FATAL: Stacktrace dumped to
/var/chef/cache/chef-stacktrace.out
[2013-09-15T11:34:23-07:00] FATAL: Net::HTTPServerException: 413 “Request
Entity Too Large”
Hi there,
manoj.thakkar@gmail.com writes:
I am running chef client on couple nodes , on all nodes the recipe is
executed fine , but i get this error in last,
[2013-09-15T11:34:23-07:00] FATAL: Net::HTTPServerException: 413 "Request
Entity Too Large"
The 413 error is returned by Chef Server (as well as Hosted Enterprise
Chef) when the JSON data sent in the request exceeds 1MM bytes.
So to take a guess, one of your nodes is quite large and the server is
rejecting the large node at the end of the run when chef-client attempts
to save the node.
--
Seth Falcon | Development Lead | Opscode | @sfalcon
Thanks for the reply,
i noted that and changed the nginx.conf in /opt/chef-server/embedded/conf
http {
include mime.types;
default_type application/octet-stream;
#log_format main '$remote_addr - $remote_user [$time_local]
"$request" '
# '$status $body_bytes_sent "$http_referer" '
# '"$http_user_agent" "$http_x_forwarded_for"';
- client_max_body_size 100M;*
i thought that will fix the issues, is there something wrong.
Thanks
Manoj
On Sun, Sep 15, 2013 at 8:40 PM, Seth Falcon seth@opscode.com wrote:
Hi there,
manoj.thakkar@gmail.com writes:
I am running chef client on couple nodes , on all nodes the recipe is
executed fine , but i get this error in last,
[2013-09-15T11:34:23-07:00] FATAL: Net::HTTPServerException: 413 "Request
Entity Too Large"
The 413 error is returned by Chef Server (as well as Hosted Enterprise
Chef) when the JSON data sent in the request exceeds 1MM bytes.
So to take a guess, one of your nodes is quite large and the server is
rejecting the large node at the end of the run when chef-client attempts
to save the node.
--
Seth Falcon | Development Lead | Opscode | @sfalcon
Manoj, run ohai itself and see what is generating so much data. If I had
to take a wild guess, I suspect the Ohai passwd plugin is enumerating
hundreds or thousands of users in your environment.
If so, consider the possibility of disabling the Ohai passwd plugin:
https://www.google.com/search?q=ohai+disable+passwd+plugin&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a
On 9/16/2013 12:35 AM, Manoj Thakkar wrote:
Thanks for the reply,
i noted that and changed the nginx.conf in /opt/chef-server/embedded/conf
http {
include mime.types;
default_type application/octet-stream;
#log_format main '$remote_addr - $remote_user [$time_local]
"$request" '
# '$status $body_bytes_sent "$http_referer" '
# '"$http_user_agent" "$http_x_forwarded_for"';
- client_max_body_size 100M;*
i thought that will fix the issues, is there something wrong.
Thanks
Manoj
On Sun, Sep 15, 2013 at 8:40 PM, Seth Falcon <seth@opscode.com
mailto:seth@opscode.com> wrote:
Hi there,
manoj.thakkar@gmail.com <mailto:manoj.thakkar@gmail.com> writes:
> I am running chef client on couple nodes , on all nodes the recipe is
> executed fine , but i get this error in last,
>
> [2013-09-15T11:34:23-07:00] FATAL: Net::HTTPServerException: 413
"Request
> Entity Too Large"
The 413 error is returned by Chef Server (as well as Hosted Enterprise
Chef) when the JSON data sent in the request exceeds 1MM bytes.
So to take a guess, one of your nodes is quite large and the server is
rejecting the large node at the end of the run when chef-client attempts
to save the node.
+ seth
--
Seth Falcon | Development Lead | Opscode | @sfalcon