Troubleshoot the Structured Data Files adapter

AVEVA adapters provide features for troubleshooting issues related to connectivity, data flow, and configuration. Resources include:

• ASP .NET Core platform log

• Wireshark

• Health and diagnostics egress to PI Web API

• Connection issues

• Logging

• System and OmfEgress logs

• Debugging folder or file structure

If you are still unable to resolve issues or need additional guidance, contact AVEVA Technical Support through the AVEVA Customer Portal.

Note: Make sure to also check the troubleshooting information specific to your adapter in this user guide.

ASP .NET Core platform log

The ASP .NET Core platform log provides information from the Kestrel web server that hosts the application. The log could contain information that the adapter is overloaded with incoming data. Perform the following steps to spread the load among multiple adapters:

1. Decrease the scan frequency.

2. Lower the amount of data selection items.

Wireshark

Wireshark is a protocol-specific troubleshooting tool that supports all current adapter protocols. Perform the following steps if you want to use Wireshark to capture traffic from the data source to the adapter or from the adapter to the OMF destination.

3. Download Wireshark.

4. Familiarize yourself with the tool and read the Wireshark user guide.

Health and diagnostics egress to PI Web API

The adapter sends health and diagnostics data to PI Web API; in some cases, conflicts may occur that are due to changes or perceived changes in PI Web API. For example, a 409 - Conflict error message displays if you upgrade your adapter version and the PI points do not match in the upgraded version. However, data is continued to be sent as long as containers are created, so buffering only starts if no containers are created.

To resolve the conflict, perform the following steps:

5. Stop the adapter.

6. Delete the Health folder inside of the Buffers folder.

7. Stop PI Web API.

8. Delete the relevant adapter created AF structure.

9. Delete the associated health and diagnostics PI points on any or all PI Data Archives created by PI Web API.

10. Start PI Web API.

11. Start the adapter.

Connection issues

PI Web API connection

Perform the following steps to determine if a connection to the PI Web API endpoint exists:

12. Open PI Web API.

13. Select the OmfEgress component of your adapter, for example GVAdapterUbuntu.<Adapter Name>.OmfEgress.

14. Make sure that the following PI points have been created for your egress endpoint:

    • DeviceStatus

    • NextHealthMessageExpected

    • IORate

CONNECT data services connection

Perform the following steps to determine if a connection to the CONNECT data services endpoint exists:

15. Open CONNECT data services.

16. Select Sequential Data Store > Streams.

17. Makes sure that the following streams have been created for your egress endpoint:

    • DeviceStatus

    • NextHealthMessageExpected

    • IORate

TCP connection

Perform the following steps to see all established TCP sessions in Linux:

18. Open a terminal.

19. Type the following command: ss -o state established -t -p

20. Press Enter.