Chef/sigar taking forever to scan /proc/net/tcp


#1

Hey All,

It seems that during a chef-client run /proc/net/tcp is read at the start by sigar. This file is huge on one of our servers built to handle tons of concurrent connections and basically results in chef-client never running. We are using chef-client 11.4.4. Does anyone know of a workaround?

Thanks,
Mark


#2

you can disable ohai plugins selectively
http://wiki.opscode.com/display/chef/Disabling+Ohai+Plugins

On Wed, Aug 21, 2013 at 9:33 AM, Rechler, Mark <MarkRechler@clearchannel.com

wrote:

Hey All,

It seems that during a chef-client run /proc/net/tcp is read at the start
by sigar. This file is huge on one of our servers built to handle tons of
concurrent connections and basically results in chef-client never running.
We are using chef-client 11.4.4. Does anyone know of a workaround?

Thanks,
Mark


#3

Disabling the network_listeners plugin fixed this. Thanks for the tip!


From: Ranjib Dey [dey.ranjib@gmail.com]
Sent: Wednesday, August 21, 2013 12:48 PM
To: chef@lists.opscode.com
Subject: [chef] Re: chef/sigar taking forever to scan /proc/net/tcp

you can disable ohai plugins selectively
http://wiki.opscode.com/display/chef/Disabling+Ohai+Plugins

On Wed, Aug 21, 2013 at 9:33 AM, Rechler, Mark <MarkRechler@clearchannel.commailto:MarkRechler@clearchannel.com> wrote:
Hey All,

It seems that during a chef-client run /proc/net/tcp is read at the start by sigar. This file is huge on one of our servers built to handle tons of concurrent connections and basically results in chef-client never running. We are using chef-client 11.4.4. Does anyone know of a workaround?

Thanks,
Mark