Mid server agent getRecords failed The host did not accept the connection within timeout of 10000 ms
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 07:19 AM
Current situation with linux installation of mid server
after install mid server agent successfully,agent service is up and running ,then i wanna validate the MID Server stauts refer to official documents [Validate the MID Server] , but servicenow instance didn't get any mid server list, when i check the mid server agent logs found some Errors in logfile agent0.log.0
2023-10-30T21:55:10.758+0800 INFO (WrapperStartStopAppMain) [LogUtil:38] JdkSASL
2023-10-30T21:55:10.758+0800 INFO (WrapperStartStopAppMain) [LogUtil:38] SunPKCS11
2023-10-30T21:55:10.758+0800 INFO (WrapperStartStopAppMain) [LogUtil:38] BCFIPS
2023-10-30T21:55:10.759+0800 INFO (WrapperStartStopAppMain) [LogUtil:38] BCJSSE
2023-10-30T21:55:10.817+0800 INFO (WrapperStartStopAppMain) [KeyPairsProviderFactory:57] Loaded credentials provider: com.service_now.mid.keypairs.provider.standard.StandardKeyPairsProvider
2023-10-30T21:55:10.868+0800 INFO (WrapperStartStopAppMain) [Instance:1384] Setting basic authentication with user midserveraccount
2023-10-30T21:55:11.435+0800 INFO (WrapperStartStopAppMain) [Bootstrapper:41] Welcome to the ServiceNow MID Server
2023-10-30T21:55:11.717+0800 INFO (WrapperStartStopAppMain) [ExtensionContainer:98] ExtensionContainer ThreadPool started with corePoolSize: 25, maximumPoolSize: 25, maximumQueueSize: 500
2023-10-30T21:55:12.751+0800 INFO (WrapperStartStopAppMain) [SenderFilesInfoService:46] Service started.
2023-10-30T21:55:12.752+0800 INFO (WrapperStartStopAppMain) [DrainingStateTransitionHandler:125] Drain timeout set (900 seconds).
2023-10-30T21:55:12.760+0800 INFO (MIDServer) [MIDCredentialsConfigProvider:36] MIDCredentialsConfigProvider initialized with com.service_now.mid.creds.provider.standard.StandardCredentialsProvider
2023-10-30T21:55:12.766+0800 INFO (MIDServer) [PriorityThreadPoolProvider:274] Drain timeout set (900 seconds).
2023-10-30T21:55:13.326+0800 INFO (MIDServer) [BootConfigProvider:36] Attempting to load boot config file at location: /home/midserver/agent/boot-config.yaml
2023-10-30T21:55:13.326+0800 INFO (MIDServer) [BootConfigProvider:44] Boot configuration file not found at default location: /home/midserver/agent/boot-config.yaml, providing empty configuration
2023-10-30T21:55:13.329+0800 INFO (MIDServer) [Main:266] Initializing MID Server
2023-10-30T21:55:13.330+0800 INFO (MIDServer) [Main:281] Running under Java version: 11.0.16.1-sncmid1, java PID: 18045, args: start
2023-10-30T21:55:13.484+0800 INFO (MIDServer) [Main:289] JVM default socket factory: class com.service_now.mid.security.policy.PolicyBasedSSLSocketFactory
2023-10-30T21:55:13.658+0800 INFO (MIDServer) [AbstractPolicyService:60] No security policy match found for endpoint [itsmpoc.test.cn]. No INTERNET security policy was found either. Falling back to the default security policy
2023-10-30T21:55:13.949+0800 INFO (MIDServer) [OCSPCheck:166] OCSPCheck adding BouncyCastle provider at -1
2023-10-30T21:55:13.950+0800 INFO (MIDServer) [OCSPCheck:174] OCSPCheckedCertificateCache build with max capacity 32
2023-10-30T21:55:13.950+0800 INFO (MIDServer) [OCSPCheck:188] OCSPRevokedCertificateCache build with max capacity 16
2023-10-30T21:55:13.951+0800 INFO (MIDServer) [OCSPCheck:202] OCSPTimeoutErrorCache build with max capacity 16
2023-10-30T21:55:19.008+0800 WARN (glide.lock.cleaner) [LockManager:86] Freed stuck JVM lock: OCSPCheck CN: *.test.cn
2023-10-30T21:55:24.019+0800 WARN (MIDServer) [OCSPCheck:544] OCSPCheck connection timeout: http://ocsp.dcocsp.cn
2023-10-30T21:55:24.023+0800 WARN (MIDServer) [HTTPClient:830] org.apache.commons.httpclient.HttpException: The host did not accept the connection within timeout of 10000 ms *.test.cn
2023-10-30T21:55:24.029+0800 ERROR (MIDServer) [RemoteGlideRecord:918] getRecords failed (org.apache.commons.httpclient.HttpException: The host did not accept the connection within timeout of 10000 ms *.test.cn)
2023-10-30T21:55:24.035+0800 WARN (MIDServer) [RetryExecutor:104] MIDRemoteGlideRecord.query failed, retrying in 10 seconds
2023-10-30T21:55:40.012+0800 WARN (glide.lock.cleaner) [LockManager:86] Freed stuck JVM lock: OCSPCheck CN: *.test.cn
2023-10-30T21:55:44.064+0800 WARN (MIDServer) [OCSPCheck:544] OCSPCheck connection timeout: http://ocsp.dcocsp.cn
2023-10-30T21:55:44.065+0800 WARN (MIDServer) [HTTPClient:830] org.apache.commons.httpclient.HttpException: The host did not accept the connection within timeout of 10000 ms *.test.cn
2023-10-30T21:55:44.065+0800 ERROR (MIDServer) [RemoteGlideRecord:918] getRecords failed (org.apache.commons.httpclient.HttpException: The host did not accept the connection within timeout of 10000 ms *.test.cn)
2023-10-30T21:55:44.066+0800 WARN (MIDServer) [RetryExecutor:104] MIDRemoteGlideRecord.query failed, retrying in 15 seconds
Any ideas from anyone?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2023 10:30 AM
@EasonYan It is due to your mid server unable to validate the instance certificate using OCSP. Please go through the below.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1216223