<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How do I fix: 'litsearch' command: Unable to parse the search: unbalanced parentheses? in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-fix-litsearch-command-Unable-to-parse-the-search/m-p/610535#M9100</link>
    <description>&lt;P&gt;I'm an end user! It appears to be just my user account. we dont seem to be able to find the answer&lt;/P&gt;
&lt;P&gt;When I do &lt;U&gt;any search&lt;/U&gt; (such as &lt;EM&gt;&lt;STRONG&gt;index="med"&lt;/STRONG&gt;&lt;/EM&gt;) I get&amp;nbsp;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;"Error in 'litsearch' command: Unable to parse the search: unbalanced parentheses."&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;When I go through the logs I was surprised to see that such a simple search resulted in&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;EM&gt;&lt;STRONG&gt;litsearch (index="med" index=nessus ((source="SI - EZproxy" orig_sourcetype="nessus:scan") OR sourcetype="nessus:scan") | lookup Device_Details nt_host as host-fqdn output bunit | search bunit="Medicine"&lt;FONT face="andale mono,times" size="4" color="#000000"&gt;)&lt;/FONT&gt; | litsearch (index="med" index=nessus sourcetype=nessus:scan | lookup Device_Details nt_host as host-fqdn output bunit | search bunit="Medicine") | fields&amp;nbsp; keepcolorder=t "*" "_bkt" "_cd" "_si" "host" "index" "linecount" "source" "sourcetype" "splunk_server"&amp;nbsp; | remotetl&amp;nbsp; nb=300 et=1660905790.000000 lt=1660906690.000000 remove=true max_count=1000 max_prefetch=100&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;While the parenthesis balance, I read somewhere they they have to balance within the pipe (|), which they don't.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We do indeed have a nessus index and several months ago someone started work on getting nessus reporting dashboard in splunk to work (still ongoing). However I am not sure why a simple search on index=Med would reference "nessus".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does the litsearch command look wrong?&lt;BR /&gt;Where is it picking up the conf to produce such a command and can it be fixed?&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="inherit"&gt;I have tried to create a table view of&amp;nbsp; "med" and I get no &lt;/FONT&gt;entries&lt;FONT face="inherit"&gt;&amp;nbsp;rather than an error. I did that &lt;/FONT&gt;because&lt;FONT face="inherit"&gt;&amp;nbsp;it would be good to see the &lt;/FONT&gt;index&lt;FONT face="inherit"&gt;&amp;nbsp;to know its not a permission error.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Aug 2022 13:58:27 GMT</pubDate>
    <dc:creator>Mr_Johnson42</dc:creator>
    <dc:date>2022-08-24T13:58:27Z</dc:date>
    <item>
      <title>How do I fix: 'litsearch' command: Unable to parse the search: unbalanced parentheses?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-fix-litsearch-command-Unable-to-parse-the-search/m-p/610535#M9100</link>
      <description>&lt;P&gt;I'm an end user! It appears to be just my user account. we dont seem to be able to find the answer&lt;/P&gt;
&lt;P&gt;When I do &lt;U&gt;any search&lt;/U&gt; (such as &lt;EM&gt;&lt;STRONG&gt;index="med"&lt;/STRONG&gt;&lt;/EM&gt;) I get&amp;nbsp;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;"Error in 'litsearch' command: Unable to parse the search: unbalanced parentheses."&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;When I go through the logs I was surprised to see that such a simple search resulted in&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;EM&gt;&lt;STRONG&gt;litsearch (index="med" index=nessus ((source="SI - EZproxy" orig_sourcetype="nessus:scan") OR sourcetype="nessus:scan") | lookup Device_Details nt_host as host-fqdn output bunit | search bunit="Medicine"&lt;FONT face="andale mono,times" size="4" color="#000000"&gt;)&lt;/FONT&gt; | litsearch (index="med" index=nessus sourcetype=nessus:scan | lookup Device_Details nt_host as host-fqdn output bunit | search bunit="Medicine") | fields&amp;nbsp; keepcolorder=t "*" "_bkt" "_cd" "_si" "host" "index" "linecount" "source" "sourcetype" "splunk_server"&amp;nbsp; | remotetl&amp;nbsp; nb=300 et=1660905790.000000 lt=1660906690.000000 remove=true max_count=1000 max_prefetch=100&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;While the parenthesis balance, I read somewhere they they have to balance within the pipe (|), which they don't.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We do indeed have a nessus index and several months ago someone started work on getting nessus reporting dashboard in splunk to work (still ongoing). However I am not sure why a simple search on index=Med would reference "nessus".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does the litsearch command look wrong?&lt;BR /&gt;Where is it picking up the conf to produce such a command and can it be fixed?&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="inherit"&gt;I have tried to create a table view of&amp;nbsp; "med" and I get no &lt;/FONT&gt;entries&lt;FONT face="inherit"&gt;&amp;nbsp;rather than an error. I did that &lt;/FONT&gt;because&lt;FONT face="inherit"&gt;&amp;nbsp;it would be good to see the &lt;/FONT&gt;index&lt;FONT face="inherit"&gt;&amp;nbsp;to know its not a permission error.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2022 13:58:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-fix-litsearch-command-Unable-to-parse-the-search/m-p/610535#M9100</guid>
      <dc:creator>Mr_Johnson42</dc:creator>
      <dc:date>2022-08-24T13:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: 'litsearch' command: Unable to parse the search: unbalanced parentheses.</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-fix-litsearch-command-Unable-to-parse-the-search/m-p/610544#M9101</link>
      <description>&lt;P&gt;Perhaps your role has a Search Filter defined that is causing the error.&amp;nbsp; If so, work with your Splunk admin to fix it.&lt;/P&gt;&lt;P&gt;Yes, parentheses must match within a pipe.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2022 18:19:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-do-I-fix-litsearch-command-Unable-to-parse-the-search/m-p/610544#M9101</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-08-23T18:19:59Z</dc:date>
    </item>
  </channel>
</rss>

