weizhouapache commented on issue #10648:
URL: https://github.com/apache/cloudstack/issues/10648#issuecomment-2809471214

   > node4 console connection after restarting cloudstack agent
   > 
   > ```
   > 2025-04-16 15:17:02,932 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-5:null) (logid:38a02db1) Request:Seq 
4-2075033528310956043:  { Cmd , MgmtId: 345049528973, via: 4, Ver: v1, Flags: 
10001
   > 1, 
[{"com.cloud.agent.api.GetVncPortCommand":{"id":"21","name":"i-2-21-VM","wait":"0","bypassHostMaintenance":"false"}}]
 }
   > 2025-04-16 15:17:02,933 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-5:null) (logid:38a02db1) Processing command: 
com.cloud.agent.api.GetVncPortCommand
   > 2025-04-16 15:17:02,933 DEBUG 
[agent.properties.AgentPropertiesFileHandler] (agentRequest-Handler-5:null) 
(logid:38a02db1) Property [hypervisor.uri] has empty or null value. Using 
default valu
   > e [null].
   > 2025-04-16 15:17:02,933 DEBUG [kvm.resource.LibvirtConnection] 
(agentRequest-Handler-5:null) (logid:38a02db1) Looking for libvirtd connection 
at: qemu:///system
   > 2025-04-16 15:17:02,938 DEBUG [kvm.resource.LibvirtVMDef] 
(agentRequest-Handler-5:null) (logid:38a02db1) Using informed label [hdc] for 
volume [null].
   > 2025-04-16 15:17:02,940 DEBUG [cloud.agent.Agent] 
(agentRequest-Handler-5:null) (logid:38a02db1) Seq 4-2075033528310956043:  { 
Ans: , MgmtId: 345049528973, via: 4, Ver: v1, Flags: 10, [{"com.c
   > 
loud.agent.api.GetVncPortAnswer":{"address":"10.66.50.54","port":"5900","result":"true","wait":"0","bypassHostMaintenance":"false"}}]
 }
   > ```
   > 
   > much faster and in browser opens immediately
   
   this looks good
   
   it looks like this step caused the issue
   ```
   LibvirtConnection.getConnectionByVmName(vmName);
   ```
   I wonder if it is because of different storages (we use NFS)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to