<?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 Not able to start Splunk on Windows when coldpath is set to a CIFS share in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74714#M15249</link>
    <description>&lt;P&gt;We have configured Splunk 4.2.2 running on Windows Server 2008 R2 with a coldPath pointing to a volume ("cold") hosted on a CIFS network drive.&lt;/P&gt;

&lt;P&gt;Contents of indexes.conf :&lt;BR /&gt;
    #Volume Definition&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[volume:cold]
path = \\sjc-vault\SplunkArchive\splunk01
maxVolumeDataSizeMB = 1000000

################################################################################
# index definitions
################################################################################

[main]
coldPath = volume:cold\defaultdb\colddb
[history]
coldPath = volume:cold\historydb\colddb
[summary]
coldPath = volume:cold\summarydb\colddb
[_internal]
coldPath = volume:cold\_internaldb\colddb
[_audit]
coldPath = volume:cold\audit\colddb
[_thefishbucket]
coldPath = volume:cold\fishbucket\colddb
[_blocksignature]
coldPath = volume:cold\blockSignature\colddb 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, we get errors on startup for every index with a cold path set to the remote network drive:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;In handler 'indexes': Unable to load index configuration: In index '_internal': Failed to create directory '\\sjc-vault\SplunkArchive\splunk02\_internaldb\colddb' (Cannot create a file when that file already exists. 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We are using a domain account to run splunkd. This account has full rights to the shares and folders, therefore this should not be a permission issue.&lt;/P&gt;

&lt;P&gt;Any advice is appreciated!&lt;/P&gt;</description>
    <pubDate>Tue, 13 Sep 2011 21:32:11 GMT</pubDate>
    <dc:creator>zliu</dc:creator>
    <dc:date>2011-09-13T21:32:11Z</dc:date>
    <item>
      <title>Not able to start Splunk on Windows when coldpath is set to a CIFS share</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74714#M15249</link>
      <description>&lt;P&gt;We have configured Splunk 4.2.2 running on Windows Server 2008 R2 with a coldPath pointing to a volume ("cold") hosted on a CIFS network drive.&lt;/P&gt;

&lt;P&gt;Contents of indexes.conf :&lt;BR /&gt;
    #Volume Definition&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[volume:cold]
path = \\sjc-vault\SplunkArchive\splunk01
maxVolumeDataSizeMB = 1000000

################################################################################
# index definitions
################################################################################

[main]
coldPath = volume:cold\defaultdb\colddb
[history]
coldPath = volume:cold\historydb\colddb
[summary]
coldPath = volume:cold\summarydb\colddb
[_internal]
coldPath = volume:cold\_internaldb\colddb
[_audit]
coldPath = volume:cold\audit\colddb
[_thefishbucket]
coldPath = volume:cold\fishbucket\colddb
[_blocksignature]
coldPath = volume:cold\blockSignature\colddb 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, we get errors on startup for every index with a cold path set to the remote network drive:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;In handler 'indexes': Unable to load index configuration: In index '_internal': Failed to create directory '\\sjc-vault\SplunkArchive\splunk02\_internaldb\colddb' (Cannot create a file when that file already exists. 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;We are using a domain account to run splunkd. This account has full rights to the shares and folders, therefore this should not be a permission issue.&lt;/P&gt;

&lt;P&gt;Any advice is appreciated!&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2011 21:32:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74714#M15249</guid>
      <dc:creator>zliu</dc:creator>
      <dc:date>2011-09-13T21:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: Not able to start Splunk on Windows when coldpath is set to a CIFS share</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74715#M15250</link>
      <description>&lt;P&gt;Curious about the msg itself: Does '\sjc-vault\SplunkArchive\splunk02_internaldb\colddb' already exist? (if yes, can you delete that and start splunk up again)&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2011 11:31:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74715#M15250</guid>
      <dc:creator>LCM</dc:creator>
      <dc:date>2011-09-14T11:31:38Z</dc:date>
    </item>
    <item>
      <title>Re: Not able to start Splunk on Windows when coldpath is set to a CIFS share</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74716#M15251</link>
      <description>&lt;P&gt;CIFS is not a currently supported file system for Splunk indexing. Please check here for updates as new version of Splunk are made available: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Installation/Systemrequirements#Supported_file_systems"&gt;System Requirements:Supported File Systems&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jun 2012 19:58:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Not-able-to-start-Splunk-on-Windows-when-coldpath-is-set-to-a/m-p/74716#M15251</guid>
      <dc:creator>ekost</dc:creator>
      <dc:date>2012-06-15T19:58:57Z</dc:date>
    </item>
  </channel>
</rss>

