Cluster Computing Related Issues
Node Discovery Issues
1.Both the computing engine and the master node are running, but why can’t the master node detect the computing engine?
- Possible Cause 1: The current computing engine and the master node are not on the same subnet, resulting in the failure to detect the computing engine.
- Solution: Contact technical staff to ensure the master node and the computing engine are on the same subnet.
- Possible Cause 2: A proxy/VPN-related software may be enabled, which prevents proper node detection.
- Solution: Disable such software and restart the computer. Make sure the software does not automatically start after reboot.
- Possible Cause 3: Due to abnormal conditions, a previously launched computing engine process may not have fully exited.
- Solution: Open the Task Manager, go to the Details tab, and check if there is a process named LiDAR360MLSEngine.exe. If it exists, right-click the process and select End Task.
2.Open log prompt: Please go to the LiDAR360MLS computing engine running this task to view the log.
Possible cause: The log file path cannot be accessed directly from the current machine.
Solution: Check the machine where the log path is located, and view the log on that machine.
Environment Issues
1.When running Gaussian-related cluster functions, the system may prompt that the required environment is missing. In this case, follow the prompt to install the required environment, and restart the computing engine before using it.
2.The language of LiDAR360MLS Engine and LiDAR360MLS Master be consistent with LiDAR360MLS. To change the language, please launch LiDAR360MLS to switch the language, and then restart LiDAR360MLS Engine and LiDAR360MLS Master.
3.During program execution, make sure the computer does not enter sleep or hibernation mode, as this will interrupt the network connection and may cause the program to malfunction.