Getting Data In

Why is our [httpserver] maxThreads limit parameter in server.conf not being applied?

stevepraz
Path Finder

We were receiving errors similar to this message due to running out of http rest connections on some of our Splunk indexers.

11-16-2015 09:38:15.180 -0500 WARN  HttpListener - Can't handle request for /services/server/info, max thread limit for REST HTTP server is 1023, threads already in use is 1023

We referenced an article on this site (https://answers.splunk.com/answers/322462/why-are-our-rest-limits-so-low-how-do-we-change-th.html?ut...) that linked back to this documentation: http://docs.splunk.com/Documentation/Splunk/6.3.0/Troubleshooting/HTTPthreadlimitissues

We made the config changes in the /etc/system/local/server.conf like below:

[httpserver]
maxThreads = 65536

However, it doesn't appear to have stuck and we are still seeing the max thread issue errors. Any ideas?

0 Karma
1 Solution

johnberwick
Splunk Employee
Splunk Employee

The was a spelling mistake on the website should have been a upper case S in Server

[httpServer]
maxThreads = 65536

View solution in original post

0 Karma

johnberwick
Splunk Employee
Splunk Employee

The was a spelling mistake on the website should have been a upper case S in Server

[httpServer]
maxThreads = 65536

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...