Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Installation
- :
- SPLUNK Forwarder on VIOS
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We just installed the forwarder on one of our VIOS systems to ensure we could get this working, however each time we try to start it up we see the below in our splunkd.log
02-09-2024 13:28:54.797 -0600 WARN ulimit [80544161 MainThread] - A system resource limit on this machine is below the minimum recommended value: system_resource = Data segment size (ulimit -d); current_limit = 134217728; recommended_minimum_value = 536870912. Change the operating system resource limits to meet the minimum recommended values for Splunk Enterprise.
02-09-2024 13:28:54.797 -0600 INFO ulimit [80544161 MainThread] - Limit: data file size: unlimited
02-09-2024 13:28:55.258 -0600 WARN Thread [86376799 HTTPDispatch] - HTTPDispatch: about to throw a ThreadException: pthread_create: Not enough space; 43 threads active. Trying to create batchreader0
We issued the ulimit -d command to update this to unlimited, however still seeing the issue.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was perfect, TY. I updated /etc/security/limits with the appropriate values and all is working now.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @kenbaugher ,
The ulimit -d configuration will only present the current ulimit configuration.
Please use the following Splunk doc to apply the ulimits configuration:
Thanks.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This was perfect, TY. I updated /etc/security/limits with the appropriate values and all is working now.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Index This | What travels the world but is also stuck in place?
Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data
Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...
