While evaluating Sawmill Professional 8.0.9 and considering it for our reporting needs there is a serious issue where it appears that database updates are not actioned.
Log sources are two shared folders on the network (set up as such with access credentials set-up manually) with files picked up via wildcards. The update task seems to run, but never recognizes that any data would be updateable. Manually updating database has no effect, manually rebuilding database picks the changes up.
Please advise whether this is expected behaviour or if there are any suggestions to get this working - as far as we are concerned this is a showstopper, but it is unclear whether this is due to running it on the test enviroment (desktop machine, essentially) or some internal issues with sawmill.
2. "RE: Database update issue"
In response to message #1
LAST EDITED ON May-13-10 AT 00:15 AM (PDT)
I noticed the same behavior, either with share folder and local folder. My syslogNg generate a new folder with the dayly logfile but sawmill dosn't semms to reat it antil a manual rebuild/update of the db
Any suggestion ? I'm using the evaluation as enterprise ed
Printer-friendly copy
