Monitoring Splunk

How can I trace back to the search that generated splunkd.log searchParser errors?

New Member

Hello everyone,

I'm monitoring my Splunk Enterprise instance and, by looking at splunkd logs both via cli and search through:

index=_internal source="/opt/splunk/var/log/splunk/splunkd.log" log_level=ERROR


I find numerous SearchParser errors, namely the following one:

ERROR SearchParser [20709 TcpChannelThread] - Missing a search command before '|'. Error at position '2' of search query '| |'.


How can I trace back to the search that generated such error (either the search or the sid is fine)? Is that "20709" something of interest in this scenario?

Labels (3)
0 Karma
Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...