nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Joined Server Site refuses to launch post Federation

Yogesh_Chavan

We have a server site with web adaptor installed on machine A and there is another machine B with server installed and joined to machine A.

We are observing that after federating machine A with portal (on machine C), machine B just goes into please wait mode. If we un-federate machine A this issue does not happen and machine B works fine. What is triggering this? We tried reinstalling, issue persist.

Thank you!!

Najděte více příspěvků označených jako

Accepted answers

All comments

tigerwoulds

Can machine c (portal) communicate with both arcgis server (a and b) machines on port 6443?

Yogesh_Chavan

Hello @tigerwoulds,

Thank you for responding. Below communication is successful when checked through Machine C.

telnet <ArcGIS Server Machine A IP> 6443

telnet <ArcGIS Server Machine B IP> 6443

and

ping <ArcGIS Server Machine A IP>

ping <ArcGIS Server Machine B IP>

Note: Issue only triggers post federating on Joined Site.

MingLee

Server A - ArcGIS Server with Web Adaptor.

Server B - ArcGIS Server

Server C - Portal for ArcGIS

Some clarification questions:

1. When you're joining Server B to Server A (prior to federating) - is the config-store for Server A in a shared location, accessible to both Server A and B?

2. Is there a Web Adaptor on Server B?

3. When federating with Portal, what are you using as the URLs for both the ArcGIS Server and the ArcGIS Administration URL?

4. Can Server B resolve and 'see' Server C (via hostname or FQDN)?

Yogesh_Chavan

Thank you @MingLee for pitching in.

Kindly find the details below:

1. When you're joining Server B to Server A (prior to federating) - is the config-store for Server A in a shared location, accessible to both Server A and B?

Yes, config-store is on a network share and is accessible without any issues.

2. Is there a Web Adaptor on Server B?

No, web adaptor is only on Server A.

3. When federating with Portal, what are you using as the URLs for both the ArcGIS Server and the ArcGIS Administration URL?

When federating Server A with Portal, we are using Web Adaptor URL(https://germany.try.net/arcgis) and Admin URL(https://germany.try.net:6443/arcgis)

4. Can Server B resolve and 'see' Server C (via hostname or FQDN)?

You mean can server B and portal communicate? Yes, both communicate without any issues.

Yogesh_Chavan

Hello @tigerwoulds, @MingLee .

Anything you can suggest further?

Thank you!!

MingLee

Can I suggest the following, let's reverse the server configuration:

1. Unfederate Server A.

2. Install Web Adaptor onto Server B. Call the web context as 'server' instead of the default 'arcgis'.

3. Federate Server B to the Portal. Test and Confirm that all is working as expected.

4. Delete the server site from Server A. Uninstall the Web Adaptor on Server A.

5. Reinstall the Web Adaptor and call it 'server' instead of 'arcgis'.

6. On Server A, 'join server site' to Server B.

7. Federate to Portal using the address of Server B.

Question: have you considered using a load balancer in front of Server A and Server B?

Yogesh_Chavan

Thank you @MingLee for the suggestion. Surely I can try this.

Just a quick question, in step 4 you have mentioned to delete server site, do you mean completely uninstall Server A, which we can definitely try and if that's the case before step 6 we need to install and setup site on machine A. Is this correct that I have understood?

For your question: have you considered using a load balancer in front of Server A and Server B? The answer is Yes we do have an internal NLB addition planned if everything works out well.

Yogesh_Chavan

Hello @MingLee

Here is what we did:

1) Removed Machine B from A

2) Created a new server site on Machine B

3) Installed a web adaptor named "arcgisserver"

4) Federated Machine B and Portal

5) Uninstalled Web Adaptor and ArcGIS Server on Machine A

6) Installed ArcGIS Server on Machine A and joined to Machine B

7) Installed Web Adaptor on machine A with instance "arcgisserver"

Findings:

It does not allow to Federate an already federated server and joined site (which is expected)
The issue persists and now Server manager on Machine A does not opens, which is caused as we reversed the setup, and is behaving exactly same as it was earlier
Just an addition to this is rest and admin ends always works fine its only the Manager end failing to load

I appreciate your efforts and help, is there anything else that I can check? Also just wanted to confirm its not an expected behavior or something as designed?

tigerwoulds

Are these servers in the same subnet? Ie. all in your internal network or are one or more servers the DMZ. Wondering if there is firewall in place that would be blocking the following communication:

Portal > Server A on 6443

Portal > Server B on 6443

Server A > Portal on 7443

Server B > Portal on 7443

Does dual server work if you omit web adaptors entirely? That may help your narrow down the issue. Otherwise, I would recommend an esri support ticket for this.

MingLee

Hello, @Yogesh_Chavan for step 4, delete the ArcGIS Server site on Server A. This is through the ArcGIS Server Administrator Directory where there is an option to 'deleteSite'; this removes the config-store information but doesn't go as far as completely reinstalling the software. All I am suggesting is to switch Server A with B; so that it is B that has Server A join it. We're trying to isolate the cause of the joining site issue.

Yogesh_Chavan

Hello @MingLee,

Yes, we have reversed the entire setup and the issue still persists.

Also, if we federate this server with a different portal issue is re-triggered. So, this issue is not restricted to one portal/server env.

Can this be a BUG with 11.1? By any chance you have tested this to see if its not an expected behavior?

BillFox

Take a ride down the documentation trail of high available sites (ArcGIS Server and Portal and Web Adaptor)

There are several critical steps you will read about in there as well as the order of setting things up successfully.

Yogesh_Chavan

Hello @BillFox,

Thank you for the suggestion. I looked into a few documentations and does not find anything I can utilize to troubleshoot further. Seems like we are hitting a roadblock.

@MingLee is there anything else you can think?

Thank you,

Yogesh.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.