|
There seems to be a big bug in v1.8.1 relating to identification of the event logs. If you subsequently add new event logs, it can break all existing filter definitions - although the configuration tool will show the right eventlog name, in fact the filter will be assosciated with the wrong eventlog.
I am working on a fix for this now, and the new v1.9 should also have a fix for the unicode messages issue. I am also dropping NT support as I dont think anyone uses it any more anyway, and its difficult to make the correct executables.
If you have this issue, the way to fix it is 1) Delete all your existing filters 2) stop the agent 3) restart the config tool 4) redefine your filters manually (DO NOT use a saved registry dump) 5) restart the agent
A better fix will be in v1.9
_________________ Steve Shipway UNIX Systems, ITSS, University of Auckland, NZ Woe unto them that rise up early in the morning... -- Isaiah 5:11
|