trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liu Ming" <>
Subject Re: RE: Re: sqstart error YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Aborted (signal 6)
Date Tue, 01 Sep 2015 12:19:11 GMT
So this is a new issue for me, which is normal since I have very few experience of installing
trafodion :-)I read through Radu's installation log, and see some message like this:
.../usr/bin/pdcp -R ssh -w node1,node2,node3,node4,node5 -x node1 sqconfig sqshell gomon.cold
gomon.warm shell.env mon.env /home/trafodion/trafodion-20150828_0830/sql/scripts 
pdcp@node1: can't stat shell.env
pdcp@node1: can't stat mon.env
...pdcp@node1: can't stat /home/trafodion/sqcert

So Radu, would you please check if you have these files on node1? And on which node did you
perform the installation?
If files were missing, you can try to copy them from other nodes to node1.
But I have no idea what these files used for, seems critical to Monitor.
----- Original Message -----
From: Atanu Mishra <>
Subject: RE: Re: sqstart error YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Aborted (signal
Date: 2015-09-01 13:01

Hi Ming,
Good point. Amanda did check the ulimits. They are good. See below.
[trafodion@euve79672 ~]$ pdsh $MY_NODES ulimit -a
euve79674: core file size          (blocks, -c) unlimited
euve79674: data seg size           (kbytes, -d) unlimited
euve79674: scheduling priority             (-e) 0
euve79674: file size               (blocks, -f) unlimited
euve79674: pending signals                 (-i) 1805076
euve79674: max locked memory       (kbytes, -l) unlimited
euve79674: max memory size         (kbytes, -m) unlimited
euve79674: open files                      (-n) 32768
euve79674: pipe size            (512 bytes, -p) 8
euve79674: POSIX message queues     (bytes, -q) 819200
euve79674: real-time priority              (-r) 0
euve79674: stack size              (kbytes, -s) 10240
euve79674: cpu time               (seconds, -t) unlimited
euve79674: max user processes              (-u) 100000
euve79674: virtual memory          (kbytes, -v) unlimited
euve79674: file locks                      (-x) unlimited
euve79676: core file size          (blocks, -c) unlimited
euve79676: data seg size           (kbytes, -d) unlimited
euve79676: scheduling priority             (-e) 0
euve79676: file size               (blocks, -f) unlimited
euve79676: pending signals                 (-i) 1805076
euve79676: max locked memory       (kbytes, -l) unlimited
euve79676: max memory size         (kbytes, -m) unlimited
euve79676: open files                      (-n) 32768
euve79676: pipe size            (512 bytes, -p) 8
euve79676: POSIX message queues     (bytes, -q) 819200
euve79676: real-time priority              (-r) 0
euve79676: stack size              (kbytes, -s) 10240
euve79676: cpu time               (seconds, -t) unlimited
euve79676: max user processes              (-u) 100000
euve79676: virtual memory          (kbytes, -v) unlimited
euve79676: file locks                      (-x) unlimited
euve79672: core file size          (blocks, -c) unlimited
euve79672: data seg size           (kbytes, -d) unlimited
euve79672: scheduling priority             (-e) 0
euve79672: file size               (blocks, -f) unlimited
euve79672: pending signals                 (-i) 1547029
euve79672: max locked memory       (kbytes, -l) unlimited
euve79672: max memory size         (kbytes, -m) unlimited
euve79672: open files                      (-n) 32768
euve79672: pipe size            (512 bytes, -p) 8
euve79672: POSIX message queues     (bytes, -q) 819200
euve79672: real-time priority              (-r) 0
euve79672: stack size              (kbytes, -s) 10240
euve79672: cpu time               (seconds, -t) unlimited
euve79672: max user processes              (-u) 100000
euve79672: virtual memory          (kbytes, -v) unlimited
euve79672: file locks                      (-x) unlimited
euve79675: core file size          (blocks, -c) unlimited
euve79675: data seg size           (kbytes, -d) unlimited
euve79675: scheduling priority             (-e) 0
euve79675: file size               (blocks, -f) unlimited
euve79675: pending signals                 (-i) 1805076
euve79675: max locked memory       (kbytes, -l) unlimited
euve79675: max memory size         (kbytes, -m) unlimited
euve79675: open files                      (-n) 32768
euve79675: pipe size            (512 bytes, -p) 8
euve79675: POSIX message queues     (bytes, -q) 819200
euve79675: real-time priority              (-r) 0
euve79675: stack size              (kbytes, -s) 10240
euve79675: cpu time               (seconds, -t) unlimited
euve79675: max user processes              (-u) 100000
euve79675: virtual memory          (kbytes, -v) unlimited
euve79675: file locks                      (-x) unlimited
euve79673: core file size          (blocks, -c) unlimited
euve79673: data seg size           (kbytes, -d) unlimited
euve79673: scheduling priority             (-e) 0
euve79673: file size               (blocks, -f) unlimited
euve79673: pending signals                 (-i) 1547029
euve79673: max locked memory       (kbytes, -l) unlimited
euve79673: max memory size         (kbytes, -m) unlimited
euve79673: open files                      (-n) 32768
euve79673: pipe size            (512 bytes, -p) 8
euve79673: POSIX message queues     (bytes, -q) 819200
euve79673: real-time priority              (-r) 0
euve79673: stack size              (kbytes, -s) 10240
euve79673: cpu time               (seconds, -t) unlimited
euve79673: max user processes              (-u) 100000
euve79673: virtual memory          (kbytes, -v) unlimited
euve79673: file locks                      (-x) unlimited
-----Original Message-----
From: Liu Ming []
Sent: Monday, August 31, 2015 9:35 PM
To: dev <>
STRING: Aborted (signal 6)
Hi, Radu,
Typically when I saw this error is due to the ulimit setting. Once
properly installed, the ulimit setting of 'trafodion' user ID should look
like this:
trafodion   soft   core unlimited
trafodion   hard   core unlimited
trafodion   soft   memlock unlimited
trafodion   hard   memlock unlimited
trafodion   soft   nofile 32768
trafodion   hard   nofile 65536
trafodion   soft   nproc 100000
trafodion   hard   nproc 100000
trafodion   soft nofile 8192
trafodion   hard nofile 65535
Would you please check this first?If ulimit is not properly set, there
must be some issue during the installation. Since both log4cxx install and
ulimit setting were done in traf_setup, there may be some issue in that
script, I will check your installation log asap.
As workaround, if ulimit is not properly set, you can set it by
hand.Either change the /etc/security/limits.conf directlyor add a new
traf.conf under /etc/security/limits.d/ Thanks,Ming
----- Original Message -----
From: Radu Marias <>
To: dev <>
STRING: Aborted (signal 6)
Date: 2015-09-01 11:13
Any thoughts on this?
On Mon, Aug 31, 2015, 18:12 Radu Marias <> wrote:
> The linux kernel is *2.6.32-042stab103.6* #uname -a Linux node1
> 2.6.32-042stab103.6 #1 SMP Wed Jan 21 13:07:39 MSK 2015 x86_64
> x86_64 x86_64 GNU/Linux
> On Mon, Aug 31, 2015 at 6:05 PM, Radu Marias <>
>> Hi Amanda,
>> It's *installer-20150828_0830*, I didn't created the trafodion user id.
>> Noticed an error somewhere in logs similar to missing *log4cxx* on
>> *sqstart*, so assumed the installer didn't installed it and I
>> manually installed it.
>> Also performed *trafodion_uninstaller* after that and installed on
>> clean again.
>> On Mon, Aug 31, 2015 at 5:58 PM, Amanda Moran
>> <>
>> wrote:
>>> Hi there Radu-
>>> There is a bug I just found in the installer with regards to the
>>> dcs-site.xml file, I will be checking in that fix soon. Glad you
>>> knew how to fix it on your own! Great work!
>>> log4cxx wasn't installed by the installer? Had you already created
>>> the trafodion user id? What version of the installer are you using?
>>> Thanks!
>>> On Mon, Aug 31, 2015 at 7:54 AM, Radu Marias <>
>>> wrote:
>>> > Hi.
>>> >
>>> > I have 5 virtual machines with:
>>> > *Centos 6.5*
>>> > *Ambari 2.1*
>>> > *HDP 2.2*
>>> >
>>> > Installation of *trafodion-20150828_0830* is ok but it fails on
>>> *sqstart*.
>>> >
>>> > After installation the *dcs-site.xml* file was empty. I created
>>> > one
>>> with
>>> > the content attached, in short:
>>> >
>>> > *<name>dcs.zookeeper.quorum</name>*
>>> > *<value>node2,node1,node3</value>*
>>> >
>>> > *<name>dcs.dns.interface</name>*
>>> > *<value>venet0</value>*
>>> >
>>> > Also *log4cxx* wasn't installed by trafodion installer, I
>>> > installed it manually on all nodes.
>>> >
>>> > When running *sqstart* it fails, attached are the logs.
>>> > One that seems relevant to me is in *monitor.mpirun.out*, seems
>>> > that
>>> the
>>> > monitor is not starting:
>>> >
>>> > 6)* *This typically refers to a problem with your application.*
>>> > *Please see the FAQ page for debugging suggestions*
>>> >
>>> > --
>>> > And in the end, it's not the years in your life that count. It's
>>> > the
>>> life
>>> > in your years.
>>> >
>>> --
>>> Thanks,
>>> Amanda Moran
>> --
>> And in the end, it's not the years in your life that count. It's the
>> life in your years.
> --
> And in the end, it's not the years in your life that count. It's the
> life in your years.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message