Index Service Configuration Failed

11137
16
Jump to solution
07-23-2019 10:33 AM
CarbonCounty_Utah
New Contributor III

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-enterpri....

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!

0 Kudos
2 Solutions

Accepted Solutions
JonathanQuinn
Esri Notable Contributor

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.

View solution in original post

0 Kudos
JonathanQuinn
Esri Notable Contributor

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.

View solution in original post

16 Replies
PhamTheVinh
New Contributor II

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

0 Kudos
JonathanQuinn
Esri Notable Contributor

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.

0 Kudos
PhamTheVinh
New Contributor II

Our portal server is 

 Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
 Sockets: 1
 Cores: 6
0 Kudos
JonathanQuinn
Esri Notable Contributor

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.

0 Kudos
RobertMiller4
New Contributor

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!

0 Kudos
JonathanQuinn
Esri Notable Contributor

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.

AndrewClark2
New Contributor III

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>

0 Kudos
JonathanQuinn
Esri Notable Contributor

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?

0 Kudos
AndrewClark2
New Contributor III

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

0 Kudos