<?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 Re: Error in 'eval' command:  unexpected character at 86400 in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628873#M218448</link>
    <description>&lt;P&gt;After running the SPL query, I am getting the below error:&lt;BR /&gt;"Error in 'where' command: Regex: unmatched closing parenthesis"&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2023 17:30:28 GMT</pubDate>
    <dc:creator>gauravu_14</dc:creator>
    <dc:date>2023-01-30T17:30:28Z</dc:date>
    <item>
      <title>Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/551659#M156548</link>
      <description>&lt;P&gt;Hi All, On the internal logs i see this eval command error -&amp;nbsp;&lt;BR /&gt;ERROR EvalCommand - Error in 'eval' command: The expression is malformed. An unexpected character is reached at '*)/86400)'.&lt;/P&gt;&lt;P&gt;but it does not provide more details like which search query / search report / alert caused this error msg.&amp;nbsp;&lt;/P&gt;&lt;P&gt;searched about this, but no luck. could someone provide some suggestions please. thanks..&lt;/P&gt;</description>
      <pubDate>Fri, 14 May 2021 18:46:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/551659#M156548</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2021-05-14T18:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/551668#M156549</link>
      <description>&lt;P&gt;Yes, that's one of Splunk's many crappy error messages.&lt;/P&gt;&lt;P&gt;If you have access to the CLI, search the savedsearches.conf files for that reported string.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;find /opt/splunk/etc/apps -name savedsearches.conf -exec grep "\*)\/86400)" {} \;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you don't have CLI access then try this SPL query&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest /services/saved/searches splunk_server=local
| search search=* 
| where match(search, "\*\)\/86400\)")&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:00:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/551668#M156549</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-30T18:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/552039#M156664</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp;/ Hi All.. the above rest query returns around 25 searches, i ran all of them, all are running fine.. no errors they give(on the gui, as well as on job inspector),..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) on the internal logs, i see this error around 12 times per hour, (6 times at the hour, 6 times at the 30min).. so, just after it appears on the internal log, i login to the search head linux box, on the dispatch directory,&lt;/P&gt;&lt;P&gt;when i search for the search logs for this error, the correct search query which caused this log into the internal logs not showing up..&lt;/P&gt;&lt;P&gt;find ./ -type f -exec grep -H '/86400)' {} \;&lt;/P&gt;&lt;P&gt;find ./ -name search.log -exec grep -H '/86400)' {} \;&lt;/P&gt;&lt;P&gt;2. apart from search queries, is there anything else which might cause this errors in the internal logs?! (any field extractions, ..etc)&lt;/P&gt;</description>
      <pubDate>Tue, 18 May 2021 12:30:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/552039#M156664</guid>
      <dc:creator>inventsekar</dc:creator>
      <dc:date>2021-05-18T12:30:01Z</dc:date>
    </item>
    <item>
      <title>Re: Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628873#M218448</link>
      <description>&lt;P&gt;After running the SPL query, I am getting the below error:&lt;BR /&gt;"Error in 'where' command: Regex: unmatched closing parenthesis"&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 17:30:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628873#M218448</guid>
      <dc:creator>gauravu_14</dc:creator>
      <dc:date>2023-01-30T17:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628879#M218451</link>
      <description>&lt;P&gt;That's probably because of improper escaping of the embedded ')' characters.&amp;nbsp; I've corrected my answer.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:01:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628879#M218451</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-30T18:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628888#M218453</link>
      <description>&lt;P&gt;Thanks, the SPL did work this time. However, there was no result for the mentioned string and yet I am seeing that error&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:31:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628888#M218453</guid>
      <dc:creator>gauravu_14</dc:creator>
      <dc:date>2023-01-30T18:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: Error in 'eval' command:  unexpected character at 86400</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628900#M218456</link>
      <description>&lt;P&gt;The regex may need to be adjusted.&amp;nbsp; Try searching just for "86400".&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 20:28:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Error-in-eval-command-unexpected-character-at-86400/m-p/628900#M218456</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-30T20:28:12Z</dc:date>
    </item>
  </channel>
</rss>

