On a windows collector, how to add a source from a second local drive?

Follow

Elijah Taylor

• January 24, 2014 21:18

Can you add a source that resides on a secondary but local drive when using a Windows Collector?

I've tried specifying it as both

d:\dir\subdir\subdir

d:/dir/subdir/subdir

The results are that I see the following in collector.log:

WARN com.sumologic.scala.collector.blade.wildcard.LocalDirectoryNode - d:/dir/subdir/subdir does not exist or cannot be read

OR

WARN com.sumologic.scala.collector.blade.wildcard.LocalDirectoryNode - D:\dir\subdir\subdir does not exist or cannot be read

 

Yet I am able to create a source which uses "c:\Program Files\Sumo Logic Collector\logs\".

Note: All file permissions are correct (i.e. SYSTEM has full access to all dirs and the end files).

0

• 

  Ben Newton

  • January 25, 2014 18:30

  Elijah,

  Is the that the actual path log files. From the docs:

  For files on Windows systems, enter the absolute path including the drive letter. Escape special characters and spaces with a backslash (). 

  So, do you need something like D:\dir\subdir\subdir\*.log ?

   

  0

  Comment actions Permalink
• 

  Elijah Taylor

  • January 26, 2014 04:04

  That's a sanitized path, but the same structure and drive.

  I had created a source using "d:\dir\subdir\subdir\*" which failed with the error above (does not exist or cannot be read). After a while I deleted that source and (after trying some others) re-added the same thing but with ** at the end instead of just *.

  For some reason it worked properly with the ** even though all the extra * did was add recursion. Both should have worked as far as I could tell. Maybe a bug?

  0

  Comment actions Permalink
• 

  Ben Newton

  • January 27, 2014 16:31

  The ** does directory recursion, and * does file recursion. So, d:\dir\subdir\subdir\**\*.log matches:

  d:\dir\subdir\subdir\foo.log

  d:\dir\subdir\subdir\subdir\foo.log

  d:\dir\subdir\subdir\subdir\subdir\foo.log

  etc..

   

  0

  Comment actions Permalink
• 

  Elijah Taylor

  • January 27, 2014 19:04

  Ben,

   

  The ** should act dual purpose and do both directory and file recursion.

   

  According to the docs: "/var/log/** will match all files in /var/log and all files in all child directories, recursively."

   

  So you should be able to end your windows path with \** (as I did) and have it find all files in the designated directory, as well as all files in any sub directories.

   

  This is how it is behaving currently actually, my question was why ending the path with \* did not find all files in the given directory but instead gave the "does not exist or cannot be read" message.

  0

  Comment actions Permalink
• 

  Yongxing Wang

  • January 27, 2014 19:54

  Elijah,

   

  "\*" only finds the files under the given directory, NOT recursively for each every subdirectories. So if your directory contains no file at all, but just a couple of subdirectories, then you will get the above mentioned symptom.

  Thanks!

  Yongxing

   

  0

  Comment actions Permalink
• 

  Elijah Taylor

  • January 27, 2014 20:08

  Yongzing,

  I wonder if I messed up the collector in the first place by creating the source before the directory was populated. The problem is that it never appeared to recover even after putting some files in the directory (i.e. it never recognized that a file had been placed there).

  I'll try again to create a source without any files in it and then populate the directory and see how long before (or if) the collector recognizes the presence of files.

  0

  Comment actions Permalink
• 

  Elijah Taylor

  • January 27, 2014 20:08

  Sorry, got your name wrong Yongxing :)

  0

  Comment actions Permalink
• 

  Yongxing Wang

  • January 27, 2014 20:48

  No problem with the name thing. :-) If it still doesn't work, I'd suggest you to open a support ticket. 

   

  Yongxing

  0

  Comment actions Permalink

Please sign in to leave a comment.