Server Version FAQ

VeloDB Cloud Studio

Login failed, unable to log in

1. Please check whether the username and password are correct. You can use mysql cli for testing.
2. Please check whether the network connection is normal. You can use the ping command to check whether the network is unobstructed.

VeloDB Cloud console failure, can Studio be used normally?

Yes, the console is out of date, Studio is still working properly. Studio and console are two separate services.

Enterprise Manager Studio

Can Studio be accessed independently without going through the Manager port?

Click Studio to access on the Manager interface. You need to log in through the Manager authorization. If you skip the Manager authorization Independent access to Studio, you can access it via http://<ip>:<studio_port>, where <studio_port> is configured for Manager The Studio port can be configured in the WEBUI_PORT in manager.conf, with the default value of 8006.

How to enable audit log?

For repositories connected to VeloDB version >= 2.1.0, Studio supports one-click activation of the audit log plug-in for the cluster on the interface. For repositories with VeloDB version < 2.1.0, please refer to Auth Log Plugin (opens in a new tab) Install the audit log plug-in by yourself.

Where are the Studio logs located?

The logs of Enterprise Manager Studio are located in the <manager_deploy_path>/deps/webui/log directory.

How much memory should be allocated to Studio?

The memory footprint of Studio depends on the size of the cluster and the scale of users simultaneously. Generally speaking, Studio's memory footprint will not be too high. It is recommended that 1 ~ 2GB of memory is enough.