Unsolved
This post is more than 5 years old
5 Posts
0
505
Activity failure summaries and logging
We are implementing SourceOne for Files with File Archive - Historic activities on hundreds of servers. These will generate thousands of detailed logs. We are running into expected issues with users restricting permissions on folders resulting in failed activities, etc. The only way to locate the paths and error information is to comb through detailed logs. Support actually told me I would have to search each file, and I quote:
May need a "grep"-like tool to do it (anything that can search for text inside files)
Does anyone using SourceOne for Files have a better solution than me trying my hand at scripting a daily search?
EDIT: grammar
BenCs
114 Posts
0
October 17th, 2014 01:00
Can you give an example of a rule in a job log that fails? This will help us to create a script/command to get the information you need.
RandomName213
5 Posts
0
October 17th, 2014 06:00
SourceOne reporting is part of the issue, and this is what support is working on.
Phased roll-out is how we are going to have to do it.
Still, I would like to be able to schedule a daily report so the server admins can address the issue and I don't know how this could be done. That's why I'm looking for suggestions
BenCs
114 Posts
0
October 17th, 2014 06:00
Hi,
Maybe SourceOne Reporting is a solution? I don't know by heart if failed UNC-paths are listed there.
The way I would process this:
- Phase by phase roll-out on different UNC-shares and daily follow-up of the (failed) logs.
This might be time-consuming but could help you out with this issue!
RandomName213
5 Posts
0
October 17th, 2014 06:00
These are plain and simple File Archive - Historic types against shares via UNC paths. Nothing special. Support has us running custom binaries to generate more logging, but these will not be used in production once they resolve the issue. What I am looking for is a way to generate a report on all failed items that doesn't require greping through detailed logs or opening a gui. That way I can have it captured/scheduled and emailed to team members.