# Starting ES-7.8.0 hung up CLI **URL:** \ **Category:** Elasticsearch\ **Created:** [July 19, 2020, 12:21am UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768 "2020-07-19T00:21:24Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![dzyubanv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzyubanv/32/24110_2.png) [@dzyubanv](https://discuss.elastic.co/u/dzyubanv)\ **Post date:** [July 19, 2020, 12:21am UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/1 "2020-07-19T00:21:24Z")
Hello, I setup ES-7.8.0 cluster on 2 hosts (Linux), 2 master and 2 data nodes on each host. I'm able to start all 4 nodes, the cluster health=GREEN and I can see all nodes joined the cluster. Environment: ES-7.8.0 (elasticsearch-7.8.0-linux-x86\_64.tar.gz), RHEL 5.11, JDK 1.8.0\_65 **The problem is when I'm staring a node on CLI then I can see the following two identical lines on the console, where I started ES and these lines hung up CLI** future versions of Elasticsearch will require java 11; your java version from [u/hadoop/java/JDK 1.8.0\_65/jre] does not meet this requirement future versions of Elasticsearch will require java 11; your java version from [u/hadoop/java/JDK 1.8.0\_65/jre] does not meet this requirement **To start another node on these console I need to release it manually with Ctl-C, which is not convenient and does Not allow to automate the multi-node startup process on the same console without manual intervention**. I'm starting nodes as follows ES\_JAVA\_OPTS="-Dmapper.allow\_dots\_in\_name=true -Xms${ES\_HEAP\_SIZE} -Xmx${ES\_HEAP\_SIZE}" bin/elasticsearch -d -p /path\_to\_pid/es-pid The ES.log on the second console shows the node is started even the CLI on the first console is not manually released as follows [WARN][o.e.b.Natives] node\_name unable to load JNA native support library, native methods will be disabled. java.lang.UnsatisfiedLinkError: /tmp/jna/--146.....tmp: /lib64/libc.so.6: version `GLIBC_2.7` not found ................................. ... loaded module ... ... loaded module ... ... node\_name initialized ... node\_name starting ... .......................... ... node\_name started Any help to address this issue will be appreciated Thanks in advance ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 21, 2020, 12:05am UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/2 "2020-07-21T00:05:40Z")
Can you post more of the log you are seeing please? ---
**Author:** ![dzyubanv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzyubanv/32/24110_2.png) [@dzyubanv](https://discuss.elastic.co/u/dzyubanv)\ **Post date:** [July 21, 2020, 1:44pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/3 "2020-07-21T13:44:29Z")
Thanks for the feedback Mark, Here are some more information from ES log [WARN][o.e.b.Natives] node\_name unable to load JNA native support library, native methods will be disabled. java.lang.UnsatisfiedLinkError: /tmp/jna/--146.....tmp: /lib64/libc.so.6: version `GLIBC_2.7` not found (required by /tmp/jna/--1462778291/jna473135465896030289.tmp) at java.lang.ClassLoader$NativeLibrary.load(NativeMethod) ~[?1.8.0\_65] at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1938) ~[?1.8.0\_65] ................................. at java.lang.Class.forName(Class.java:264) ~[?1.8.0\_65] at org.elasticsearch.bootstrap.Natives.(Natives.java:45) [elasticsearch-7.8.0.jar:7.8.0] ................................ at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:170) [elasticsearch-7.8.0.jar:7.8.0] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:161) [elasticsearch-7.8.0.jar:7.8.0] at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:86) [elasticsearch-7.8.0.jar:7.8.0] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:127) [elasticsearch-cli-7.8.0.jar:7.8.0] at org.elasticsearch.cli.Command.main(Command.java:90) [elasticsearch-cli-7.8.0.jar:7.8.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:126) [elasticsearch-7.8.0.jar:7.8.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:92) [elasticsearch-7.8.0.jar:7.8.0] [date time goes here][WARN][o.e.b.Natives] node\_name cannot check if running as root because JNA is not available [date time goes here][WARN][o.e.b.Natives] node\_name cannot register console handler because JNA is not available [date time goes here][WARN][o.e.b.Natives] node\_name cannot getrlimit RLIMIT\_NPROC because JNA is not available ................................. [date time goes here][WARN][o.e.b.Natives] node\_name version[7.8.0], pid[29283], build[....] [date time goes here][WARN][o.e.b.Natives] node\_name JVM arguments [...] [date time goes here][WARN][o.e.b.Natives] node\_name loaded module[aggs-matrix-stats] ................................. ... loaded module ... ... loaded module ... [date time goes here][WARN][o.e.b.Natives] node\_name initialized [date time goes here][WARN][o.e.b.Natives] node\_name starting ... [date time goes here][WARN][o.e.b.Natives] node\_name publish\_address ...... .......................... [date time goes here][WARN][o.e.b.Natives] node\_name refreshed keys [date time goes here][WARN][o.e.b.Natives] node\_name started **The node started and joined the cluster but the starting process capture the CLI console and to release it I need manual intervention with Ctl-C.** **I expect the CLI console should be automatically released and available to start another node.** Thanks so much for your help and patience ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 21, 2020, 11:26pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/4 "2020-07-21T23:26:45Z")
> [@dzyubanv](#): > > **The node started and joined the cluster but the starting process capture the CLI console and to release it I need manual intervention with Ctl-C.** > **I expect the CLI console should be automatically released and available to start another node.** That's pretty standard for Linux based systems. Have a look on the web for running tasks in the background to see what you can do. Alternatively, you should really use the service files that the DEB/RPM packages provide. ---
**Author:** ![dzyubanv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzyubanv/32/24110_2.png) [@dzyubanv](https://discuss.elastic.co/u/dzyubanv)\ **Post date:** [July 22, 2020, 1:32pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/5 "2020-07-22T13:32:03Z")
Thanks Mark for the feedback. DEB/RPM packages with service files is not the option for us. We've being running the ES-5.6.3 multi-node cluster in test and prod environments and have the deployment/monitoring process in place already. Now we'd like to migrate the old cluster to new ES-7.8.0. The starting node command, I provided at the beginning of this thread, worked well with no issues on ES-5.6.3 and that is why I'm wondering why it is Not working on ES-7.8.0. I'll follow up your advise and search the web. If you have more specific advise related to ES-7.8.0 starting process and resolving the above mentioned issue it would be appreciated. Is there any document elsewhere allowing to see/compare/evaluate changes for ES major releases? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 22, 2020, 9:16pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/6 "2020-07-22T21:16:04Z")
This is not an Elasticsearch issue. If you run any process in linux in the foreground it'll hold the focus of the shell, then if you use `ctrl+c` it'll pause the process. I don't know how you used to start the process, but doing it manually doesn't sound very efficient. ---
**Author:** ![dzyubanv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzyubanv/32/24110_2.png) [@dzyubanv](https://discuss.elastic.co/u/dzyubanv)\ **Post date:** [July 22, 2020, 11:06pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/7 "2020-07-22T23:06:30Z")
Actually I'm running the shell script which at the end produces the following line ES\_JAVA\_OPTS="-Dmapper.allow\_dots\_in\_name=true -Xms${ES\_HEAP\_SIZE} -Xmx${ES\_HEAP\_SIZE}" bin/elasticsearch -d -p /path\_to\_pid/es-pid And this worked for me couple of years with ES-5.6.3. I was able to start first node by running starting script, then the console was released and I was able to start second node from the same terminal and so on. To start nodes of ES-7.8.0 I'm using the same shell script and the console is not released despite the node started and joined the cluster. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 22, 2020, 11:11pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/8 "2020-07-22T23:11:10Z")
Ah ok. Well that's outside the immediate scope of what we can assist with, as it's a custom script. But if you post the script, we might be able to offer more advice. ---
**Author:** ![dzyubanv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzyubanv/32/24110_2.png) [@dzyubanv](https://discuss.elastic.co/u/dzyubanv)\ **Post date:** [July 22, 2020, 11:17pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/9 "2020-07-22T23:17:27Z")
Thanks Mark for the feedback The starting process capture the terminal with 2 lines future versions of Elasticsearch will require java 11; your java version from [u/hadoop/java/JDK 1.8.0\_65/jre] does not meet this requirement future versions of Elasticsearch will require java 11; your java version from [u/hadoop/java/JDK 1.8.0\_65/jre] does not meet this requirement which come up from ES-7.8.0 somehow and that is why I think it is ES-7.8.0 related (?) ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 22, 2020, 11:18pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/10 "2020-07-22T23:18:23Z")
I think you need to post the entire script you are running. ---
**Author:** ![dzyubanv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzyubanv/32/24110_2.png) [@dzyubanv](https://discuss.elastic.co/u/dzyubanv)\ **Post date:** [August 4, 2020, 3:37pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/11 "2020-08-04T15:37:43Z")
Mark, [1]I addressed this issue using standard technique and start node as follows **script\_to\_start\_es\_node.sh [inp\_arg\_node\_name\_to\_start] [inp\_arg\_cluster\_name] \> /dev/null 2&1 &** and now the node started as expected releasing the cmd and allowing to run the script again to start second node without manual intervention [2]script\_to\_start\_es\_node.sh accepts input arguments, export $JAVA\_HOME and at the end produces the following command to start particular node as follows ES\_JAVA\_OPTS="-Dmapper.allow\_dots\_in\_name=true -Xms${ES\_HEAP\_SIZE} -Xmx${ES\_HEAP\_SIZE}" **bin/elasticsearch** -d -p /path\_to\_pid/es-pid _ **\> /dev/null 2&1 &** _ I tried to understand why old version ES-5.6.3 allowed me to start node without the "\> /dev/null 2&1 &" and new version ES-7.8.0 starting process captures the cmd terminal and requires Ctl-l to release it. I think the message on the cmd "future versions of Elasticsearch will require java 11; your java version from [u/hadoop/java/JDK 1.8.0\_65/jre] does not meet this requirement" has been produced by the ES-7.8.0 code. It seems the ES-7.8.0 checks up the java version somehow (if bundled jdk is not in use) and produces the alert message about the "...java 11..." and **captures** the cmd terminal, which, I think, shouldn't happen (?) Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 1, 2020, 3:37pm UTC](https://discuss.elastic.co/t/starting-es-7-8-0-hung-up-cli/241768/12 "2020-09-01T15:37:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.