Hi,
I am testing Pentaho8 Schedules. I created 2 jobs to be executed every day and every our each. Somehow Schedule is not working properly due to the job that is scheduled to run every our is not working at all and the other one is getting a strange behavior.
If I run both jobs from Spoon, both works fine.
If I run both jobs using command line (kitchen.sh), both works fine.
how can I check the error?
Thanks in advance.
Hi,
I was checking the Pentaho logs and I found that every time that I try to run a job using the schedule, Pentaho is getting this error:
2018-01-13 23:41:40,775 ERROR [org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob] ActionAdapterQuartzJob.ERROR_0004 - Action "org.pentaho.platform.plugin.kettle.PdiAction" failed to run as a quartz job
org.quartz.JobExecutionException: org.pentaho.platform.api.action.ActionInvocationException: ActionInvoker.ERROR_0004 - Action "org.pentaho.platform.plugin.kettle.PdiAction" failed to execute [See nested exception: org.pentaho.platform.api.action.ActionInvocationException: ActionInvoker.ERROR_0004 - Action "org.pentaho.platform.plugin.kettle.PdiAction" failed to execute]
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.invokeAction(ActionAdapterQuartzJob.java:224)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.execute(ActionAdapterQuartzJob.java:76)
at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:199)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
Caused by: org.pentaho.platform.api.action.ActionInvocationException: ActionInvoker.ERROR_0004 - Action "org.pentaho.platform.plugin.kettle.PdiAction" failed to execute
at org.pentaho.platform.scheduler2.action.ActionRunner.call(ActionRunner.java:86)
at org.pentaho.platform.scheduler2.action.ActionRunner.call(ActionRunner.java:52)
at org.pentaho.platform.engine.security.SecurityHelper.runAsUser(SecurityHelper.java:175)
at org.pentaho.platform.engine.security.SecurityHelper.runAsUser(SecurityHelper.java:164)
at org.pentaho.platform.scheduler2.action.DefaultActionInvoker.invokeActionImpl(DefaultActionInvoker.java:133)
at org.pentaho.platform.scheduler2.action.DefaultActionInvoker.invokeAction(DefaultActionInvoker.java:77)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.invokeAction(ActionAdapterQuartzJob.java:175)
... 4 more
Caused by: java.lang.reflect.InvocationTargetException: BeanUtil.ERROR_0001 - Failed to set bean property "org.pentaho.platform.plugin.kettle.PdiAction.parameters" (of type "parameters") with a value (of type "java.util.Map").
at org.pentaho.platform.util.beans.BeanUtil$EagerFailingCallback.failedToSetValue(BeanUtil.java:316)
at org.pentaho.platform.util.beans.ActionHarness$VarArgsWrapperCallback.failedToSetValue(ActionHarness.java:94)
at org.pentaho.platform.util.beans.BeanUtil.setValue(BeanUtil.java:263)
at org.pentaho.platform.util.beans.ActionHarness.setValue(ActionHarness.java:70)
at org.pentaho.platform.util.beans.BeanUtil.setValue(BeanUtil.java:183)
at org.pentaho.platform.util.beans.BeanUtil.setValues(BeanUtil.java:294)
at org.pentaho.platform.scheduler2.action.ActionRunner.callImpl(ActionRunner.java:107)
at org.pentaho.platform.scheduler2.action.ActionRunner.call(ActionRunner.java:75)
Now I am trying to figure out what is going on.
I am using LDAP as authentication system.
First problem resolved. The Job is not working due to I am connecting to MariaDB and jar plugin is too old on Pentaho8. I updated the plugin from 5.1.17 to 5.1.42 and all worked fine with scheduler. Also worked OK using 5.1.23.
Now problem is only PentanoAdmin (I am using LDAP and admin was replaced by PentahoAdmin) can run successfully schedules. I tried to run a job scheduled by other user into PentahoAdministrators LDAP group and it failed. The error was the same as before, so it means that initially Pentaho is checking if the user is capable to run schedule jobs and then it will try to run it.
Finally, all is working fine:
Issues detected:
- Quartz DB was not installed propperly. Once installation was OK, Schedule worked fine too.
Hi Manuel,
What was wrong with your Quartz installation? I've got exactly the same error stack trace and don't see any problems in my Quartz DB.
Hi,
We reinstalled Quartz DB using the right access (user/password). We used a old Quartz DB from a previos installation.
Finally, all is working fine:
Issues detected:
- Quartz DB was not installed propperly. Once installation was OK, Schedule worked fine too.