Support Questions
Find answers, ask questions, and share your expertise

Oozie E1005 issue at Coordinator

Explorer

We scheduled the Oozie job with three xml's

1.Bundle

2.Coordinator

3.Workflow

The very first day it was running fine but the next day bundle is in running state to calling the coordinator but coordinator unable to calling the workflow. We seen the error code in the UI is E1005(Could not read the coordinator job configuration read from DB). Please let me know the exact issue and what property we could change in configuration files. Only we may able to seeing the below logs for this error.

Thanks for advance.

2015-08-03 06:43:43,820  INFO CoordSubmitXCommand:543 - SERVER[sandbox.hortonworks.com] USER[root] GROUP[-] TOKEN[] APP[camus] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[-] ENDED Coordinator Submit jobId=0000000-150803063131195-oozie-oozi-C
2015-08-03 06:43:43,935  INFO CoordMaterializeTransitionXCommand:543 - SERVER[sandbox.hortonworks.com] USER[root] GROUP[-] TOKEN[] APP[camus] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[-] materialize actions for tz=Coordinated Universal Time,
 start=Thu Jul 30 11:40:00 UTC 2015, end=Thu Jul 30 15:40:00 UTC 2015,
 timeUnit 12,
 frequency :20:MINUTE,
 lastActionNumber 0
2015-08-03 06:43:43,971  INFO CoordMaterializeTransitionXCommand:543 - SERVER[sandbox.hortonworks.com] USER[root] GROUP[-] TOKEN[] APP[camus] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[-] [0000000-150803063131195-oozie-oozi-C]: Update status from PREP to RUNNING
2015-08-03 06:43:44,113  INFO CoordActionInputCheckXCommand:543 - SERVER[sandbox.hortonworks.com] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[0000000-150803063131195-oozie-oozi-C@1] [0000000-150803063131195-oozie-oozi-C@1]::CoordActionInputCheck:: Missing deps: 
2015-08-03 06:43:44,209  INFO CoordActionNotificationXCommand:543 - SERVER[sandbox.hortonworks.com] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[0000000-150803063131195-oozie-oozi-C@1] STARTED Coordinator Notification actionId=0000000-150803063131195-oozie-oozi-C@1 : WAITING
...
2015-08-03 06:43:44,267  INFO CoordActionNotificationXCommand:543 - SERVER[sandbox.hortonworks.com] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[0000000-150803063131195-oozie-oozi-C@12] No Notification URL is defined. Therefore nothing to notify for job 0000000-150803063131195-oozie-oozi-C action ID 0000000-150803063131195-oozie-oozi-C@12
2015-08-03 06:43:44,268  INFO CoordActionNotificationXCommand:543 - SERVER[sandbox.hortonworks.com] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[0000000-150803063131195-oozie-oozi-C@12] ENDED Coordinator Notification actionId=0000000-150803063131195-oozie-oozi-C@12
2015-08-03 06:43:44,433  WARN ParameterVerifier:546 - SERVER[sandbox.hortonworks.com] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[0000000-150803063131195-oozie-oozi-C@1] The application does not define formal parameters in its XML definition
...
3 REPLIES 3

Re: Oozie E1005 issue at Coordinator

Explorer

2015-08-0306:43:44,209 INFO CoordActionNotificationXCommand:543- SERVER[sandbox.hortonworks.com] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000000-150803063131195-oozie-oozi-C] ACTION[0000000-150803063131195-oozie-oozi-C@1] STARTED CoordinatorNotification actionId=0000000-150803063131195-oozie-oozi-C@1 : WAITING

The first action from the coordinator is in the waiting state. Are you sure that, it execute for the first coord action and did not work.

You need to provide more logs related to the issue. Also E1005 should have some more message than what you provided in the post.

Re: Oozie E1005 issue at Coordinator

Explorer

Hi Abhishek,

Thanks for your valuable replay here. The problem is in my cluster oozie not configured properly after restarting the oozie server things are working fine based an expectations. We are getting the above log only for that issue not printed much oozie.

Thanks,

Viswanatha Reddy

Re: Oozie E1005 issue at Coordinator

New Contributor

Hi Viswa,

 

I am also facing the same issue. Doesn't look anything wrong with my oozie cluster configuration. Can you please let me know, what changes you made to your cluster configuration to fix this?