VLSR - Failed to generate system log bundle : The connection was closed by the remote end during handshake
search cancel

VLSR - Failed to generate system log bundle : The connection was closed by the remote end during handshake

book

Article ID: 367076

calendar_today

Updated On:

Products

VMware Live Recovery VMware Site Recovery Manager 8.x

Issue/Introduction

You are unable to download SRM log bundle from UI because it throws the error. 

ERROR
Operation Failed
Failed to generate system log bundle. Internal error: Operation not permitted: The connection was closed by the remote end during handshake..
Operation ID: 17d0f920-c9c6-4d54-ae10-ba1f82783735


/var/log/vmware/dr/drconfig.log:

2024-02-06T05:40:26.627Z verbose drconfig[16713] [SRM@6876 sub=DrConfigDiagnosticManager opID=5e398f13-f64d-4fa8-84eb-fe32f43efd9d-generateSystemLogBundle:9a3e] Support bundle script output:
--> cp: cannot stat '/opt/vmware/etc/sfcb/sfcb.cfg': No such file or directory
--> cp: cannot stat '/opt/vmware/etc/vami/vami.xml': No such file or directory
--> cp: cannot stat '/opt/vmware/var/lib/vami/services.xml': No such file or directory
--> /usr/bin/cp: -r not specified; omitting directory '/opt/vmware/srm-dbtool/logs/srm-dbtool'
-->
--> **** Errors reported!!!
--> **** Exit code 1
-->
-->
2024-02-06T05:40:26.627Z info drconfig[16713] [SRM@6876 sub=DrConfigDiagnosticManager opID=5e398f13-f64d-4fa8-84eb-fe32f43efd9d-generateSystemLogBundle:9a3e] Support bundle script command exit code: 1
2024-02-06T05:40:26.627Z error drconfig[16713] [SRM@6876 sub=DrConfigDiagnosticManager opID=5e398f13-f64d-4fa8-84eb-fe32f43efd9d-generateSystemLogBundle:9a3e] Support bundle command returned non-zero exit code: 1 (Operation not permitted: The connection was closed by the remote end during handshake.).
--> cp: cannot stat '/opt/vmware/etc/sfcb/sfcb.cfg': No such file or directory
--> cp: cannot stat '/opt/vmware/etc/vami/vami.xml': No such file or directory
--> cp: cannot stat '/opt/vmware/var/lib/vami/services.xml': No such file or directory
--> /usr/bin/cp: -r not specified; omitting directory '/opt/vmware/srm-dbtool/logs/srm-dbtool'
-->
--> **** Errors reported!!!
--> **** Exit code 1
-->
-->
2024-02-06T05:40:26.628Z error drconfig[16713] [SRM@6876 sub=DrConfigDiagnosticManager opID=5e398f13-f64d-4fa8-84eb-fe32f43efd9d-generateSystemLogBundle:9a3e] Error during bundle file generation
--> (dr.fault.InternalError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    reason = "Operation not permitted: The connection was closed by the remote end during handshake."
-->    msg = ""
--> }

Cause

This is caused by upgrading SRM to 8801 or 8802. After upgrade, it creates the srm-dbtool file in the location '/opt/vmware/support/logs/srm-dbtool' abnormally thereby blocking support bundle downloads. 

This problem only affects upgraded SRM appliances (Upgrading to SRM 8.8.0.1/8.8.0.2), new deployments of SRM appliance aren't affected by this.

You also can't download logs manually - 

root@srm [ /opt/vmware/dr/bin ]# ./dr-support-linux.sh
cp: cannot stat '/opt/vmware/etc/sfcb/sfcb.cfg': No such file or directory
cp: cannot stat '/opt/vmware/etc/vami/vami.xml': No such file or directory
cp: cannot stat '/opt/vmware/var/lib/vami/services.xml': No such file or directory
/usr/bin/cp: -r not specified; omitting directory '/opt/vmware/srm-dbtool/logs/srm-dbtool'

**** Errors reported!!!
**** Exit code 1

Resolution

Upgrade to 8.8.0.3, 23263427 or SRM 9.0, 23464738


Workaround: 

Remove 'srm-dbtool' from this location. Run the command: rm -rf srm-dbtool

root@srm [ /opt/vmware/srm-dbtool/logs]# ls
srm-dbtool

This must allow you to download the support bundle.