Introduction

JumpServer provides multiple ways to connect to database assets: users can utilize web-based tools such as web CLI, web GUI, and a common database connection tool on RemoteApp. Users can also use local database tools(DBeaver,Navicat,etc) to securely access databases through JumpServer's transparent proxy tool.

These different connection methods are provided by different components: Web CLI is provided by the Koko component, Web GUI is provided by the Chen component, RemoteApp is provided by Tinker on RemoteApp machine, and the local client is facilitated by the Magnus component's proxy implementation.

Server trace files are stored in the /data/jumpserver/ for reference during troubleshooting. 

Common Issues for Magnus(DB Client and DB Guide)

1. Oracle: No more Data to Read From Socket

Cause：

Magnus transparent proxy tool currently does not support Oracle instances with character sets other than UTF-8 while using thin mode.

Troubleshooting tips:

1. Ensure that the ojdbc used by the local database tool is compatible with the target database assets.

2. You can use the following SQL statement to query the character set used by the instance:

SELECT parameter, value
FROM nls_database_parameters
WHERE parameter IN ('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET');

If it is a non-UTF-8 instance, you can configure the local OCI for the connection.

Common Issues for RemoteApps(Applet)

1. Connection Error or API Error

Cause：

These problem happen when RemoteApp is not functioning properly.

Troubleshooting tips:

Please refer to the following article to troubleshoot the status of the RemoteApp machine.

2. Module Not Found Error: No module named 'win32ui'

Cause:

The main reason for this issue is that the RemoteApp autofill feature, which relies on Selenium, is missing some Python libraries. The cause of this problem may be related to the environment of RemoteApp machine.

Troubleshooting tips: 

Manually install the missing library on the RemoteApp Machine by running the following command:

pip install --upgrade exceptiongroup

Common Issues for Koko and Chen(Web CLI and web GUI)

1. Redis Account Verification Error / Authentication Failed

Cause:

Authentication errors due to different login authentication methods in different versions of Redis.

Troubleshooting tips: 

Please identify the version of Redis being used and select the platform for the asset accordingly. When Redis asset authentication does not require a username, configure the username as 'null'.

2. Connection Websocket Error

Cause:

The issue may be due to sessions not being properly maintained or an administrator setting a disconnect time for asset sessions in the system security settings.

Troubleshooting tips: 

1. Check for multiple layers of reverse proxies. Ensure that the reverse proxy is configured to maintain WebSocket long-lived connections.

2. Check if the asset session in the security settings of JumpServer has a time limit set.

3. Check the stability of the network between JumpServer and the assets.