Lack of records in Talend Log Table after die on error on component

[Anonymous]

Hello Talend Forge people,
I have a problem with generic Talend ODI mechanism.
Yesterday we had some technical problems and I wanted to diagnose it today.
However I spot that I don't have data in 'stats&logs' table or log file.
while I have records in stats table and in my additional error handler table there is no date in file nor database table created for talend logs:
select * from talend_logs where root_pid ='cJV8iN'
--no results
select * from talend_stats where root_pid ='cJV8iN'


To see the whole post, download it here

[Anonymous]

Hi,
What does your whole work flow look like? Did you use tStatCatcher and tLogCatcher components both in your parent and child job?
More information about your current job situation will be helpful for us to diagnose your issue.
Best regards
Sabrina

[Anonymous]

Hello Sabrina, we have two cases
for NOT WORKING scenario:

We are using tLogCatcher component only to store additional information in our db structure.
In this case its stand alone job.

2) For working correctly scenario we are using tLogCatcher components in both child and parent jobs.
and logging mechanism defined in Stats&Logs tab

[Anonymous]

Hello Sabrina,
I was told that we have some jobs with incomplete stats.
I have a strange example:
select * from talend_stats where root_pid ='swt1XT' order by moment;

moment	pid	father_pid	root_pid	system_pid	job_repository_id	job_version	origin	message_type	message	duration
2016-02-08 14:54:44	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1		begin		
2016-02-08 14:55:03	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tMysqlInput_2	begin		
2016-02-08 14:55:52	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tMysqlInput_2	end	success	48926
2016-02-08 14:55:53	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tMysqlInput_4	begin		
2016-02-08 14:58:22	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tMysqlInput_4	end	success	148419
2016-02-08 15:12:06	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tRedshiftRow_3	begin		
2016-02-08 15:12:06	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tRedshiftRow_3	end	success	499
2016-02-08 15:12:08	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tS3Put_1	begin		
2016-02-08 15:12:59	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tS3Put_1	end	success	50831
2016-02-08 15:12:59	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tRedshiftBulkExec_1	begin		
2016-02-08 15:14:17	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tRedshiftBulkExec_1	end	success	78194
2016-02-08 15:14:19	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tS3Put_2	begin		
2016-02-08 15:14:19	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tS3Put_2	end	failure	587
2016-02-08 15:14:20	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tLogCatcher_1	begin		
2016-02-08 15:14:20	swt1XT	swt1XT	swt1XT	6316	_nsBOsIMAEeW9iONWbYfBqg	0.1	tLogCatcher_1	end	success	551

As you can see we had an error in   tS3Put_2 and this error is visible in logs table.
After that error catcher component is triggered (we can see additional row in our own error table). Ends with success and.. nothing.
there is no row with swt1XT end status (and it should be 'failure').
Could you tell me if there is known scenario when we shouldn't expect end status info?
KR,
Michal

[Anonymous]

Hello Sabrina, 
Can I count for any feedback?