https://community.splunk.com/t5/Security/many-CLOSE-WAIT-and-splunkweb-is-not-responding/m-p/160848#M4801 <P>I am using Splunk 5.0.2 and I see many CLOSE_WAIT when running netstat -an command.<BR /><BR /> Splunkweb becomes unresponsive and I have to restart splunk to fix the issue.</P> Fri, 21 Feb 2014 08:58:16 GMT cwl 2014-02-21T08:58:16Z https://community.splunk.com/t5/Security/many-CLOSE-WAIT-and-splunkweb-is-not-responding/m-p/160848#M4801 <P>I am using Splunk 5.0.2 and I see many CLOSE_WAIT when running netstat -an command.<BR /><BR /> Splunkweb becomes unresponsive and I have to restart splunk to fix the issue.</P> Fri, 21 Feb 2014 08:58:16 GMT https://community.splunk.com/t5/Security/many-CLOSE-WAIT-and-splunkweb-is-not-responding/m-p/160848#M4801 cwl 2014-02-21T08:58:16Z https://community.splunk.com/t5/Security/many-CLOSE-WAIT-and-splunkweb-is-not-responding/m-p/160849#M4802 <P>This is a bug in the cherrypy threading code where the number of worker threads are reduced to a really low amount and no new threads are allowed to spawn. <BR /><BR /> This has been fixed in 5.0.3 but if you are using versions pre-5.0.3 then you can workaround the issue by modifying web.conf on all of the search heads.<BR /><BR /> Please add below settings in web.conf and restart your splunk instance.<BR /> <PRE><CODE>server.thread_pool_max = 30 <BR /> server.thread_pool_max_spare = 31 <BR /> </CODE></PRE></P> Mon, 28 Sep 2020 15:57:10 GMT https://community.splunk.com/t5/Security/many-CLOSE-WAIT-and-splunkweb-is-not-responding/m-p/160849#M4802 cwl 2020-09-28T15:57:10Z