GL-RM1 "Binding failed, unable to obtain basic KVM device information."

[larsony99]

Hello, I only found one other post on this subject. I cannot bind my Comet devices to the app. Here is an example log.

glkvm_app_log.txt.zip (12.6 KB)

[yanchuanbin]

We apologize for the inconvenience. To help us troubleshoot further, please provide the following information:

1. Verify that the device’s white LED remains solidly lit. A continuously lit LED indicates the network connection is functioning properly.

2. Access the device over your local network. In a browser, navigate to http://glkvm.local or the device’s LAN IP address to open its web interface.

3. Within the web interface, click Toolbox, then Access to open the device-management SSH terminal page.
   

   

4. On the terminal page, run the ping command to check whether the device can resolve domain names properly. Please take a screenshot of the results for our review.

   ping gslb-us.goodcloud.xyz
   

5. Ensure the DNS process is running normally by executing:

   netstat -ntlp
   

   Please keep a screenshot of this output for our records.

6. Export the device’s log files by clicking Help, then selecting Export Log Files in the web interface. Please attach these logs so we can analyze them.
   

   

Once you’ve gathered this information, share it with us and we’ll continue assisting you.

[yanchuanbin]

If DNS issues persist, update the device firmware to the latest version (v1.4.0) via the web interface. New beta test firmware: 1.4.0 beta1 for RM1(Comet)

[larsony99]

Hello, ping is working properly, please see attached.

I also ran the netstat command, and I have that saved. I'm not sure what I should be looking for in that though.

Please see attached log file as well.
system_logs_20250811_133954.zip (50.6 KB)

[larsony99]

Is it possible to rollback to the latest stable firmware, or will my devices be on this firmware until the stable version is released?

[yanchuanbin]

From your device logs, it appears that the DNS client of the device is experiencing abnormal operation. You can try restarting this service to pull up the DNS client first

/etc/init.d/S45connman restart

If the command shows successful startup after execution, you can wait for a while and bind the device again on the client side.
If the above methods cannot solve the problem, it is necessary to update the firmware to resolve it. This issue is not present on all devices and is related to specific network environments. We have fixed it in firmware version 1.4.0. The latest firmware version 1.4.0 will be released in the next two days. You can use the firmware from the last reply for the update, or wait for 1-2 days and we will push the new firmware. After the new firmware version is pushed, you can enter the web interface and manually click on the update button to update to version 1.4.0

[larsony99]

I ran that command, which did not fix the issue. I then updated the firmware, and I'm still getting an error.

[minmie]

Please try ot upgarde to 1.4.1R1 , I already push it to server.
if it still not work , please provide debug log again

[larsony99]

The latest firmware released today fixed the issue. However, now I have a different issue; I can't see my ATX board on the unit that it's attached to.