Hello Experts, 
        
        
        In one of our submit node while submitting the batch we see
          the following error: snippet captured from SchedLog file. Not
          using any condor python binding simply calling condor_submit
          for submitting the jobs. Machine is not overloaded. This is
          happening very often. 
        
        
        Obfuscated is the sched IP.
        
        
        04/14/21 07:09:23 (pid:830409) SECMAN: Error sending
          response classad to <xx.xx.xxx.xx:17323>!
          NewSession = "YES"
          Subsystem = "TOOL"
          AuthMethods = "FS,KERBEROS,GSI"
          CryptoMethods = "3DES,BLOWFISH"
          Authentication = "OPTIONAL"
          Integrity = "OPTIONAL"
          Command = 516
          Encryption = "OPTIONAL"
          ServerPid = 2800527
          SessionDuration = "60"
          OutgoingNegotiation = "PREFERRED"
          Enact = "NO"
          SessionLease = 3600
          RemoteVersion = "$CondorVersion: 8.5.8 Dec 13 2016 BuildID:
          390781 $"
        
        
        
        Nothing fancy in configuration. 
        
        
        # condor_config_val -dump | grep SEC
          DCSTATISTICS_WINDOW_SECONDS =
          ENCRYPT_SECRETS = true
          IGNORE_ATTEMPTS_TO_SET_SECURE_JOB_ATTRS = true
          SEC_CLAIMTOBE_INCLUDE_DOMAIN = false
          SEC_CLAIMTOBE_USER =
          SEC_DEBUG_PRINT_KEYS = false
          SEC_DEFAULT_AUTHENTICATION_TIMEOUT = 20
          SEC_ENABLE_MATCH_PASSWORD_AUTHENTICATION = true
          SEC_INVALIDATE_SESSIONS_VIA_TCP = true
          SEC_PASSWORD_DOMAIN =
          SEC_PASSWORD_FILE =
          SEC_SESSION_DURATION_SLOP = 20
          SEC_TCP_SESSION_TIMEOUT = 20
          SECURE_JOB_ATTRS =
          STATISTICS_WINDOW_SECONDS = 1200
          SYSTEM_SECURE_JOB_ATTRS = x509userProxySubject
          x509UserProxyEmail x509UserProxyVOName x509UserProxyFirstFQAN
          x509UserProxyFQAN
        
        
        
        It seems to be a local sched issue, nothing interesting in
          negotiator logs. 
        
        
        Any thoughts? what could be causing it. 
        
        
        
        
          
            
              
                Thanks & Regards,
                Vikrant Aggarwal