Problem of S6805 NETCONF not being able to connect at a location

NULL

R6635H11 patch deployment for S6805. Disconnect netconf before deploying the patch, after the patch is deployed, restoring the netconf configuration connection fails

1. Viewing the switch logs shows the xmlcfgd process abnormally alarmed 

 %Aug 7 18:41:03:723 2023 H3C SCMD/4/PROCESS_ABNORMAL: The process xmlcfgd exited abnormally. ServiceName=XMLCFGD, ExitCode=1, KillSignal=NA, StartTime=2023-08-07 18:41:02, StopTime=2023-08-07 18:41:03. StartTime=2023-08-07 18:41:02, StopTime=2023-08-07 18:41:03. 

 %Aug 7 18:41:04:833 2023 H3C SCMD/4/PROCESS_ABNORMAL: The process xmlcfgd exited abnormally. ServiceName=XMLCFGD, ExitCode=1, KillSignal=NA, StartTime=2023-08-07 18:41:02, StopTime=2023-08-07 18:41:03. StartTime=2023-08-07 18:41:03, StopTime=2023-08-07 18:41:04.

 %Aug 7 18:41:05:929 2023 H3C SCMD/4/PROCESS_ABNORMAL: The process xmlcfgd exited abnormally. ServiceName=XMLCFGD, ExitCode=1, KillSignal=NA, StartTime=2023-08-07 18:41:03, StopTime=2023-08-07 18:41:04. ServiceName=XMLCFGD, ExitCode=1, KillSignal=NA, StartTime=2023-08-07 18:41:04, StopTime=2023-08-07 18:41:05.

2. check xmlcfgd process, did not start normally, the scene of the previous patch through the controller on January 10, fork xmlcfgd sub-process deadlock did not exit (does not affect the patch function), resulting in this time xmlcfgd startup lipc port is occupied by the residual process startup failure:

Looking at the log there is also a record of the patch installation, the time can be right

%@19848%Jan 10 11:08:04:512 2023 H3C FTP/5/OPER: User sdnadmin@17.251.12.68 uploaded flash:/d65033ec-f0d5-42d5-8dee-e18a8c0fe87e.bin.

 %@19861%Jan 10 11:13:03:261 2023 H3C XMLSOAP/6/ACTION: User (sdnadmin, 17.251.12.68, session ID 9), message ID=1, operation=action Package/ InstallImage, result=Succeeded. attributes: Action=1, PatchFile="slot1#flash:/d65033ec-f0d5-42d5-8dee-e18a8c0fe87e.bin", OverwriteLocalFile=true.

The current version of the device when deploying patches through the controller, a small probability of triggering fork xmlcfgd sub-process deadlock did not exit, when the subsequent xmlcfgd process restart can not start normally, this problem is planned to be solved through the R6635H17 patch