Due to an OS upgrade of a Windows server the WinCollect agent does not deliver any events, because the processor rejected the connection. We examined this issue and found several entires in the Postgres database for the same WinCollect log source with different IDs and keys.
Our suggestion is, due to seeting up the server with same IP and hostname, WinCollect forwards the events to the processor. The Processor detects a new ID and generates a new entry. While processing the logs, the processor detects another ID for the same source and rejects the new connection.
Does anybody expereinced the same issue already? How to resolv this issue? Is there a proper way to delete the dublicate entires from the database?
KR,
Volker
------------------------------
Volker Scholz
------------------------------