I am using
Ubuntu 12.04
Neo4j - Graph Database Kernel 2.0.0-M04
javac 1.7.0_25
java version "1.7.0_25
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Even though, I am using Oracle Java, I was getting warning:
"WARNING! You are using an unsupported Java runtime. Please use Oracle(R) Java(TM) Runtime Environment 7."
When I debug utils file in neo4j directory, I found a function with following comment:
# check if running JDK 6, warn if not
checkjvmcompatibility() {
$JAVACMD -version 2>&1 | egrep -q "Java HotSpot\\(TM\\) (64-Bit Server|Client) VM"
if [ $? -eq 1 ]
then
echo "WARNING! You are using an unsupported Java runtime. Please use Oracle(R) Java(TM) Runtime Environment 7."
else
$JAVACMD -version 2>&1 | egrep -q "java version \"1.7"
if [ $? -eq 1 ]
then
echo "WARNING! You are using an unsupported version of the Java runtime. Please use Oracle(R) Java(TM) Runtime Environment 7."
fi
fi
}
Some confusion :
comment of function shows that it is checking for java 6 but error message displayed use 'echo' shows that you are not using java run time 7.
So actually what Java is being expected by neo4j ?
I was using Oracle-Java-1.7 still it was throwing me error not using Oracle-Java1.7 .
Thanks
Amit Aggarwal
Neo4j 2.0 is supposed to run with Java 7 only. I guess the comment in the script is misleading. Please make JAVA_HOME points to the right directory. On linux this is not necessary valid if java -version shows version 7.
JAVA_HOME=/usr/lib/jvm/java-7-oracle
To check which version Neo4j is actually using run
grep "JVM information" -A 5 <neo4j_dir>/data/graph.db/messages.log
It is a bug, I got
ERROR! Neo4j cannot be started using java version 1.7.0_25.
...
http://localhost:7474/ is ready.
So it seems to start up OK, even though it gives this error message.
Related
I compiled harfbuzz 7.0.0 on Ubuntu 22.04 ok.
I want to install latest kitty terminal (0.27.1) where harfbuzz >= 1.5 is required.
Kitty did not find harfbuzz 7.0.0
When I typed "make" for Kitty, i get a system exit telling me that harfbuzz >= 1.5 is required and that the version is not found.
I typed "export PKG_CONFIG_PATH=/home/user/harfbuzz/harfbuzz-7.0.0/src" since that is where 'harfbuzz.pc' resides.
harbuzz is still not found when typing 'make' in the kitty directory.
Alternative solution implemented (worked ok): "curl -L https://sw.kovidgoyal.net/kitty/installer.sh | sh /dev/stdin"
I get build errors when using mvn unleash:perform because it tries to use the default Java VM to build the release instead of the one pointed to with JAVA_HOME or the one which was used to start the maven-unleash-plugin.
With -Dunleash.releaseArgs="--debug=true" -X, I can see that the outer Maven uses Java 11 and the inner uses 8.
I tried to fix this with:
mvn unleash:perform -Dunleash.releaseEnvironment="JAVA_HOME=$JAVA_HOME" -X |& tee mvn.log
but that leads to an NPE:
Caused by: java.lang.NullPointerException
at com.itemis.maven.plugins.unleash.steps.actions.BuildProject.setupInvocationRequest (BuildProject.java:123)
at com.itemis.maven.plugins.unleash.steps.actions.BuildProject.execute (BuildProject.java:73)
Is changing the default VM in Windows my only option?
In my case, the culprit was in .mavenrc (Linux) or %USERPROFILE%\mavenrc_pre.cmd (Windows, also check %USERPROFILE%\mavenrc_pre.bat). There, JAVA_HOME was hardcoded to some specific path.
The fix is to a) only set JAVA_HOME when it has no value and b) to display a warning (with path) when the variable is set. That way, people can't get confused by some silent behavior.
Solution in .mavenrc:
if [[ -z "$JAVA_HOME" ]]; then
export JAVA_HOME=...
echo "~/.mavenrc: Setting JAVA_HOME to $JAVA_HOME"
fi
For %USERPROFILE%\mavenrc_pre.cmd, use:
if "%JAVA_HOME%"=="" (
set JAVA_HOME=...
echo %USERPROFILE%\mavenrc_pre.cmd: Setting JAVA_HOME to %JAVA_HOME%
)
I am trying to install PostgreSQL 9.6 on a CentOS 7.6 VM using installer binary postgresql-9.6.6-1-linux-x64.run. I have run the below command to install:
./postgresql-9.6.6-1-linux-x64.run --installer-language en --serviceaccount postgres --servicename postgresqld --datadir "/home/postgres/" --prefix "/home/postgres" --superpassword **** --serverport 5432 --debuglevel 4 --debugtrace ./postgresql-debug.log --mode unattended
The debug trace log "./postgresql-debug.log" generated lot of encoded formatted text which cannot be understood.
It is not in base64 either. Can someone please help me how to decode the log.
Here is first few lines of debug trace log.
<errorDump>
<context>MwSUdmn65MlwA81MDBVmg34ZjlXDReCYnIxjAwgZ15jHp8UXS0OQ2L/a8iph
kR7moeATHKE7UkwbqeM1bluAAET0rr2AXwDdQdowNVgI5BYvwz7YBMUd5nsn
AgldXNczMw/dSiFsj334+Bb/iOhXuaQo/S0FzyzqFPEqaBHVjPrJv70vdhTD
dmHn7vKY/Zo2xZ/eyouLxobkFYdRw2zqX+HAkRpygUNPqHzvy0AJg6Kln8uv
GhwphVedsu1buJc7gb2T+1HWqsCXB8jm9LI7GmDvA62sKmgmjxRDMl+UI6UE
rn7gbhrc59oI4Wjem2aJK8ufTHuYM+xfXNFc5yY9CtoI4Wjem2aJzo+oIONC
gYoZFhKeT1iysdoI4Wjem2aJ8B3Ju++KR9us+PNdpxdCk9oI4Wjem2aJL+bx
eZCCp83ng4pRhi+GoQyXnF++cnIKHlx0bVlSX7X7AV8O24BoFwyXnF++cnIK
rJUoxqtsZe6URWF1lQj7xgyXnF++cnIKkX2dNd0GKfLyeRPuEuaM1N6/6xVl
I am trying to start ejabber 16.05 server on mac os 10.7.5. while starting up, it gives error. on further investigation, I found that "erl" executor file shipped with ejabber is throwing "Segmentation Fault:11" while running independently. I firmly believe that resolving issue with "erl" file execution will solve server start up issue. can anyone please help. Below is the code from "erl" that is causing segmentation fault error
#!/bin/sh
ROOTDIR=/Applications/ejabberd-15.06
export ROOTDIR
BINDIR=$ROOTDIR/bin
export BINDIR
EMU=beam
export EMU
PROGNAME=$BINDIR/erl
export PROGNAME
PATH=$BINDIR:$PATH
export PATH
arch() {
case `uname -m` in
i[3456]86 ) echo x86 ;;
i86pc) echo x86 ;;
armv7*) echo armhf ;;
arm*l) echo armel ;;
* ) echo `uname -m | tr A-Z a-z` ;;
esac
}
os=`uname -s | tr A-Z a-z`
cpu=`arch`
ARCHDIR=${os}-${cpu}
export ARCHDIR
# Dynamic libraries
LD_LIBRARY_PATH=$ROOTDIR/lib/$ARCHDIR
export LD_LIBRARY_PATH
DYLD_LIBRARY_PATH=$LD_LIBRARY_PATH
export DYLD_LIBRARY_PATH
exec $BINDIR/erlexec ${1+"$#"}
I just see that you are using OSX 10.7. We do not test ejabberd binary installer on version of OS that are so old.
I do not even expect the binary installer to run on such an old release.
If you have to run ejabberd on that OSX version, you have to build it from source.
ejabberd source are available on official ejabberd Github.
Documentation for installation and build is here Installing ejabberd from source code.
I try to run android simulator in Rhostudio on Windows 7, but below error is showing, what could be the problem? Please help me!
process additional java files for build from extensions :
ext_build.files not found - no additional java files
PWD: D:/bin/RhoStudio/ruby/lib/ruby/gems/1.8/gems/rhodes-3.3.2
CMD: "C:/Program Files/Java/jdk1.6.0_11/bin/javac.exe" -g -d D:/Messenger/bin/tmp/Rhodes -source 1.6 -target 1.6 -nowarn -encoding latin1 -classpath D:/Bin/Android/android-sdk/platforms/android-15/android.jar;D:/Messenger/bin/tmp/Rhodes #C:/Users/Pete/AppData/Local/Temp/RhodesSRC_build20120325-2984-1ejkqvm-0
rake aborted!
No such file or directory - "C:/Program Files/Java/jdk1.6.0_11/bin/javac.exe" -g -d D:/Messenger/bin/tmp/Rhodes -source 1.6 -target 1.6 -nowarn -encoding latin1 -classpath D:/Bin/Android/android-sdk/platforms/android-15/android.jar;D:/Messenger/bin/tmp/Rhodes #C:/Users/Pete/AppData/Local/Temp/RhodesSRC_build20120325-2984-1ejkqvm-0
Tasks: TOP => run:android => run:android:emulator => device:android:debug => package:android => build:android:all => build:android:rhodes
(See full trace by running task with --trace)
Error in build application
The problem is I do not set correct path for the Java SDK.