I have Aptana version 3.4.2.201308081805 on Linux Mint 15 64bit
was open just once and now anytime when I want to start the Aptana crash
here is the one from a few crash log:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007fab6e08a938, pid=4403, tid=140373276522240
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libzip.so+0x4938] Java_java_util_zip_ZipFile_getZipMessage+0x8d8
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Don't use OpenJDK
Use Java 7 from the wbupd8 repository
sudo apt-add-repository ppa:webupd8team/java
Prerequirements
sudo apt-get install software-properties-common
If you got problems with SWT take a look at
Eclipse cannot load SWT libraries
I managed to fix this issue by removing openjdk and installing oracle jdk.
The step by step instruction is provided in the following article
http://www.wikihow.com/Install-Oracle-Java-on-Ubuntu-Linux
so far no crash in aptana.
FYI: I am using lubuntu
Related
I was using Elasticsearch 6.8 via homebrew, and I was trying to upgrade to 7.3. Previously, on 6.8 I already got a warning about a log file that did not exist, but the server would still run - so I did nothing.
Now with 7.3, I get an error and the server won’t run:
Exception in thread "main" java.lang.RuntimeException: starting java failed with [1]
output:
[0.002s][error][logging] Error opening log file 'logs/gc.log': No such file or directory
[0.002s][error][logging] Initialization of output 'file=logs/gc.log' using options 'filecount=32,filesize=64m' failed.
error:
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Invalid -Xlog option '-Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m', see error log for details.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
at org.elasticsearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:111)
at org.elasticsearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:79)
at org.elasticsearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:57)
at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:89)
I tried creating the dir/file where elasticsearch was installed, but that did not work for me (or i did something wrong).
Reference: https://onecompiler.com/questions/3uwszcf3x/homebrew-installed-elasticsearch-failing-to-start
I have fixed this by changing the relative logs/gc.log path to an absolute path. Follow the below steps to solve the issue
Open jvm.options file which is located at /usr/local/etc/elasticsearch/jvm.options
Change the relative path to an absolute path
from the following
# JDK 9+ GC logging
9-:-Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m
to
# JDK 9+ GC logging
9-:-Xlog:gc*,gc+age=trace,safepoint:file=/usr/local/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m
Restart elasticsearch $ brew services restart elasticsearch-full or just start it without daemon - $ elasticsearch
I'm newbie in DB2 database administration and I couldn't think that I'd be stuck with the installation process. I read some documents before installation and found an interesting "db2prereqcheck" thing.
So I tried to run it before installation and got an error:
DBT3505E The db2prereqcheck utility was unable to determine the Linux distribution level.
About this error from ibm:
IBM Knowledge Center: DBT3505E
IBM Support: db2prereqcheck fails checking Linux distribution
I found some other answers where suggest to delete the files "/etc/issue" and "/etc/issue.net".
I checked my "/etc/issue*" files according to the tips. I filled that files with the example from the article in IBM Support, but nothing has changed. I tried running this script on other servers with CentOS, Debian operating systems, but got another error:
./db2prereqcheck
DBI1189E There has been an attempt to use db2prereqcheck
on an image for a platform that does not match the current platform
'Linux/x86-64' on which it is being run.
Explanation:
Possible causes include:
- This DB2 install image is not valid for the current
platform.
- The current platform is not supported by DB2.
User Response:
Install DB2 using the DB2 install image that corresponds
with the current platform 'Linux/x86-64'.
I've already installed db2, but my self-esteem is down. So the question is: my hands are a problem or is the problem in another? And how to make db2 work
Technical details:
cat /etc/issue
Amazon Linux AMI release 2018.03
Kernel \r on an \m
cat /etc/*-rel*
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
Amazon Linux AMI release 2018.03
cpe:/o:amazon:linux:2018.03:ga
uname -a
Linux hostname.host 4.14.47-56.37.amzn1.x86_64 #1 SMP Wed Jun 6 18:49:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
As you may have noticed, this is an EC2 instance.
DB2 versions:
IBM® Db2 11.1 Developer-C Edition for Linux® on AMD64 and Intel® EM64T systems (x64)
IBM® DB2 Express-C Version 11.1
I would appreciate your help in this matter. Thank you for your time.
If db2prereqcheck reports :
DBT3505E The db2prereqcheck utility was unable to determine the Linux
distribution level. Aborting the current installation ... Run
installation with the option "-f sysreq" parameter to force the
installation.
and if other IBM suggestions do not apply, then you may be able to avoid this symptom with the following workaround:
(as root)
cp /etc/os-release /etc/lsb-release
The reason it works is that some versions of db2prereqcheck look only for the following files in turn:
/etc/centos-release
/etc/redhat-release
/etc/SuSE-release
/etc/lsb-release
If none of those files are present, the DBT3505E symptom can result.
If your distro (or container) has an equivalent file (for example, Debian may have /etc/os-release) then simply copying it to /etc/lsb-release will allow db2prereqcheck to complete.
db2prereqcheck checks and understands only /etc/SuSE-release with the following content:
SUSE Linux Enterprise Server 15 (x86_64)
VERSION = 15
PATCHLEVEL= 1
This works also with OpenSuse Leap 15.1. This file is deprecated since SLES 12. So you must create it your self. Then run db2prereqcheck and install all missing libraries and kernel sources mentioned. Having all requirements fulfilled you may finally see the segmentation fault message:
Validating "Intel TCO WatchDog Timer Driver modules" ...
DBT3546E The db2prereqcheck utility failed to determine whether the
following file or package exists: "".
Segmentation fault (core dumped)
Don't worry!
Simply retest with db2prereqcheck -i. The -i parameter checks for prerequisites that are not Db2 pureScale related. If we don't install pureScale and all requirement are fulfilled, we can ignore this ugly segmentation fault.
Otherwise you must blacklist by adding:
blacklist iTCO_wdt
blacklist iTCO_vendor_support
Into the file /etc/modprobe.d/blacklist.conf
A further issue is related to:
export DISPLAY=your.machine.ip:0.0
running ./db2setup as root doesn't work.
./db2_install is deprecated, but it works.
First create the db2 users and groups as described by the IBM Knowledge Center.
Then run ./db2_install as root, followed by creating an instance using db2icrt.
Login as db2inst1 and test as described by the IBM Knowledge Center eventually creating the SAMPLE Database, etc. Normally "first steps" would do the job, but it crashes with javascript error. Hence you must do it manually!
Additional manual configuration may be required as opening the firewall for port 50001 and setting this port within /etc/services and within dbm cfg with:
db2 update dbm cfg using SVCENAME 50001
or
db2 update dbm cfg using SVCENAME db2c_db2inst1
If you use the latter you must update /etc/services with the line:
db2c_db2inst1 50001/tcp #and a comment like db2 tcp/ip
connection port.
I setup RocketMQ following the guide of Quick Start https://rocketmq.incubator.apache.org/docs/quick-start/ ,run
sh bin/mqnamesrv
the logs shows:
Java HotSpot(TM) Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=320m; support was removed in 8.0
Java HotSpot(TM) Server VM warning: Using the DefNew young collector with the CMS collector is deprecated and will likely be removed in a future release
Java HotSpot(TM) Server VM warning: UseCMSCompactAtFullCollection is deprecated and will likely be removed in a future release.
Error: Could not find or load main class org.apache.rocketmq.namesrv.NamesrvStartup
I come to the same problem, when I use rocketmq-4.0.0.
I unzip the source zip, and run the mqnamesrv
nohup sh bin/mqnamesrv &
the problem occurs...
my solution is following:
compile the source with maven-3.6:
mvn -Prelease-all -DskipTests clean install -U
then cd target/apache-rocketmq-all, I repeat the command:
nohup sh bin/mqnamesrv &
mq runs well.
I have a clean install of RStudio Server (Pro) on clean Ubuntu 14.04. Install was smooth only problem I have is with rJava. Everything else appears to be working fine.
To install the rJava package I installed the package from the R (running as sudo) from the console. This is what I have always done when setting up RStudio Servers. Once installed rJava works fine from the R console as sudo or normal user.
From the RStudio IDE I can load the rJava package, but when I call .jinit() I get errors:
library(rJava)
.jinit()
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error in .jinit() : Cannot create Java virtual machine (-4)
This is contrary to what happens if I ssh onto the server directly as same user and run the same commands from R console - this does not generata any error.
Any idea what is going on here? I have searched around and not found anything that helps. I tried completely uninstalling openjdk, tried reinstalling the package. Nothing seems to work - and because I get different behavior between the R console on the terminal and the R console in RStudio Server I am slightly puzzled.
The version of R on the console is:
$platform
[1] "x86_64-pc-linux-gnu"
$arch
[1] "x86_64"
$os
[1] "linux-gnu"
$system
[1] "x86_64, linux-gnu"
$status
[1] ""
$major
[1] "3"
$minor
[1] "1.2"
$year
[1] "2014"
$month
[1] "10"
$day
[1] "31"
$`svn rev`
[1] "66913"
$language
[1] "R"
$version.string
[1] "R version 3.1.2 (2014-10-31)"
$nickname
[1] "Pumpkin Helmet"
This is the same as the version that R Studio Server is using.
JAVA_HOME is the same from R console on terminal and R console in RStudio Server
> Sys.getenv('JAVA_HOME')
[1] "/usr/lib/jvm/java-1.7.0-openjdk-amd64/jre"
This is the same as the JAVA_HOME I get from the shell.
I have the following java version:
java -version
java version "1.7.0_75"
OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~trusty1)
OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)
Would love some suggestions or input from folks who have struggled with this same problem.
Cheers,
Matt
Have you check how much memory you set up for the JVM? I had the same issue as initially I set it up as 8g.
You can set up the size of JVM's memory using the following command:
options( java.parameters = "-Xmx8g" )
I did everything well in window, but fail in linux.
What i want to do is to compile ruby script to java bytecode with -Xcompile.invokedynamic=true parameters:
[sxu3#** rubyscript]$ jrubyc -Xcompile.invokedynamic=true hello.rb
OptionParser::InvalidOption: invalid option: -Xcompile.invokedynamic=true
complete at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1542
catch at org/jruby/RubyKernel.java:1282
complete at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1540
parse_in_order at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1380
catch at org/jruby/RubyKernel.java:1282
parse_in_order at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1347
order! at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1341
permute! at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1432
parse! at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:1453
compile_argv at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/shared/jruby/compiler.rb:83
initialize at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/1.9/optparse.rb:882
compile_argv at /homes/sxu3/tools/jruby-1.7.10/lib/ruby/shared/jruby/compiler.rb:35
(root) at /homes/sxu3/tools/jruby-1.7.10/bin/jrubyc:5
[sxu3#** rubyscript]$ jrubyc -Xcompile.invokedynamic=true hello.rb ^C
[sxu3#** rubyscript]$ which jrubyc
~/tools/jruby-1.7.10/bin/jrubyc
[sxu3#** rubyscript]$ jruby -v
jruby 1.7.10 (1.9.3p392) 2014-01-09 c4ecd6b on Java HotSpot(TM) Server VM 1.7.0_51-b13 [linux-i386]
[sxu3#** rubyscript]$
[sxu3#** rubyscript]$ uname -a
Linux .. 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Without -Xcompile.invokedynamic=true, jrubyc works but none of invokedynamic instruction is in generated bytecodes. Also,
"jrubyc -Xcompile.invokedynamic=true hello.rb"
works in window and i saw invokedynamic in class file in window.
I leave all other jrubyc properties(.jrubyrc) as default value
hello.rb is one line ruby script:
puts "hello world"
I also tried jrubyc 1.7.6 and the same errors . Anyone could provide some clue ?
[Update]:
Finally, I think the exception indicates jrubyc does not support -Xcompile.invokedynamic=true option. The jruby wiki page says jruby, instead of "jrubyc" can work with option.
I also had issues with jruby and invokedynamic. The problem is that invokedynamic is not really supported on JVM 1.7. To get it working you should install the JVM 1.8. You can read about the issues here: https://github.com/jruby/jruby/wiki/PerformanceTuning
But be careful when installing Java 8 - it's not so easy switching between versions and some programs like several eclipse IDEs don't want to run on that JVM.
However maybe jruby with invokedynamic works on Windows, because you have installed the Oracle JVM, which is a little bit different from the HotSpot OpenJDK version.