https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155348#M1760 <P>The full message is:</P> <P>WARN HttpListener - Socket error from 127.0.0.1 while accessing /servicesNS/-/search/admin/summarization: Broken pipe</P> <P>It is always the same. I get five of them in a row, a second apart. I see them at 15, 30, 40 and 45 minutes after the hour.</P> <P>I am on Splunk 6.1.5 build 239630</P> <P>When splunk is starting up I see these:</P> <PRE><CODE>12-09-2014 11:43:35.753 -0800 INFO loader - Limiting REST HTTP server to 2730 sockets 12-09-2014 11:43:35.753 -0800 INFO loader - Limiting REST HTTP server to 397 threads </CODE></PRE> <P>$ ulimit -n<BR /> 8192</P> <P>I'm wondering what it was doing and what I need to do to stop the errors.</P> Wed, 10 Dec 2014 00:51:18 GMT wrangler2x 2014-12-10T00:51:18Z https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155348#M1760 <P>The full message is:</P> <P>WARN HttpListener - Socket error from 127.0.0.1 while accessing /servicesNS/-/search/admin/summarization: Broken pipe</P> <P>It is always the same. I get five of them in a row, a second apart. I see them at 15, 30, 40 and 45 minutes after the hour.</P> <P>I am on Splunk 6.1.5 build 239630</P> <P>When splunk is starting up I see these:</P> <PRE><CODE>12-09-2014 11:43:35.753 -0800 INFO loader - Limiting REST HTTP server to 2730 sockets 12-09-2014 11:43:35.753 -0800 INFO loader - Limiting REST HTTP server to 397 threads </CODE></PRE> <P>$ ulimit -n<BR /> 8192</P> <P>I'm wondering what it was doing and what I need to do to stop the errors.</P> Wed, 10 Dec 2014 00:51:18 GMT https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155348#M1760 wrangler2x 2014-12-10T00:51:18Z https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155349#M1761 <P>Hi, </P> <P>Please check the ulimit -u , default value is more than 150k. Please change that, it should fix that. </P> Thu, 19 Mar 2015 01:36:53 GMT https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155349#M1761 mwong 2015-03-19T01:36:53Z https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155350#M1762 <P>are you saying that 150k default value has to be changed? To what value?</P> Fri, 29 Sep 2017 17:45:30 GMT https://community.splunk.com/t5/Monitoring-Splunk/quot-HttpListener-Socket-error-from-127-0-0-1-Broken-pipe-quot/m-p/155350#M1762 kiril123 2017-09-29T17:45:30Z