DataWay List Empty in Integration

As shown in the figure below:

Troubleshooting Approach¶

Assumption 1: The backend management interface does not display the version number. After installing DataWay, only the version number indicates a successful connection.

As shown in the figure:

1. First, check whether the DataWay configuration file is correct — whether the correct listening port and Workspace token information are configured.
2. Check whether the DataWay service is running normally.

kubectl get pods -n launcher

1. Whether there are errors when running normally.

kubectl logs -f -n launcher <launcher_name>

1. Check whether the deployed kodo service is abnormal. Confirm by examining the kodo service logs.

2. First, enter the pod of the kodo service.

kubectl exec -ti -n forethought-kodo <kodo_pod_name> -- /bin/bash

• Then, go to the /logdata directory and view the log files.

cd /logdata
tail -f logs

1. Check whether the DataWay service can communicate normally with the kodo service (including whether the dataway server has not added the correct resolution of the df-kodo service in the hosts file).
2. Go to Studio Integration and check the DataWay list to see if it is normal.

Assumption 2: The backend management interface displays the version number, but the DataWay list under the DataKit module in Studio Integration is empty.

1. The above issues have been resolved, but the list is still empty.
2. If you have deployed before, it may be caused by the Redis cache not being cleared. If no persistent storage is configured, restart the container.

kubectl delete pods -n middleware <redis_pod_name>