Connectivity issue with Mid Server

[antonio1989]

Hi,

i have configured a Mid Server on a Linux Server but after the start of service, i see these errors, can you help me to identify the cause?

12/17/21 12:29:01 (273) StartupSequencer SEVERE *** ERROR *** SOAP Request: <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://www.service-now.com/GetMIDInfo" xmlns:m="http://www.service-now.com" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
12/17/21 12:29:01 (273) StartupSequencer SEVERE *** ERROR *** SOAP Response: Status code=0, Response body=null
12/17/21 12:29:01 (273) StartupSequencer SEVERE *** ERROR *** Problem invoking InstanceInfo on  Please check that the InstanceInfo page exists in the sys_public table and active="true".
12/17/21 12:29:01 (273) StartupSequencer SEVERE *** ERROR *** Request not sent to uri=  : java.net.SocketTimeoutException: connect timed out
(Network Configuration issue) Please check that the MID server can ping the instance: 
You may also need to configure the network that the MID server uses to allow traffic over TCP port 443.
12/17/21 12:29:01 (273) StartupSequencer SEVERE *** ERROR *** test failure
java.lang.IllegalStateException: Unable to connect to instance.
at com.service_now.mid.services.StartupSequencer.runTests(StartupSequencer.java:638)
at com.service_now.mid.services.StartupSequencer.startupSequencerRunnable(StartupSequencer.java:694)
at java.base/java.lang.Thread.run(Thread.java:834)

12/17/21 12:30:11 (401) StartupSequencer WARNING *** WARNING *** Request not sent to uri= h : java.net.SocketTimeoutException: connect timed out
12/17/21 12:30:11 (401) StartupSequencer SEVERE *** ERROR *** SOAP Request: <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://www.service-now.com/GetMIDInfo" xmlns:m="http://www.service-now.com" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
12/17/21 12:30:11 (401) StartupSequencer SEVERE *** ERROR *** SOAP Response: Status code=0, Response body=null
12/17/21 12:30:11 (402) StartupSequencer SEVERE *** ERROR *** Problem invoking InstanceInfo on Please check that the InstanceInfo page exists in the sys_public table and active="true".
12/17/21 12:30:11 (402) StartupSequencer SEVERE *** ERROR *** Request not sent to uri=  : java.net.SocketTimeoutException: connect timed out
(Network Configuration issue) Please check that the MID server can ping the instance: 
You may also need to configure the network that the MID server uses to allow traffic over TCP port 443.
12/17/21 12:30:11 (402) StartupSequencer SEVERE *** ERROR *** test failure
java.lang.IllegalStateException: Unable to connect to instance.
at com.service_now.mid.services.StartupSequencer.runTests(StartupSequencer.java:638)
at com.service_now.mid.services.StartupSequencer.startupSequencerRunnable(StartupSequencer.java:694)
at java.base/java.lang.Thread.run(Thread.java:834)

How can i start the Mid Server service on 0.0.0.0 instead of 127.0.0.1?

Thank you

[antonio1989]

how can i force the Mid Server service to start on 0.0.0.0?

[-O-]

Can you post what is the output of "ping dev89988.service-now.com"?

[antonio1989]

ping dev89988.service-now.com
PING dev89988.service-now.com (149.96.5.118) 56(84) bytes of data.
^C
--- dev89988.service-now.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6139ms

[-O-]

As you can see, IPv4 is not correctly set up, it does not work to ping the SN instance, as expected based on the settings posted above.

You need to reconfigure the network on the host to be able to communicate with a gateway router and the Internet.

[-O-]

From Wikipedia:

In the Internet Protocol Version 4, the address 0.0.0.0 is a non-routable meta-address used to designate an invalid, unknown or non-applicable target.