I am trying to install and run elasticsearch on my raspberry pi and when I execute the command sudo service elasticsearch restart I don't see elasticsearch running and when I check the status using the command sudo service elasticsearch status I see the below response
Dec 28 23:15:32 raspberrypi systemd[1]: Starting LSB: Starts elasticsearch...
Dec 28 23:15:32 raspberrypi elasticsearch[21031]: [warning] /etc/init.d/elasticsearch: JVM flavor 'sun6' not understood
Dec 28 23:15:32 raspberrypi elasticsearch[21031]: [warning] /etc/init.d/elasticsearch: No java runtime was found
Dec 28 23:15:32 raspberrypi systemd[1]: Started LSB: Starts elasticsearch.
I have below java version installed on my raspberry pi
root#raspberrypi:/home/pi# java --version
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-post-Raspbian-1deb10u1)
OpenJDK Server VM (build 11.0.11+9-post-Raspbian-1deb10u1, mixed mode)
Not sure if the issue is with Java version or elasticsearch version . Also on hitting curl localhost:9200 I get connection refused error. And on executing below ./bin/elasticsearch --version I receive the error
root#raspberrypi:/usr/share/elasticsearch# ./bin/elasticsearch --version
Option requires an argument: '--version'.
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Note : I am using Java 11 , is that a issue ?
Related
I am currently trying to install Neo4j on my Raspberry Pi. The installation for the latest version worked great so far.
When I tried neo4j start I received this error message but was able to resolve it by setting dbms.memory.heap.initial_size=12m and dbms.memory.heap.max_size=12m and dbms.memory.pagecache.size=1g (allthough that feels wrong to me since my Pi has 8GB of memory):
nohup: ignoring input
2021-01-26 21:54:18.409+0000 ERROR Invalid memory configuration - exceeds physical memory. Check the configured values for dbms.memory.pagecache.size and db>
2021-01-26 21:54:18.436+0000 INFO Neo4j Server shutdown initiated by request
2021-01-26 21:54:18.437+0000 INFO Stopped.
Now, when I try to start neo4j I get this error in my logs:
nohup: ignoring input
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class org.neo4j.configuration.GraphDatabaseSettings
at org.neo4j.server.NeoBootstrapper.start(NeoBootstrapper.java:105)
at org.neo4j.server.NeoBootstrapper.start(NeoBootstrapper.java:90)
at org.neo4j.server.CommunityEntryPoint.main(CommunityEntryPoint.java:35)
2021-01-26 22:20:55.271+0000 INFO [o.n.s.CommunityBootstrapper] Neo4j Server shutdown initiated by request
2021-01-26 22:20:55.290+0000 INFO [o.n.s.CommunityBootstrapper] Stopped.
I have now been trying to google the problem for a couple hours but I feel like I don't really know what to look for.
My setup:
Raspberry Pi 4 (8 GB memory)
Ubuntu Server (uname -a returns Linux ubuntu 5.8.0-1011-raspi #14-Ubuntu SMP PREEMPT Tue Dec 15 08:53:29 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux)
Java 11 (java -version returns openjdk version "11.0.9.1" 2020-11-04 OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.20.10) OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.20.10, mixed mode))
Neo4j version 4.2.3
After some more trying it seems like it is a problem with the latest Neo4j version (4.2.3).
I now installed version 4.0.11 and it works without any problems.
I successfully installed elasticsearch along with the fulltextsearch in nextcloud following the information provided here.
The search worked fine. Recently I noticed that the elasticsearch service failed to start properly. When I manually restarted initially the serviced seemed to run fine.
sudo service elasticsearch status
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: active (running) since Di 2018-04-10 12:10:15 CEST; 1s ago
Docs: http://www.elastic.co
Main PID: 5958 (java)
Tasks: 6
Memory: 432.7M
CPU: 1.391s
CGroup: /system.slice/elasticsearch.service
└─5958 /usr/bin/java -Xms3g -Xmx3g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=t...
But after about 10 seconds it stoped with:
sudo service elasticsearch status
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Di 2018-04-10 12:10:23 CEST; 24s ago
Docs: http://www.elastic.co
Process: 5958 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 5958 (code=exited, status=1/FAILURE)
Apr 10 12:10:15 Ubuntu-Server systemd[1]: Started Elasticsearch.
Apr 10 12:10:23 Ubuntu-Server systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Apr 10 12:10:23 Ubuntu-Server systemd[1]: elasticsearch.service: Unit entered failed state.
Apr 10 12:10:23 Ubuntu-Server systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
I am running elasticsearch version 6.2.3 on Ubuntu 16.04 with java version
java -version
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
I would like to provide more detailed error logs, but I do not know where to search for them. Please tell me which information is needed and where to find it.
Thank you very much for help.
Have you tried upgrading Virtual Memory max map count?
https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html
Without that change ES is shutting down right after it starts.
If so, try to post more info from logs.
Logs should be located here:
/var/log/elasticsearch
/var/log/syslog
or by typing:
journalctl -xe and find something about: "Elasticsearch (....) exited"
My Cassandra won't start on a new installed root...
/var/log/cassandra/debug.log prints:
ERROR [main] 2018-02-03 07:13:46,463 CassandraDaemon.java:706 - Exception encountered during startup
java.lang.AbstractMethodError: org.apache.cassandra.utils.JMXServerUtils$Exporter.exportObject
root#srv49023:~# java -version
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
root#srv49023:~# systemctl status cassandra
● cassandra.service - LSB: distributed storage system for structured data
Loaded: loaded (/etc/init.d/cassandra)
Active: active (exited) since Sat 2018-02-03 07:13:43 EST; 1min 8s ago
Process: 213 ExecStart=/etc/init.d/cassandra start (code=exited, status=0/SUCCESS)
Feb 03 07:13:43 srv49023 systemd[1]: Started LSB: distributed storage system for structured data.
Thanks for helping!
This seems to relate to an upgrade to the JDK to 8u161 which was released 2 days ago.
A ticket has been opened on the Cassandra Jira
There is no published work-around that I can find. You might have to go back to an earlier version of the JDK or wait for Cassandra 3.11.2 which fixes the issue.
If waiting until Cassandra 3.11.2 is not an option, you can use an old version of Java and of Cassandra. Example below.
Download the binary tarbell (-bin) of an old Cassandra version (link). I used 3.10.0
Extract downloaded tarbell: tar -xvf apache-cassandra-3.100bin.tar.gz -C /home/ty/src (more details on extracting)
Download old Java version (link). I used Java SE Development Kit 8u151 (1.8.151)
Remove incompatible version of Java (Java 1.8.161) (instructions).
For example:
[root#localhost ty]# rpm -qa | grep java
tzdata-java-2017b-2.fc27.noarch
abrt-java-connector-1.1.0-14.fc27.x86_64
java-1.8.0-openjdk-headless-1.8.0.144-7.b01.fc27.x86_64
javapackages-tools-5.0.0-7.fc27.noarch
[root#localhost ty]# sudo yum remove java-1.8.0-openjdk-headless-1.8.0.144-7.b01.fc27.x86_64
Install older version of Java: rpm -ivh jdk-8u151-linux-x64.rpm
Cd to your Cassandra directory and try starting Cassandra: bin/cassandra -f (more instructions)
Im using Openshift Platfrom (jre 1.6) to deploy my java application with jasper reports. From last few days Im receiving following exception during jasper report execution.
java.lang.NullPointerException
sun.font.FontManager.getDefaultPlatformFont(FontManager.java:3409)
sun.java2d.SunGraphicsEnvironment$2.run(SunGraphicsEnvironment.java:263)
java.security.AccessController.doPrivileged(Native Method)
sun.java2d.SunGraphicsEnvironment.<init>(SunGraphicsEnvironment.java:164)
any info how to resolve this issue?
Our sysadmins had updated java to
java version "1.6.0_39"
OpenJDK Runtime Environment (IcedTea6 1.13.11) (rhel-1.13.11.1.el6_8-x86_64)
OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode)
on
Linux version 2.6.32-573.7.1.el6.x86_64 (mockbuild#x86-031.build.eng.bos.redhat.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC) ) #1 SMP Thu Sep 10 13:42:16 EDT 2015
I got around that problem by installing these with yum
dejagnu.noarch 1:1.4.4-17.el6
dejavu-sans-mono-fonts.noarch 2.33-1.el6
dejavu-serif-fonts.noarch 2.33-1.el6
yum install dejagnu.noarch 1:1.4.4-17.el6
yum install dejavu-sans-mono-fonts.noarch 2.33-1.el6
yum install dejavu-serif-fonts.noarch 2.33-1.el6
I'm getting this error. MdPnP project provides a java demo-app. I have it already running on beaglebone black and works fine. I´m trying to run it on RPi and I encounter this problem.
Application hangs when it tries to use dds external library.
Rpi uname -a = Linux raspberrypi 3.12.26-rt40+ #1 PREEMPT RT Fri Sep 19 23:59:27 MSK 2014 armv6l GNU/Linux
Please advise.
Thanks,
A fatal error has been detected by the Java Runtime Environment:
SIGILL (0x4) at pc=0xa8003d48, pid=4183, tid=3058177136
JRE version: Java(TM) SE Runtime Environment (7.0_60-b19) (build 1.7.0_60- b19)
Java VM: Java HotSpot(TM) Client VM (24.60-b09 mixed mode linux-arm )
Problematic frame:
C [libnddscore.so+0x72d48] call_gmon_start+0x7