Frequently asked questions and answers during the installation and use of VMware Workstation+openGauss

Frequently asked questions and answers during the installation and use of VMware Workstation+openGauss

For specific installation steps of openGauss3.1.1, see

1. Installing and deploying openGauss 3.1.1 Enterprise Edition Database on x86_64 architecture + VMware® Workstation 16.2.3 Pro virtual machine + openEuler20.3-LTS Detailed Instruction Manual One - openGauss 3.1.1 Enterprise Edition Database
2. Installing and deploying openGauss 3.1.1 Enterprise Edition Database Instruction Manual Part 2 on x86_64 architecture + VMware16.2.3 Pro + openEuler20.3-LTS – Use of client tools
3. Quickly deploy (one-click installation) openGauss 3.1.1 Enterprise Edition Database Instruction Manual on x86_64 architecture + VMware16.2.3 Pro + openEuler20.3-LTS

Question 1: Computer BIOS virtualization disabled problem

Answer: If the problem shown in the picture appears when installing VMware Workstation, it is because your computer BIOS has disabled intel vt, virtualization is disabled, and virtualization is disabled in the computer BIOS. You can turn on virtualization by modifying the BIOS. .

Problem 2: Not having permission to execute VMware, as follows:

Answer: If VMware does not have execution permissions, as shown in the figure, you can use the following methods to solve the problem. Right-click as shown in the picture and select "Run as administrator" VMware Workstation

Question 3: Data Studio failed to connect to the openGauss database, prompting "Error connecting to the server, connection failed!"

Answer: The JDK version on the computer host (Windows) system is not compatible. Different DataStudio versions require different JDKs. For example, the JDK version requirement is 1.8, JDK11, etc. Re-download and install the JDK and modify the global variables.

Note: If the JDK version cannot be modified, you can use other tools to connect to the database, such as using navicat to connect to opengauss. See the manual for client tools to use the database. If the MAC operating system cannot use the Data Studio tool, you can also use Navicat.

Question 4: Data Studio has an error connecting to the openGauss database. The error message is as follows:

Answer: There is a problem with the connection configuration. Follow the steps below to find out:

Step 1: Confirm whether the database gs_om -t start has been started, and use gsql to connect to the database (connection user and password, the user cannot be the omm user)

Step 2: Confirm the whitelist configuration. The operation manual client tool uses database configuration.

Question 5: The omm user exits to the root user.

Answer: Use the exit command.

Question 6: When gsql connects to the database, it prompts "unknow:26000", as shown below:

Answer: If you confirm that the port number is 26000 and there is no problem, it means that the database service has not been started. You need to start the database service gs_om -t start , as follows:

Question 7: When using the database for the first time, it prompts that the username and password must be changed, as follows:

Answer: When using the database for the first time, you must change the omm user password: alter role omm identified by 'new password' replace 'old password';

No error will be reported when performing other operations

Note: If you forget your omm password, you cannot modify it. Please exit the database and enter gs_guc reload -N all -I all -c "modify_initial_password = false" to turn off the password modification setting.

Question 8: The SSh connection to the remote server suddenly failed, and the error Socket error Event: 32 Error: 10053. connection closing…socket close. connection closed by foreign host. disconnected from remote host Socket error Event: 32 Error: 10053.

Answer : There is a conflict in the intranet IP address. If it is a static address configuration, please modify the static address. If it is automatically assigned by DHCP, please restart VMware workstation, configure it automatically, and then use Xshell to connect with the new address. https://zhuanlan.zhihu.com/p/58336487

Question 9: VMware reports an error when importing ova files

VMware reports an error when importing ova files - the import failed and the consistency compliance check was not passed

Answer : The above problem is usually caused by different versions of VMware's built-in ofvtool tool, which results in incompatibility. Simply uninstall the original VMware installed inside and reinstall the VMware version corresponding to ova.

Question 10: Remote clients like Xshell cannot connect to the virtual machine. This may be caused by the missing virtual network card of the VMware or virtualbox virtual machine.

Phenomenon: When connecting to a virtual machine through , but the virtual network card may be missing due to some reasons after installation or possibly after installation, which will cause problems like Xshell's remote client being unable to connect to the virtual machine. For example, VMware is missing VMware Network Adapter VMnet1 and VMware Network Adapter VMnet8.

If virtualbox is missing virtualbox-host-only-network

Answer:
The first method: restore the default settings method
(1) For virtualbox, automatically configure the network card and restart.

(2) Use the following steps for VMware

Second method: If the first method does not solve the problem of missing virtual network card, try uninstalling + cleaning the registry + reinstalling.
Step 1: Uninstall the corresponding virtual machine, such as VMware or Virtual Box.
Step 2: Use everything to search for VMware or Virtual Box on your computer, and then choose to delete useless content.
Download everything from the official website https://www.voidtools.com/zh-cn/

Step 3: Use CCleaner to clean and repair the registry.
(1) Enter CCleaner official website: https://www.ccleaner.com/zh-cn, download the free version and install it

(2) Press 1 Registry => 2 Select All => 3 Scan for Problems

Continue as follows.

Step 3: Reinstall VMware or virtualbox virtual machine.

Question 11: Solution to "vmx86 version mismatch problem" encountered when starting VMware

Answer:
Method 1: Find the matching version of the driver vmx86.sys and copy it to overwrite the original version.
Step 1: Close VMware.
Step 2: Modify the name of vmx86.sys on your computer, such as changing it to oldvmx86.sys.
Search your computer with the full text of everything. Driver vmx86.sys, find all and modify the names of all vmx86.sys on your computer, for example, change it to oldvmx86.sys

Download everything from the official website https://www.voidtools.com/zh-cn/
Step 3: Copy vmx86.sys that matches the version and put it in each corresponding location.
Copy the driver vmx86.sys of the VMware virtual machine that matches the version to you. where vmx86.sys is located and then delete oldvmx86.sys

Method 2 (refer to question 10) :
Step 1: Uninstall the corresponding virtual machine, such as VMware or Virtual Box.
Step 2: Use CCleaner to clean and repair the registry.
(1) Enter CCleaner official website: https://www.ccleaner.com/zh-cn, download the free version and install it

(2) Press 1 Registry => 2 Select All => 3 Scan for Problems

Continue as follows.

Step 3: Reinstall VMware or virtualbox virtual machine.

Question 12: When using gsql and navicat client tools in openGauss, a connection timeout will occur. For example, navicat will have the following error.

Reason: By default, when the client is idle after connecting to the database, it will automatically disconnect based on the default value of the session_timeout parameter. Parameter description: Indicates the maximum time for no operation after establishing a link with the server. The value range of this parameter: integer, 0-86400, the minimum unit is seconds (s), 0 means turning off the timeout setting. Default value: 10min, 86400s=24 60 60s, that is, 24 hours a day.
Solution: It can be solved by setting the session_timeout value.
(1) Set
ALTER DATABASE db_uni set session_timeout=86400 for 1 day and 24 hours;
or
(2) Turn off the timeout setting
ALTER DATABASE db_uni set session_timeout=0;
Question 13: VMware cannot connect to the virtual machine. Please make sure you have rights to run the program, access all directories used by the program, and access all temporary file directories or VMX exits early.

Reason: The virtual machine VMware has been damaged and the virtual machine authority authentication service cannot be started.

***Solution: ***Go into the service and change the startup type of VMware Authorization Service to delayed startup.
1. Win+r and enter services.msc

2. Find VMware Authorization Service, right-click and click Properties

3. Modify the startup type of VMware Authorization Service to automatic (delayed startup)

4. Restart vmware.
5. If the problem persists, uninstall VMware and then reinstall VMware.