MID Server connected but not shown in a list of MID servers

dgomel
Mega Contributor

Dear all,

I have a new MID server installation. The MID server installed and connected successfully. No error in log what so ever.

I see hartbeat of the MID server comming as well.

But it's never shown in MID servers list. I checked KBs related to the issue, but can't find a problem.

What troubleshooting steps should I take?

Dmitry

1 ACCEPTED SOLUTION

dgomel
Mega Contributor

I got an answer from the support. This is a Jakarta specific defect.

This issue has been fixed in our Kingston and Jakarta Patch 10 release, so please upgrade the instance and then this issue will not occur.

If you cannot upgrade to Kingston then the below workarounds could be used:

  1. Use a pre-Jakarta Patch 9 installer instead, which will work, and then it will immediately upgrade itself to match the instance version.
    Links to Jakarta Patch 8c Installer ZIPs: Windows: 32 bit64 bit, Linux: 32 bit64 bit

  2. Install a new MID Server using the Jakarta Patch 9 installer from your instance MID Server Downloads page, by following the manual installation steps as outlined below: 

View solution in original post

18 REPLIES 18

tim_broberg
ServiceNow Employee
ServiceNow Employee

"Discovery - MID Servers" shows the ecc_agent table.

You can also enter ecc_agent.list in the filter box.

Finally, you can write a background script

var gr = new GlideRecord('ecc_agent');
gr.query();
while (gr.next())
 gs.print(gr.name + ' ' + gr.status);

tim_broberg
ServiceNow Employee
ServiceNow Employee

If you look in your config.xml, you should see a record like this:

<parameter name="mid_sys_id" value="41ebc3a5dca5c7403c3ff0e5bf9619b4"/>

 

If you filter the mid list for sys_id = the value from this record, can you find it?

    - Tim.

Hey Tim,

Thanks for your answer.

My Config XML has no mid_sys_id parameter, but it has:

<parameter name="keypairs.mid_id" value="601112006a1023005916065b6bdb6300" />

Is it similar parameter?

 

tim_broberg
ServiceNow Employee
ServiceNow Employee

Different thing. That's the keypair used to encrypt credentials sent to the mid.

You say you're getting heartbeats in the agent log? That means there are ecc_queue records for this mid. Right? You might look for those.

It's hard to think how the agent log could be clean but we failed to create an agent record.

It may be time to just delete and reinstall rather tan spend a lot of time debugging it.

dgomel
Mega Contributor

I also verified that there is no proxy defined. I did this by installing Firefox, which implements separate IP stack, so when setting set to No proxy, it's not using system one.