- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have been a long time linux shop for monitoring syslog data. However recently we have needed to switch to winOS since we are trying to convert to syslog over TCP. I am running into issues now with the UF causing the syslog application to hang and not be able to write over previous rolling log files. Are there any suggestions on settings to try on the UF or syslog application? There are several very chatty devices that will roll a 100MB log file in about 5 minutes. These are usually the log files that the UF is having an issue.
Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not believe it is the Splunk UF at this time. I think there is an issue with WinSyslog using circular logging, so I have switched back to normal logging. I also wrote a ps script to delete log files older than 2 hours based on last modified timestamp.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not believe it is the Splunk UF at this time. I think there is an issue with WinSyslog using circular logging, so I have switched back to normal logging. I also wrote a ps script to delete log files older than 2 hours based on last modified timestamp.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does the UF lock the file in anyway that would prevent the WinSyslog application from writing to it? Is there any setting that I could enable to resolve this UF issue?
