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

[Sohail Khilji]

Hi,

There is an ACL on the sys_public table that allows editing the Instance Info page only for a user with a role "maint". If your Instance Info page is not active I would suggest setting the flag Admin overrides to true for a moment, change the Active flag on Instance Info and revert changes to ACL to bring it back to the OOTB state. To do this you have to elevate your roles to security admin.


Go to sys_public list, right-click on the first column's header, go to configuration>security rules:

 Then find the sys_public.none rule:

Then set the Admin overrides flag to true and save the record

 Now go to sys_public list and change the InstanceInfo active flag to true from the list or on the form.

After that, revert your changes to ACL.

-OR-

Refer this : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0825441 

I hope the answer helps, Kindly Mark ✅ Correct or ???? Helpful if applicable., So that others get benefited in future for similar issues...

Thanks,

MF Sohail Khilji.

LinkedIn >   https://www.linkedin.com/in/mf-sohail-khilji/

[-O-]

What is the output of "ip a" (or "ifconfig")?

[antonio1989]

ens4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460
inet 10.58.231.24 netmask 255.255.255.255 broadcast 10.58.231.24
ether 42:01:0a:3a:e7:18 txqueuelen 10000 (Ethernet)
RX packets 33291529 bytes 8079058893 (7.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28187773 bytes 34083777390 (31.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 28712307 bytes 9752913136 (9.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28712307 bytes 9752913136 (9.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[-O-]

It seems to me you have connectivity issues: netmask 255.255.255.255 doesn't seem right.

Under normal circumstances the listener is correctly started for all rout-able interfaces, no "forcing" is necessary.