Pentaho

 View Only

 Unexpected error during job metadata load

  • Pentaho
  • Kettle
  • Pentaho
  • Pentaho Data Integration PDI
Daniel Clark's profile image
Daniel Clark posted 03-15-2019 16:32

I'm having an issue executing a job with kitchen.sh that executes fine within spoon. Any ideas? Please see below:

master_job

2019/03/15 11:51:34 - Master_Job - Starting entry [Workflow]

2019/03/15 11:51:34 - Master_Job - exec(5, 0, Workflow.0)

2019/03/15 11:51:34 - Workflow - Starting job entry

2019/03/15 11:51:34 - Workflow - Loading job from XML file : [null]

2019/03/15 11:51:34 - Workflow - ERROR (version 8.2.0.0-342, build 8.2.0.0-342 from 2018-11-14 10.30.55 by buildguy) : Error running job entry 'job' :

2019/03/15 11:51:34 - Workflow - ERROR (version 8.2.0.0-342, build 8.2.0.0-342 from 2018-11-14 10.30.55 by buildguy) : org.pentaho.di.core.exception.KettleException:

2019/03/15 11:51:34 - Workflow - Unexpected error during job metadata load

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.run (Job.java:384)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:497)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute (Job.java:680)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.execute (JobEntryJob.java:667)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta (JobEntryJob.java:1345)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta (JobEntryJob.java:1381)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMetaFromRepository (JobEntryJob.java:1353)

2019/03/15 11:51:34 - Workflow -

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta(JobEntryJob.java:1421)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta(JobEntryJob.java:1345)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.execute(JobEntryJob.java:667)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:680)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.execute(Job.java:497)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.Job.run(Job.java:384)

2019/03/15 11:51:34 - Workflow - Caused by: java.lang.NullPointerException

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMetaFromRepository(JobEntryJob.java:1353)

2019/03/15 11:51:34 - Workflow - at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta(JobEntryJob.java:1381)

2019/03/15 11:51:34 - Workflow - ... 10 more


#Kettle
#Pentaho
#PentahoDataIntegrationPDI
Sparkles Sparkles's profile image
Sparkles Sparkles posted 03-18-2019 12:18

Remove all steps. Then add first step only. See if it executes without error. Then add 1 more step, incrementally checking for errors. Is it possible to find which step (if any) causes this error?

Daniel Clark's profile image
Daniel Clark posted 03-19-2019 11:36

Thanks for the reply Sparkles Sparkles,

According to the log, it's the subjob name Workflow that's throwing the error. I'll give your suggestion a try.

Daniel Clark's profile image
Daniel Clark posted 03-19-2019 13:52

Sparkles Sparkles,

After removing all the steps, then adding steps back one by one, I still receive the same error I originally reported.

Sparkles Sparkles's profile image
Sparkles Sparkles posted 03-19-2019 18:27

When did the error appear? When you added the subjob "Workflow"? How is the path configured for this subjob? Is it possible to replace that subjob with an empty job that only logs some debug text to log?

Daniel Clark's profile image
Daniel Clark posted 03-20-2019 13:39

Sparkles Sparkles,

Yes, the error appeared when I added the subjob "Workflow". The path for the subjob is set to ${Internal.Entry.Current.Directory}/Workflow. I created another subjob named "Debug". It contains one transformation named debug_trans which contains a get variables step and a write to log step. I get the same error via kitchen, please see below:

2019/03/20 09:32:30 - Master_Job - Starting entry [Debug]

2019/03/20 09:32:30 - Debug - ERROR (version 8.2.0.0-342, build 8.2.0.0-342 from 2018-11-14 10.30.55 by buildguy) : Error running job entry 'job' :

2019/03/20 09:32:30 - Debug - ERROR (version 8.2.0.0-342, build 8.2.0.0-342 from 2018-11-14 10.30.55 by buildguy) : org.pentaho.di.core.exception.KettleException:

2019/03/20 09:32:30 - Debug - Unexpected error during job metadata load

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.run (Job.java:384)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:497)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:821)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.Job.execute (Job.java:680)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.entries.job.JobEntryJob.execute (JobEntryJob.java:667)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta (JobEntryJob.java:1345)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta (JobEntryJob.java:1381)

2019/03/20 09:32:30 - Debug -  at org.pentaho.di.job.entries.job.JobEntryJob.getJobMetaFromRepository (JobEntryJob.java:1353)

2019/03/20 09:32:30 - Debug -

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta(JobEntryJob.java:1421)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta(JobEntryJob.java:1345)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.entries.job.JobEntryJob.execute(JobEntryJob.java:667)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:680)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:821)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.execute(Job.java:497)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.Job.run(Job.java:384)

2019/03/20 09:32:30 - Debug - Caused by: java.lang.NullPointerException

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.entries.job.JobEntryJob.getJobMetaFromRepository(JobEntryJob.java:1353)

2019/03/20 09:32:30 - Debug -   at org.pentaho.di.job.entries.job.JobEntryJob.getJobMeta(JobEntryJob.java:1381)

2019/03/20 09:32:30 - Debug -   ... 10 more

Sparkles Sparkles's profile image
Sparkles Sparkles posted 03-21-2019 13:13

That sounds very good the way you describe it.

I would like to see if you're able to debug write to log the variable ${Internal.Entry.Current.Directory}. Is this used as the path for the other jobs/transformations too? I'm sorry I'm not able to provide more useful help here, I haven't seen your error before. My thought is maybe it is a problem resolving the actual file path to the (sub)job? Maybe Spoon somehow have some variables that for some reason is not properly set in Kitchen?

Try to debug write this variable on the top job level. There is a job step which can write and log variables directly. Another possibility, could you try and hard-code the file paths to your job and transformation files to test if that works?

Daniel Clark's profile image
Daniel Clark posted 04-03-2019 15:16

Sparkles Sparkles,

Thank you for the reply. I was able to work around this issue by changing the way I was calling the job via kitchen. I have a file-based repository. I originally was executing kitchen with the -file=<path to kjb file> option. After changing kitchen options to utilize -rep, -dir, and -job options, the error disappeared. However, I'm not sure why the original method stopped working.

Related Content