topic Re: Index Service Configuration Failed in ArcGIS Enterprise Questions

Index Service Configuration Failed

CarbonCounty_Utah — Tue, 23 Jul 2019 17:33:51 GMT

I'm trying to do a fresh install of Portal for ArcGIS on Windows Server 2016. The install goes fine but I keep getting an error when trying to create the portal site and initial admin account. I get an error saying "There was an error creating your initial administrator account. Index Service configuration failed. For more information, please view the log messages located in the content directory specified during setup."

I have already tried uninstalling and reinstalling Portal on the server. I also checked the files from this thread https://community.esri.com/thread/223779-i-cannot-create-a-portal-admin-account-with-arcgis-enterprise.

I attached a screenshot of the error I'm getting as well as a copy of the log from Portal.

If anyone has any ideas what the problem might be I would appreciate the help!

Re: Index Service Configuration Failed

PhamTheVinh — Thu, 12 Sep 2019 02:55:51 GMT

I have save error. Please help

Index Service configuration failed

Attempt to configure data store failed. Attempt to configure data store failed.. Extended error message: Failed to configure spatiotemporal big data store.. Extended error message: Failed to start spatiotemporal big data store machine.. Extended error message: Failed to start spatiotemporal big data store machine

Re: Index Service Configuration Failed

JonathanQuinn — Thu, 12 Sep 2019 16:58:00 GMT

You'll need at least two cores on the Portal machine to create the site. If you only have core, that's the reason it's failing.

Re: Index Service Configuration Failed

PhamTheVinh — Fri, 13 Sep 2019 06:41:41 GMT

Our portal server is

Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz

Sockets: 1
Cores: 6

Re: Index Service Configuration Failed

JonathanQuinn — Fri, 13 Sep 2019 18:58:44 GMT

The quickest troubleshooting step is to make sure that ports 7120 and 7220 are not in use. If they aren't, I suggest you reach out to Technical Support so they can take a look with you.

Re: Index Service Configuration Failed

Chenna_KishoreMallemala — Mon, 16 Sep 2019 12:52:11 GMT

If you have antivirus installed on the server, disable it and try. it worked for me while installing 10.7.1

Re: Index Service Configuration Failed

RobertMiller4 — Tue, 21 Jan 2020 20:43:03 GMT

Hi Jonathan,

I am hoping you can elaborate a bit on this. I had Portal working just fine on a single core machine at version 10.6.1. I attempted to upgrade to 10.7 using the ArcGIS Enterprise Builder and ran into the "Index Service Configuration Failed" error. Is the two core requirement something that changed between these two versions? I am having a hard time finding information about how many cores are needed to run Enterprise. I see that for the Portal it is recommended to have 4 cores for 100 concurrent users, but my requirements are not even close to 100 users (more like 15 or so). Any advice on the topic would be appreciated so I can justify resource upgrades. Thanks!

Re: Index Service Configuration Failed

JonathanQuinn — Tue, 21 Jan 2020 22:23:24 GMT

Yes, it's changed due to a limitation in an internal component which required more than 1 core. At 10.7 and 10.7.1, you'll need two cores as a hard requirement. At 10.8, we've resolved that issue so you can create/upgrade portal on a machine with one core, but in our documentation, we list the following requirements:

Processor: 2 cores minimum for development and testing, 4 cores minimum highly recommended for production systems

You'll see this in the documentation when 10.8 is released.

Re: Index Service Configuration Failed

AndrewClark2 — Fri, 21 Feb 2020 01:30:50 GMT

Hi!

I am having the exact same issue. I have installed portal 10.7.1 on a Centos 7 VM and am trying to create a portal. When I try to create the Portal instance, it crashes with the following error messages. I am running with 16 cores and ports 7120 and 7220 are not in use.

Here is the full description of my vm hardware:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 16
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 60
Model name: Intel Core Processor (Haswell, no TSX, IBRS)
Stepping: 1
CPU MHz: 2593.990
BogoMIPS: 5187.98
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
L3 cache: 16384K
NUMA node0 CPU(s): 0-15

Here is the error messages

<Msg time="2020-02-21T00:45:21,768" type="INFO" code="209020" source="Portal Admin" process="3667" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting to initialize indexer module.</Msg>
<Msg time="2020-02-21T00:45:21,796" type="INFO" code="218022" source="Portal Admin" process="3667" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Elastic node configuration started.</Msg>
<Msg time="2020-02-21T00:46:25,957" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:46:25,959" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:47:41,535" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:47:41,536" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:48:57,105" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:48:57,106" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:50:12,676" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:50:12,676" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:51:28,247" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:51:28,248" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:52:43,815" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:52:43,816" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:53:59,391" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:53:59,393" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:55:14,957" type="WARNING" code="218014" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Starting Index Service.</Msg>
<Msg time="2020-02-21T00:55:14,958" type="WARNING" code="218015" source="Portal" process="3379" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Started Index Service.</Msg>
<Msg time="2020-02-21T00:55:29,362" type="SEVERE" code="110506" source="Data Store" process="3667" thread="70" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Attempt to configure data store failed. Attempt to configure data$
<Msg time="2020-02-21T00:55:29,363" type="SEVERE" code="218028" source="Portal Admin" process="3667" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Index Service configuration failed.</Msg>
<Msg time="2020-02-21T00:55:29,363" type="SEVERE" code="218028" source="Portal Admin" process="3667" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Index Service configuration failed.</Msg>
$creation. Index Service configuration failed.</Msg>
<Msg time="2020-02-21T00:55:44,639" type="INFO" code="209074" source="Portal Admin" process="3667" thread="1" methodName="" machine="XXXXXXXXXXXXXXX" user="" elapsed="" requestID="">Connection file deleted from disk.</Msg>

Re: Index Service Configuration Failed

JonathanQuinn — Sat, 22 Feb 2020 00:20:02 GMT

Under <install directory>/framework/runtime/ds/usr/logs, you should be able to see a log file that describes why the index service couldn't start. Can you post a snippet of those logs, obscuring any identifying information?

Re: Index Service Configuration Failed

AndrewClark2 — Mon, 24 Feb 2020 03:28:03 GMT

Hi,

Here is the log. Let me knos if you need anything else!

Cheers,

Andrew

[2020-02-20T22:39:38,670][ERROR][o.e.b.Bootstrap          ] [SERVERNAME] Exception
org.elasticsearch.transport.BindTransportException: Failed to resolve host [_site_, SERVERNAME, _local_]
   at org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:772) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.netty4.Netty4Transport.doStart(Netty4Transport.java:134) ~[?:?]
   at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.TransportService.doStart(TransportService.java:217) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.node.Node.start(Node.java:667) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:265) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:335) [elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) [elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:127) [elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) [elasticsearch-cli-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) [elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:86) [elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
Caused by: java.net.UnknownHostException: SERVERNAME: Name or service not known
   at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
   at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAddressesFromNameService(Unknown Source) ~[?:?]
   at java.net.InetAddress$NameServiceAddresses.get(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAllByName0(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
   at org.elasticsearch.common.network.NetworkService.resolveInternal(NetworkService.java:237) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.network.NetworkService.resolveInetAddresses(NetworkService.java:187) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.network.NetworkService.resolveBindHostAddresses(NetworkService.java:106) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:770) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   ... 14 more
[2020-02-20T22:39:38,678][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [SERVERNAME] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: BindTransportException[Failed to resolve host [_site_, SERVERNAME, _local_]]; nested: UnknownHostException[SERVERNAME: Name or service not known];
   at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:140) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:127) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:124) ~[elasticsearch-cli-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.cli.Command.main(Command.java:90) ~[elasticsearch-cli-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:93) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:86) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
Caused by: org.elasticsearch.transport.BindTransportException: Failed to resolve host [_site_, SERVERNAME, _local_]
   at org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:772) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.netty4.Netty4Transport.doStart(Netty4Transport.java:134) ~[?:?]
   at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.TransportService.doStart(TransportService.java:217) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.node.Node.start(Node.java:667) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:265) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:335) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   ... 6 more
Caused by: java.net.UnknownHostException: SERVERNAME: Name or service not known
   at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
   at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAddressesFromNameService(Unknown Source) ~[?:?]
   at java.net.InetAddress$NameServiceAddresses.get(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAllByName0(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
   at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
   at org.elasticsearch.common.network.NetworkService.resolveInternal(NetworkService.java:237) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.network.NetworkService.resolveInetAddresses(NetworkService.java:187) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.network.NetworkService.resolveBindHostAddresses(NetworkService.java:106) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:770) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.netty4.Netty4Transport.doStart(Netty4Transport.java:134) ~[?:?]
   at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.transport.TransportService.doStart(TransportService.java:217) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:66) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.node.Node.start(Node.java:667) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:265) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:335) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:136) ~[elasticsearch-6.4.2.jar:6.4.2-SNAPSHOT]
   ... 6 more
[2020-02-20T22:39:39,550][INFO ][o.e.n.Node               ] [SERVERNAME] stopping ...
[2020-02-20T22:39:39,553][INFO ][o.e.n.Node               ] [SERVERNAME] stopped
[2020-02-20T22:39:39,553][INFO ][o.e.n.Node               ] [SERVERNAME] closing ...
[2020-02-20T22:39:39,563][INFO ][o.e.n.Node               ] [SERVERNAME] closed

Re: Index Service Configuration Failed

JonathanQuinn — Mon, 24 Feb 2020 18:29:43 GMT

Looks like the index service is having trouble resolving the hostname of the machine:

Failed to resolve host [_site_, SERVERNAME, _local_]
...
Caused by: java.net.UnknownHostException: SERVERNAME: Name or service not known

Any issues running ifconfig/pings/hostname on the machine, and not returning the expected information?

Re: Index Service Configuration Failed

AndrewClark2 — Thu, 27 Feb 2020 01:59:10 GMT

Hi Jonathan,

I have fixed another problem, but ran into this error message.

2020-02-26 18:20:03.002 UTC [10957] FATAL: no pg_hba.conf entry for host "[local]", user "centos", database "centos", SSL off

Seems to be a common issue with PostGres, and the recommendation seems to be as follows:

Edit pg_hba.conf under Master data directory and make the following changes:
local all <user_name> trust
host all <user_name> 0.0.0.0/0 trust
host all <user_name> ::/0 trust

Unfortunately, when I try that the pg_hba.conf file resets as soon as the "Create Portal" command, so the changes are undone.

Any help you can give me would be greatly appreciated.

Thanks,

Andrew

Re: Index Service Configuration Failed

AndrewClark2 — Thu, 27 Feb 2020 17:02:34 GMT

I got it working again. There must have been some residual memory of the previous settings, as I uninstalled portal and reinstalled it and everything created perfectly.

Thanks for your help!

Andrew

Re: Index Service Configuration Failed

JonathanQuinn — Thu, 27 Feb 2020 18:32:50 GMT

Glad you got it working! Couple things I need to point out though:

1) Modifying internal files is not supported and risky. The pg_hba.conf file was getting updated because Portal is expecting and writes certain contents to it

2) The 2020-02-26 18:20:03.002 UTC [10957] FATAL: no pg_hba.conf entry for host "[local]", user "centos", database "centos", SSL off errors are expected. Portal is checking the status of the database, but prior to 10.8, doesn't check with a username nor DB, so it assumes the install user. These can be ignored. This is fixed at 10.8.

3) The trust setting allows you to connect to the database without a password, which is a security risk. Allowing anyone to connect from anywhere (0.0.0.0 and ::/0) is certainly not something you want to do.

Re: Index Service Configuration Failed

GreggRoemhildt2 — Wed, 09 Nov 2022 16:37:57 GMT

Hi @JonathanQuinn I saw your post and am running into a similar issue where the indexer service won't start properly. I've enabled debug logs and am seeing this message:

java.net.ConnectException: Connection refused at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:849) at org.elasticsearch.client.RestClient.performRequest(RestClient.java:259) at org.elasticsearch.client.RestClient.performRequest(RestClient.java:246) at com.esri.arcgis.portal.ElasticSearchManager.a(ElasticSearchManager.java:487) at com.esri.arcgis.portal.ElasticSearchManager.createIndexWithMappingsAndSettings(ElasticSearchManager.java:621) at com.esri.arcgis.portal.Indexer.c(Indexer.java:1535) at com.esri.arcgis.portal.Indexer.run(Indexer.java:426) at com.esri.arcgis.portal.Indexer.main(Indexer.java:207) Caused by: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:174) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:148) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351) at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) at java.base/java.lang.Thread.run(Unknown Source)

The server I'm running is a supported Ubuntu Ubuntu 20.04.5 LTS. I'm installing a single machine deployment on an AWS instance using ArcGIS Enterprise 11 installers.

Any tips on this one?

Re: Index Service Configuration Failed

JonathanQuinn — Thu, 10 Nov 2022 16:05:49 GMT

Connection refused would indicate that the the index service is not running. Have you verified whether you see a java.exe process running on the machine? If not, the logs under <install directory>\framework\runtime\ds\usr\logs may help identify why it can't start. You can post some logs here, but these types of problems are a bit challenging to troubleshoot so it may be best to contact Support.