Hello, since we upgraded to the version 10.4.3.0 we have encountered the problem that randomly after the login we hit the page with the following error message:  Oops. The splunkd daemon cannot be reached by splunkweb. Check that there are no blocked network ports or that splunkd is still running. Click here to return to Splunk homepage. After a F5 Refresh the page loads again.. but that should not be the "solution". After looking a bit trough the logs, the only error I found was this :  2026-09-21 10:17:08,360 ERROR [6ab0e7e63b27b1af39010] decorators:357 - Splunkd daemon is not responding: ('Error connecting to /services/apps/local: The read operation timed out',) Traceback (most recent call last): File "D:\Splunk\Python-3.13\Lib\site-packages\splunk\rest\__init__.py", line 632, in simpleRequest serverResponse, serverContent = h.request(uri, method, headers=headers, body=payload) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ERROR [6ab0e7e63b27b1af39010] __init__:659 - Socket error communicating with splunkd (error=The read operation timed out), path = /services/apps/local Before the upgrade we did not had that problem. We did not change anything according to the firewall or ports. Does anybody else encountered the same issue after upgrading ? ... View more

Hello, we have this issue that our splunk manager and search head after around 1 up to 2 weeks increase in RAM. The splunkd service and some python scripts are the ones that slowly increment the usage of RAM over time and we had the issue that the splunkd service fails sometimes, since there is not enough ram for it to execute tasks.  We have 16GB of ram after I restart the splunkd service it goes down to 4.6 GB RAM in use. Now like I said this will increase slowly up to 15.8GB over time.  As you can see here it goes up to 12GB. Current splunk version: 9.2.0.1 Is there a known bug of memory leak for splunk itself ? Did somebody had the same issue already if so, how did you resolve this problem ? Thank you. ... View more