Troubleshooting

This section describes common issues that can occur when AVEVA PI System Connector 3 (PSC3) is caching data and provides guidance for identifying the underlying cause. Use these troubleshooting topics to diagnose connectivity problems, or resource constraints that may prevent cached data from flushing normally.

Cache is growing and not flushing

This condition typically indicates that the downstream broker or destination is unavailable.

1. Verify the broker's health, the destination availability, network connectivity, and available disk space on the connector machine.

2. If the cache is not flushing, verify that the broker reports a healthy status and check file permissions on the cache directories. Additionally, check the cache location path and verify it is assessable.

3. If necessary, restart the connector service and review the logs for processing errors.

Broker frequently reports busy

Frequent busy responses usually indicate that the broker or destination system cannot keep pace with incoming data. Review destination performance, broker resources, network bandwidth, and the connector’s incoming data rate.

Issues when connector and broker are in the same process

In co-located deployments, repeated transitions between memory and disk caching may indicate memory pressure or insufficient system resources. Monitor memory usage, buffer queue depth, and logs for processing errors.

Disk space exhaustion

If disk space allocated for caching is full, data collection may stop. Free disk space immediately or increase the cache size limit.

Identify the root cause (for example, extended outage or undersized allocation) and then implement monitoring alerts for disk space thresholds.

Contact AVEVA Customer Support if data loss is suspected.