This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Oct 8, 2013, 2:22 AM
4 Posts

Domino9 installation on RHEL 6

  • Category: Domino Server
  • Platform: Linux
  • Release: 9.0
  • Role: Administrator
  • Tags: RHEL6,Domino9
  • Replies: 5

Hi, need advise. I'm currently trying to install Domino 9 64Bit server on a RedHat Ent Linux 6 64Bit server. I've already installed the pre-requisites rpms like glibc, libstdc++, libXp but still the installations do not continue. I tried to create a log in the installation process and below is the log output. I'm just a newbie in Linux platform and don't know what this log means:

------------------
file type: 0
  file id: 0
  length: 177
  offset: 655148
  file name: instructions.txt
file type: 5
  file id: 1
  length: 650
  offset: 655325
  file name: Verify.jar
file type: 2
  file id: 2
  length: 746
  offset: 655975
  file name: launch.txt
file type: 4
  file id: 3
  length: 79259749
  offset: 656721
  file name: Linux64_IBM_jvm.bin
Executing launch script command: "/tmp/isjxJA69P/bin/java" -cp "":"setup.jar":"" -Dtemp.dir="/tmp" -Dis.jvm.home="/tmp/isjxJA69P" -DLinux64=1 -Dis.jvm.temp="1" -Dis.media.home="" -Dis.launcher.file="/install/domino9/linux64/domino/tools/setupLinux.bin" -Dis.jvm.file="/tmp/isjxJA69P/jvm" -Dis.external.home="/install/domino9/linux64/domino/tools"      run  "-console" "-G" "overwriteJVM=yes" in working directory /install/domino9/linux64/domino/tools
 
Oct 8, 2013, 10:38 AM
4 Posts
Domino9 installation on RHEL 6

I also have found this log in the /tmp folder but does not know what it means:

[root@ZZPTRSMTP domino]# cat /tmp/nuish.err
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000080
Handler1=00007F4254527900 Handler2=00007F42541E0FB0 InaccessibleAddress=0000000000000000
RDI=0000000000000058 RSI=0000000000000000 RAX=0000000000000001 RBX=0000000002384800
RCX=000000009E982203 RDX=000000000FEBFBFF R8=0000000000000000 R9=0000000000000000
R10=00007F42269323B0 R11=0000000002384800 R12=00007F42269325A8 R13=00007F4250000AD0
R14=0000000000000000 R15=0000000000000000
RIP=00000039C3014D70 GS=0000 FS=0000 RSP=00007F4226932438
EFlags=0000000000210202 CS=0033 RBP=00007F4226932580 ERR=0000000000000000
TRAPNO=000000000000000D OLDMASK=0000000000000000 CR2=0000000000000000
xmm0 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm2 00007f421c00c318 (f: 469812000.000000, d: 6.913061e-310)
xmm3 00007f421c00c360 (f: 469812064.000000, d: 6.913061e-310)
xmm4 00007f425468e300 (f: 1416160000.000000, d: 6.913108e-310)
xmm5 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm6 00007f4226932bb0 (f: 647179200.000000, d: 6.913070e-310)
xmm7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/lib64/ld-linux-x86-64.so.2
Module_base_address=00000039C3000000
Target=2_40_20121024_126067 (Linux 2.6.32-71.el6.x86_64)
CPU=amd64 (1 logical CPUs) (0xbc59c000 RAM)
----------- Stack Backtrace -----------
(0x00000039C3014D70 [ld-linux-x86-64.so.2+0x14d70])
(0x00000039C300AAEA [ld-linux-x86-64.so.2+0xaaea])
(0x00000039C300DEE0 [ld-linux-x86-64.so.2+0xdee0])
(0x00000039C30147B5 [ld-linux-x86-64.so.2+0x147b5])
JVM_Open+0x4b (0x00007F4254799BBB [libjvm.so+0x7bbb])
JVM_Open+0x12 (0x00007F42552BD6B2 [libjvm.so+0x36b2])
Java_java_io_UnixFileSystem_createFileExclusively+0xc2 (0x00007F4226C1F022 [libjava.so+0x1a022])
(0x00007F425453D9E3 [libj9vm24.so+0x2a9e3])
---------------------------------------
JVMDUMP039I Processing dump event "gpf", detail "" at 2013/10/08 17:56:30 - please wait.
JVMDUMP032I JVM requested System dump using '/root/linux64/domino/tools/core.20131008.175630.4203.0001.dmp' in response to an event
JVMPORT030W /proc/sys/kernel/core_pattern setting "|/usr/libexec/abrt-hook-ccpp /var/spool/abrt %p %s %u %c" specifies that the core dump is to be piped to an external program.  Attempting to rename either core or core.4212.
 
JVMDUMP010I System dump written to /root/linux64/domino/tools/core.20131008.175630.4203.0001.dmp
JVMDUMP032I JVM requested Java dump using '/root/linux64/domino/tools/javacore.20131008.175630.4203.0002.txt' in response to an event
JVMDUMP010I Java dump written to /root/linux64/domino/tools/javacore.20131008.175630.4203.0002.txt
JVMDUMP032I JVM requested Snap dump using '/root/linux64/domino/tools/Snap.20131008.175630.4203.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /root/linux64/domino/tools/Snap.20131008.175630.4203.0003.trc
JVMDUMP013I Processed dump event "gpf", detail "".
Oct 8, 2013, 7:14 PM
60 Posts
Could you, please, send to me the following information
Dump & core files that were created in these locations:

JVMDUMP010I System dump written to /root/linux64/domino/tools/core.20131008.175630.4203.0001.dmp
JVMDUMP032I JVM requested Java dump using '/root/linux64/domino/tools/javacore.20131008.175630.4203.0002.txt' in response to an event
JVMDUMP010I Java dump written to /root/linux64/domino/tools/javacore.20131008.175630.4203.0002.txt
JVMDUMP032I JVM requested Snap dump using '/root/linux64/domino/tools/Snap.20131008.175630.4203.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /root/linux64/domino/tools/Snap.20131008.175630.4203.0003.trc

Looks like jvm, used by installation process, crashed in library module, but not quite clear why.

While we are looking at the issue, you could try running java command with another java - if you have one installed on your system.

Command will be
"<your java>" -cp "":"tools/setup.jar":""   -DLinux64=1 -Dis.launcher.file="/install/domino9/linux64/domino/tools/setupLinux.bin"  -Dis.external.home="/install/domino9/linux64/domino/tools"      run  "-console" "-G" "overwriteJVM=yes"

[For newbie you had collected great info]


ikhasin@us.ibm.com
Oct 9, 2013, 2:46 AM
4 Posts
Could you, please, send to me the following information

Hi Irina,

Thank you for your response. I've sent the core,javacore and snap file to your email address. Hope you can have a look on it and see what's the problem why Domino 9 in not installing in our Linux 6 server.

Warm Regards,

Marlo 

Oct 14, 2013, 5:39 AM
4 Posts
Domino 9 Installation successful

Hi,

After doing the java command that Irina gave, I still unable to install the domino 9 server so I downloaded a new iso for RHEL 6.4 64bit server. I was able to install the Domino 9 64-bit on a new RedHat Enterprise Linux 6.4 64bit server.

Thank you Irina for your help.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal