ONE Troubleshooting Guide

After ONE has been idle for a long time, for example, over 12h, the first subsequent job does not progress past the Submitted state. Any following jobs are performed without issues.

There is an issue with how the logging context is cleared after a subscription attempt fails.

There are two options depending on whether you need to use auditing in Data Processing Module (DPM) or not:

Compared to earlier versions, DPE might spend more time in the STARTING status before it begins processing data.

This behavior is expected. Starting from 13.9.0, queries used for reading data (such as get the row count or get the last partition) are executed in DPE instead of DPM. As a result, the DPM throughput was significantly improved although DPE might initially appear slower in comparison.

Runtime job takes too long to process.

Enable performance profiling in the Global Runtime Configuration. This way you can view the individual runtime steps to identify performance issues that might have occurred during execution.

<?xml version='1.0' encoding='UTF-8'?>
<runtimeConfiguration>
  <runtimeComponents>
  <runtimeComponent samplingPeriod="20" class="com.ataccama.dqc.processor.monitoring.sampling.SamplingComponent">
    <writers>
      <writer filename="dqc_sampling_output.txt" stdout="false" detailed="true" class="com.ataccama.dqc.processor.monitoring.sampling.writer.SamplingTextWriter"/>
      <writer filename="dqc_sampling_output.dot" stdout="false" class="com.ataccama.dqc.processor.monitoring.sampling.writer.SamplingDotWriter"/>
    </writers>
  </runtimeComponent>
</runtimeComponents>
</runtimeConfiguration>

Users that have been imported from Keycloak are not correctly updated in ONE. The same issue can occur in earlier releases, but as it causes the application to fail, the same solution cannot be applied.

To determine what caused the synchronization issue, start by checking the Metadata Management Module (MMM) logs. To do so, follow these steps:

The issue can be resolved in one of the following ways. As all of them have some drawbacks, the most suitable solution depends on your needs and particular use case.

When trying to manually upload a lookup file (Lookup Items tab), it fails with the following error: Upload of <user_file>.lkp failed.

To determine what caused the upload issue, open the log file and look for the error message. If the error is Refused to connect to <URL>, the property that allows the connection from ONE to ONE Object Storage (MinIO) is likely misconfigured or missing.

Make sure the MinIO URL is correctly configured in the property ataccama.one.webserver.content-security.extra-urls.

Full-text search is broken for some users. Instead of search results, you see a Full-text Search is experiencing problems error and after refreshing a Socket closed error message.

Ataccama ONE communicates with the web browser using WebSocket. If your proxy removes headers from server responses, the WebSocket communication cannot be established between the browser and the servers where the Ataccama ONE is installed. Consequently, the servers cannot push notifications to the client browser, causing issues such as non-functional search.

To solve the issue, your network administrator must allowlist the Connection header for network communication for the platform domain (for example, <customer_domain>), subdomain (for example, one.<customer_domain>), or link, with the latter being more strict than the previous.