This topic describes how to use the Qoder CN diagnostic script to troubleshoot issues such as startup failures for Qoder CN. The script automatically collects system environment context, network configurations, Qoder CN service status, and related logs to help you quickly identify and resolve issues.
1. Download and Run the Script
Download and run the diagnostic tool for your operating system:
Windows Environment
-
Download the script: Download windows_lingma.bat.
-
Execute the script: Locate the file, right-click it, and select Run as administrator.
-
View the results: After the script finishes, it automatically opens the generated log file. The log path appears in the command line window and is typically in the same directory as the script, named Qoder CN_Log_Date_Time.txt.
Linux/macOS Environment
-
Download the script: Download linuxormac_lingma_cn.sh.
-
Execute the script: Open Terminal, navigate to the script's directory, and run the following commands:
-
Grant execute permissions to the script.
chmod +x Linuxormac_lingma_cn.sh -
Run the script.
./Linuxormac_lingma_cn.sh
-
-
View the results: After the script finishes, it generates a log file, typically in the same directory as the script and named Qoder CN_Log_Date_Time.txt.
2. Troubleshooting Suggestions for Diagnostic Results
The following guidance applies to all operating systems (Windows, macOS, Linux). Use the generated log file to troubleshoot issues as follows:
|
Issue Type |
Issue Item |
Solution |
|
Network |
Check proxy settings |
The script checks whether a proxy is enabled. Check the "[Network Settings]" or "[Proxy Settings]" section to confirm that the settings are as expected. If you use a proxy, you need to manually configure the network proxy for Qoder CN in the settings. |
|
Qoder CN Service Status |
Qoder CN process existence |
The script first verifies if the Qoder CN process exists (Lingma.exe for Windows, lingma for macOS and Linux). If an error occurs, check if the installation path is correct. Delete the .lingma directory, restart the IDE, and regenerate the .lingma directory. |
|
Version and startup test |
Review the "[version test]" and "[Start Qoder CN]" sections. Confirm the Qoder CN version information and that it can connect to the public network server. If "failed" is reported, configure a proxy in the settings to access the public network, using the URL from the error message. |
|
|
Process starts but login remains unresponsive |
Windows: Add the process file to the Windows Firewall whitelist (Control Panel\System and Security\Windows Defender Firewall\Allowed apps). Then, retry logging in: C:\Users\xxx\.lingma\bin\2.X.X\x86_64_windows\lingma.exe.macOS/Linux: Check system firewall settings. Ensure the Qoder CN process has network access permissions. |
|
|
If an incompatible program is reported |
If using IDEA, decompression might fail due to insufficient heap memory. Click the Qoder CN icon in the lower-right corner, select Advanced Settings, and change the path to a non-system disk path (ending with an empty folder). Then, restart IDEA. Note
Note that some companies lock binary programs internally, preventing them from running. |
|
|
What if "Qoder CN is starting" is displayed (or a startup error is reported, and the service is unresponsive)? |
|
|
|
System Compatibility |
System and hardware information |
The script collects operating system versions and CPU models. Review the "[Operating System Information]" section. Confirm it meets Qoder CN's system requirements. |
|
Log Analysis |
Qoder CN application logs |
The generated log file records the last few lines (typically 80 lines) of "lingma.log". This helps identify specific errors or warnings during Qoder CN's runtime. Analyze the error messages in the log yourself. |
|
Directory structure and file size |
The script also provides the structure of the Qoder CN installation directory and the size of each file. Use this for space usage checks or file integrity validation. |
|
|
Issues you cannot troubleshoot independently |
Join the DingTalk group "Qoder CN Public Preview Discussion Group (for answers to common questions, see the group announcement first)", group number: |