Versions Compared

Old Version 7

changes.mady.by.user Amit Munwes

Saved on

compared with

New Version 8

changes.mady.by.user Amit Munwes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Make sure DPOD Syslog agents are accessible from the Gateway that is experiencing the dropped events.
    You can use the troubleshooting tools on the Gateway Web UI to try to connect to DPOD Syslog agents. If the tools fail to connect, that needs to be fixed by the network administrator.
  2. Restart the Syslog agents using the Admin Console, and see if the problem still exists (you need to wait at least 2 hours to check the Devices page again).
  3. Inspect the logs of DPOD Syslog agents and DPOD Store and search for any errors that might explain the issue. You might see CPU starvation errors or long GC error messages which indicate there is a lack of resources for DPOD machine.
  4. In case DPOD is installed on a virtual machine, make sure to reserve memory, as documented in Hardware and Software Requirements.
  5. Also, make sure the TPS level matches the type of installation of DPOD servers and the allocated resources in Hardware and Software Requirements.

...