Hi Radu, Thanks for using Trafodion. With the help from Suresh, we looked at the core files in your cluster. We believe that there are two scenarios that is causing the Trafodion processes to dump core.
Scenario 1: Core dumped by tdm_arkesp processes. Trafodion engine has assumed the entity /proc/meminfo/Committed_AS is available in all flavors of linux. The absence of this entity is not handled correctly by the trafodion tdm_arkesp process and hence it dumped core. Please file a JIRA using this link https://issues.apache.org/jira/secure/CreateIssue!default.jspa and choose "Apache Trafodion" as the project to report a bug against. Scenario 2: Core dumped by tdm_udrserv processes. From our analysis, this problem happened when the process attempted to create the JVM instance programmatically. Few days earlier, we have observed similar issue in your cluster when java -version command was attempted. But, java -version or $JAVA_HOME/bin/java -version works fine now. Was there any change made to the cluster recently to avoid the problem with java -version command? You can please delete all the core files in sql/scripts directory and issue the command to invoke SPJ and check if it still dumps core. We can look at the core file if it happens again. Your solution to the java -version command would be helpful. For the failures with HammerDB, can you please send us the exact error message returned by the Trafodion engine to the application. This might help us to narrow down the cause. You can also look at $MY_SQROOT/logs/trafodion.dtm.log to check if any transaction conflict is causing this error. Selva -----Original Message----- From: Radu Marias [mailto:[email protected]] Sent: Tuesday, September 15, 2015 9:09 AM To: dev <[email protected]> Subject: Re: odbc and/or hammerdb logs Also noticed there are several core. files from today in */home/trafodion/trafodion-20150828_0830/sql/scripts*. If needed please provide a gmail address so I can share them via gdrive. On Tue, Sep 15, 2015 at 6:29 PM, Radu Marias <[email protected]> wrote: > Hi, > > I'm running HammerDB over trafodion and when running virtual users > sometimes I get errors like this in hammerdb logs: > *Vuser 1:Failed to execute payment* > > *Vuser 1:Failed to execute new order* > > I'm using unixODBC and I tried to add these line in */etc/odbc.ini* > but the trace file is not created. > *[ODBC]* > *Trace = 1* > *TraceFile = /var/log/odbc_tracefile.log* > > Also tried with *Trace = yes* and *Trace = on*, I've found multiple > references for both. > > How can I see more logs to debug the issue? Can I enable logs for all > queries in trafodion? > > -- > 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.
