Subscriber is not receiving data

The Data Streamer successfully started and is operational, but a subscriber is not receiving data.

Cause

The cause might be one of the following problems:

The policy file is incorrect.
The policy file is referencing an incorrect tag to the file path for a data stream. If the trace is activated, check the logs for message HBO6021E, which indicates that an incorrect tag is present in the policy file.
The subscriber is subscribed to the wrong streams.
The parameters that are used to connect to the subscriber are incorrect.
The Data Streamer cannot connect to, or is trying to reconnect to, the subscriber.
The data packets are being discarded.
The data gatherer (Log Forwarder or System Data Engine) is not connected to the Data Streamer.

To resolve the problem, complete one or more of the following steps, as appropriate:

Verify that the policy file is correct. Also, verify that the subscriber is subscribed to the correct data streams, and that all parameters that are used to connect to the subscriber are correctly defined.
If the policy file contains data streams that have no subscribers, the logs include message HBO6020E.

If you update the policy file, rerun the Data Streamer with the correct policy file.
Check the logs to determine whether a connection is established between the Data Streamer and the subscriber. Message HBO6012E indicates that this connection is not established.
Verify that the subscriber host and port is correct and available for connection.
Check the logs to determine whether a connection is established between the Data Streamer and the data gatherer (Log Forwarder or System Data Engine). Message HBO6003I indicates that this connection is established.
If the connection is established, also verify that the data gatherers are providing output to the Data Streamer.

For more information about troubleshooting the connection between the Data Streamer and the System Data Engine, see Data Streamer is not receiving data from System Data Engine.