Troubleshooting Module to Module Communication

The following is a troubleshooting list of the most common symptoms associated with Module to Module Communication. If you are still unable to resolve issues or need additional guidance, contact AVEVA Technical Support through the AVEVA Customer Portal.

• Adapter cannot reach Edge Data Store by module name (edge_data_store_module:5590)

  • Containers are not on the same Docker bridge or the bridge was not created or attached.

  • Typo or mismatch in the module name used in the egress URL.

  • Nginx reverse proxy in the EDS module not running or configured correctly.

• Intermittent disconnects after reboot or network change

  • Egress still pointed at host IP or the fully qualified domain name instead of the module name

• HTTP 404/502/timeout to :5590

  • Nginx is up but backend Edge Data Store on 5595 is not listening or has crashed.

• Everything deployed, but there is no data in Edge Data Store

  • Egress section is missing or invalid in the configuration

  • Wrong protocol path

  • Secrets/credentials are not supplied where required.