Monitoring Splunk

Splunk Crash

sriva6
New Member

Hi,

We had an issue today where Splunk suddenly stopped responding and I had to restart splunk services to fix this.

Below is what i found in the splunkd.log

10:38:45.240 AM
01-16-2013 10:38:45.240 +0000 ERROR HTTPServer - method_size=1048577, max_method_size=1048576

Please let me know if you have any clue about this. thanks

Tags (1)
0 Karma

paul_1994
Path Finder

THis is something you may want to open a support ticket on. That log entry may not be the issue? Did the crash produce a dump file? If so I would run splunk diag and then add that file to your ticket.

splunk\bin\ splunk diag

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...