Administration
Problem | Solution |
---|---|
User cannot log into Listener. | Make sure corporate LDAP group settings are correct and the user is a member of a configured LDAP group. |
Browser complains about insecure SSL/TLS certificate. | Make sure the Listener-installed SSL/TLS certificate is issued by a trusted certificate provider, not self-signed or expired. |
Administrator cannot log into Administration. | Only the super-user administrator can access Listener Administration settings. User-level administrators do not have this privilege. |
Unable to add LDAP settings. | Make sure the username and password are valid. Listener requires original credentials to verify settings. |
Cannot find location to add new users to Listener. | Users are automatically added to Listener the first time they log in. User restriction occurs at the LDAP group level. |
API
Problem | Solution |
---|---|
A deleted item still appears in API. | To allow for Elasticsearch index refreshing, wait at least one second after deletion to confirm the item is deleted. |
Data Ingestion
Problem | Solution |
---|---|
Ingest API returns the 201 status code, but data does not appear to be landing. | Send a test packet with Header Sync=1 and see if UUID is returned with the 201 status code. |
When writing to Teradata, data is not inserted and the following error message appears: Bad parameter type, could not bind. | Make sure Teradata column data type is varchar, json, or clob. Currently, these are the only supported data types for Teradata. |
When writing to Aster, data is not inserted and the following error message appears: Bad parameter type, could not bind. | Make sure Aster data column data type is varchar or text. Currently, these are the only supported data types for Aster. |
When using /messages endpoint and sending an array of JSON docs, target table has a single character as each message/record. | This occurs when the JSON array is invalid. Make sure the JSON array is valid. |
When using /messages endpoint, when an array of JSON docs are sent, target table has single char as each message/record. | Check if the JSON array is valid. This happens when Ingest services finds the JSON array invalid. |
MQTT
Problem | Solution |
---|---|
Messages are not getting to the source. | Make sure the topic is valid. |
State of the source indicates a bad broker. | Check for network blocks from MQTT to Listener. |
Scalability
To configure the auto-scaling paradigm for Ingest micro-service, an administrator sets the maximum number of micro-service replicas through the API or UI. The minimum cannot be changed.
Problem | Solution |
---|---|
The users on your system are getting frequent responses of 502, 503, or 504; or they are unable to ingest data. | As an administrator, identify if additional Ingest micro-services are needed by comparing the ones currently running versus the maximum available to autoscaler. For API ("current_replicas" and "max_replicas") instructions, see Get Autoscaling Details. For UI instructions, see Resource Management. |
Autoscaler needs additional ingest services. | As an administrator, update auto-scaling after identifying the need for addition ingest micro-services. For API instructions, see Update Autoscaling. For UI instructions, see Adjusting the Ingest Rate. |
Sources
Problem | Solution |
---|---|
Dashboard is empty after user created sources. | Star sources to see them on the dashboard. |
The following error message appears: {"title":"Could not save this source","content":"Data validation error: Owner attribute is required"}. | Log out and back into Listener. |
Systems
Problem | Solution |
---|---|
User does not have access to add a target system (Teradata, Aster, HDFS, or HBase). | Make sure the user has administrator privileges. Only administrators are allowed to add systems to Listener, which non-administrator users can then select to create targets. |
Administrator cannot add or verify an HDFS system. | Make sure the URL/IP is prefaced by hdfs:// and ends with the :port-number. |
Administrator cannot validate and save a new system. | Turn off autofill in the browser. |
Targets
Problem | Solution |
---|---|
Data is not inserted into the target system. | Make sure the user credentials supplied have proper privileges to access and insert data on the target system. |
Cannot retrieve column data from Teradata after checking valid target credentials. | Make sure the user has proper privileges for getColumnPrivileges and getColumn on the Teradata system:Select access on DBC.Tables[V][X] Select access on DBC.Columns[V][X] Select access on DBC.AllRights[V][X] Select access on DBC.UDTInfo |
Target is stuck in deploy mode. | Make sure there are enough resources to deploy a new target. |
Administrator cannot add a target from Manage Targets. | Make sure at least one source exists in Listener and the source is selected in the target form. |
Connection to a WebSocket target fails and the following message appears: 503 Service Unavailable. | Reattempt the WebSocket connection until it makes a successful connection. |
Writer
Problem | Solution |
---|---|
When transactions, such as insert or delete, are run on a Teradata table by anyone other than Listener, writer errors out because of deadlock. User cannot find any new data in the target table. | If you want to modify data while Listener is writing, use partition tables instead of regular tables. |
Insert query fails because of data type mismatch, and the following error message appears in the Manage Targets view under the target name: Target error. | Click VIEW ERROR DETAILS under the target error message for more information. |
Target was created successfully, but the data is not being written to the target table. | Check the target status on UI. If Target is writing data in near realtime/batches, the writer was deployed successfully. |
Writer errors out because of deadlock when transactions, like insert or delete, are performed on Teradata table by anyone other than Listener. | Use partition tables instead of regular table to modify data while Listener is writing. |
User Interface
Problem | Solution |
---|---|
Unable to add LDAP settings. | Make sure the username and password are valid. Listener requires original credentials to verify the entered settings. |