<?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: Problems with File &amp; Directory Monitoring in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70287#M14303</link>
    <description>&lt;P&gt;For the Syslog, have you verified that the Windows server is not blocking UDP:514 in the firewall?  Also, did you add UDP:514 to the Splunk ports input?&lt;/P&gt;</description>
    <pubDate>Thu, 14 Oct 2010 17:59:14 GMT</pubDate>
    <dc:creator>treinke</dc:creator>
    <dc:date>2010-10-14T17:59:14Z</dc:date>
    <item>
      <title>Problems with File &amp; Directory Monitoring</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70286#M14302</link>
      <description>&lt;P&gt;I've installed Splunk (4.1.5(85165) on windows) and have uploaded some logs without any issues.&lt;/P&gt;

&lt;P&gt;I now want to monitor a linux server, but I'm having problems adding the datasource and always get the message:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;Encountered the following error while trying to save: In handler 'monitor': Path must be absolute.&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I'm using Splunk Web and have set the host field value to the two servers IP address and the full path on server to &lt;CODE&gt;/var/log&lt;/CODE&gt; (and tried various other combinations).&lt;/P&gt;

&lt;P&gt;On the Linux server I've added &lt;CODE&gt;*.*@192.168.254.100&lt;/CODE&gt; to syslog.conf.&lt;/P&gt;

&lt;P&gt;I've &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Monitorfilesanddirectories" rel="nofollow"&gt;read the manual&lt;/A&gt;, but it doesn't really help. and I'm finding a lack of tutorials. Pretty much thinking of abandoning the idea of Splunk now. I'm obviously missing some sort of basic information here. Can anyone help out? Being pointed in the direction of some decent tutorials would be good...&lt;/P&gt;

&lt;P&gt;I'm having trouble understand how all this data gets sent to Splunk and how Splunk intercepts/retrieves it.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Oct 2010 17:00:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70286#M14302</guid>
      <dc:creator>autovhcdev</dc:creator>
      <dc:date>2010-10-14T17:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with File &amp; Directory Monitoring</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70287#M14303</link>
      <description>&lt;P&gt;For the Syslog, have you verified that the Windows server is not blocking UDP:514 in the firewall?  Also, did you add UDP:514 to the Splunk ports input?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Oct 2010 17:59:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70287#M14303</guid>
      <dc:creator>treinke</dc:creator>
      <dc:date>2010-10-14T17:59:14Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with File &amp; Directory Monitoring</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70288#M14304</link>
      <description>&lt;P&gt;The firewall is not blocking that port, and I've got a Data Input on UDP:514 - I had to restart and now it shows up in the data sources&lt;/P&gt;</description>
      <pubDate>Thu, 14 Oct 2010 18:10:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70288#M14304</guid>
      <dc:creator>autovhcdev</dc:creator>
      <dc:date>2010-10-14T18:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with File &amp; Directory Monitoring</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70289#M14305</link>
      <description>&lt;P&gt;When you are getting the error message, are you getting that on the agent on the linux system or are you trying to use an UNC path?  &lt;/P&gt;

&lt;P&gt;If it is local to the system, what is the path you are trying to enter to get that error (/var/log/)?  &lt;/P&gt;

&lt;P&gt;What linux flavor and version are you using?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Oct 2010 19:33:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problems-with-File-Directory-Monitoring/m-p/70289#M14305</guid>
      <dc:creator>treinke</dc:creator>
      <dc:date>2010-10-15T19:33:45Z</dc:date>
    </item>
  </channel>
</rss>

