Skip to main content
Question

Unable to browse Linux vm file (AHV)

  • September 29, 2025
  • 4 replies
  • 35 views

Forum|alt.badge.img+1

hello guys,

after deploying FREL vm (qcow2), script deployment went fine but can’t seem to browse vm files when restoring, CS is all in one deployment, i’ve checked the logs and this is what i found :

WebServer.log :

IdxBrowseClientCache initialized a new browse session [1758805201-125]
6208  4d38  09/25 15:00:01 ### CVOnDemandSvcClient::SubmitTask() - Unable to attach to cvd at myFrelVmHostName*myFrelVmHostName*8400*8402 to launch on demand service.Error is 0xE8090011:{CCvNetwork::Attach_RemotePort(1453)} + {CCvNetwork::GetConnection(3327)} + {CSessionConnectionSocket::GetConnection(225)} + {CSessionConnectionSocket::ParseLastError(170)/EventMessage.0x09000011.9:17. (Localized string unavailable)}
6208  4d38  09/25 15:00:01 ### IDXBROWSECL Failed to send browse request to mediaagent [myFrelVmHostName*myFrelVmHostName*8400*8402]. Error:[0xE8090011:{CCvNetwork::Attach_RemotePort(1453)} + {CCvNetwork::GetConnection(3327)} + {CSessionConnectionSocket::GetConnection(225)} + {CSessionConnectionSocket::ParseLastError(170)/EventMessage.0x09000011.9:17. (Localized string unavailable)}]
6208  4d38  09/25 15:00:01 ### IdxBrowseClientCache_Browse() - Error. Failed to Browse IdxBrowseClientCache error [-1]

 

REMOTELIVEBROWSE.log

Mount not active on [remote=myFrelVmHostName*myFrelVmHostName*8400*8402, proxy=ctnsi-cv-10-frel-01]

 

both CS and Frel can ping each other using ip or hostnames, don’t know where to start troubleshooting this.

4 replies

Forum|alt.badge.img+8
  • Vaulter
  • September 30, 2025

Hi Houssam,

My recommendation would be to check the FREL itself.

On the FREL check FBR.log, browse.log and cvd.log to begin. You’re looking for events around 09/25 15:00:01

It may also help to check cvfwd.log to rule out some network outliers but it sounds like this is more to do with the block level driver, pseudomounting or something of that nature with the information provided.

Cheers,


Forum|alt.badge.img+1
  • Author
  • Bit
  • October 1, 2025

hello ​@Jace Ross

humm not sure where to find FBR.log 


Forum|alt.badge.img+8
  • Vaulter
  • October 1, 2025

Hi Houssam,

It resides in /var/log/commvault/Log_Files of a FREL.
The log should be created once the node is configured as a FREL. You should also have cvfbr_validate.log, this is the log that confirms whether the instance is appropriately configured to function as a FREL. If it has failed at this point you won’t be able to browse and I don’t believe FBR would have logged either.

Cheers,


Forum|alt.badge.img+1
  • Author
  • Bit
  • October 1, 2025

Hi Jace,

before answering i wanted to precise the environment version 

CS :  11.40.6

FREL : 11.24

AHV : 10.3.0.2

AOS : 7.3.0.6

so yeah cvfbr_validate.log seems fine, it says “All operations completed. myFrelVmHostName has been set as a valid FBR MA

but no fbr.log file found, 

on the cvfwd.log this is what it is saying :

1504 05e0 10/01 14:51:23 ######## ######## Reporting the client ONLINE
1504 05e0 10/01 14:51:53 VT:00005 CN:00705 [local->ctnsi-cv-10:50023] Successfully completed client connection {ff1e2f89-aece-60e2-58c9-eaecd7f9d6d0} via OT:00004
1504 05e0 10/01 14:51:53 VT:00005 CN:00706 [local->ctnsi-cv-10:49858] Successfully completed client connection {0362fee0-ef45-badf-710f-432fd903d303} via OT:00004
1504 05e0 10/01 14:51:54 VT:00005 CN:00707 [local->ctnsi-cv-10:49858] Successfully completed client connection {c2dfe71f-d26a-7e9e-7c65-be8534f1c1d7} via OT:00004
1504 05e0 10/01 14:53:13 VT:00005 CN:00709 [local:8400<-ctnsi-cv-10] Completed client connection {df37ef45-d9bd-3509-ee88-7d94eba68eb7} to local:8400
1504 05e0 10/01 14:53:13 VT:00005 CN:00710 [local:50469<-ctnsi-cv-10] Completed client connection {5f6b0ee6-d4e5-a97c-67c6-08c0153ae3be} to local:50469
1504 05e0 10/01 14:53:13 VT:00005 CN:00711 [local->ctnsi-cv-10:49865] Successfully completed client connection {86b97831-d05c-b279-131c-c81b2ebc6b0a} via OT:00004
1504 05e0 10/01 14:53:43 VT:00005 CN:00712 [local->ctnsi-cv-10:49858] Successfully completed client connection {bb3f17b9-fa22-3712-e1c5-c4bc9d47f8b7} via OT:00004
1504 05e0 10/01 14:53:43 VT:00005 CN:00713 [local->ctnsi-cv-10:49865] Successfully completed client connection {90ea1090-ecfb-ec1e-1043-6a725b32c47b} via OT:00004
1504 05e0 10/01 15:07:22 VT:00005 CN:00714 [local:8400<-ctnsi-cv-10] Completed client connection {a37a03f9-a9a9-9989-9e79-791df402573e} to local:8400
1504 05e0 10/01 15:07:23 VT:00005 CN:00715 [local:8400<-ctnsi-cv-10] Completed client connection {e1603bdd-178b-9dc4-ce9f-7fc22714a187} to local:8400
1504 05e0 10/01 15:07:28 VT:00005 CN:00716 [local:8400<-ctnsi-cv-10] Completed client connection {dba069ca-3a29-016f-597f-49e72f3a15dd} to local:8400
1504 05e0 10/01 15:07:29 VT:00005 CN:00717 [local:8400<-ctnsi-cv-10] Completed client connection {f4d21def-92fb-e44b-cbd1-806723585877} to local:8400
1504 05e0 10/01 15:07:29 VT:00005 CN:00718 [local:8400<-ctnsi-cv-10] Completed client connection {d357f79a-0e37-7ac1-4a41-0f927e9ab802} to local:8400
1504 05e0 10/01 15:07:29 VT:00005 CN:00719 [local:8400<-ctnsi-cv-10] Completed client connection {2200dcf3-4cbc-c11c-bf07-115224c125fb} to local:8400
1504 05e0 10/01 15:07:29 VT:00005 CN:00720 [local:8400<-ctnsi-cv-10] Completed client connection {6c08989c-5e01-e6e4-b3bb-6b9e17374a84} to local:8400
1504 05e0 10/01 15:07:29 VT:00005 CN:00721 [local:8400<-ctnsi-cv-10] Completed client connection {2e28c72f-9d9e-bb1b-cf16-0b598135c4d9} to local:8400
1504 05e0 10/01 15:08:23 ######## ######## Service cvd terminated
1504 05e0 10/01 15:08:23 ######## ######## Reporting the client OFFLINE