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
Get Updates on the Splunk Community!

Leveraging Detections from the Splunk Threat Research Team & Cisco Talos

  Now On Demand  Stay ahead of today’s evolving threats with the combined power of the Splunk Threat Research ...

New in Splunk Observability Cloud: Automated Archiving for Unused Metrics

Automated Archival is a new capability within Metrics Management; which is a robust usage & cost optimization ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...