> user "abc" did start coordinator and user "xyz" tries to kill it. > "xyz" is not allowed to kill coordinators submitted by "abc".
OK, that's good to know, but in this case it's same user both times. This user can't kill his own coordinator jobs. > Which interface you are talking about? The Oozie Web Console, running on port 11000 (on my Hortonworks HDP system). Screen shot attached. [image: Inline image 1] You'll see that there are two eternally running coordinator jobs that I have no idea how to kill. Thanks, Michael On Mon, Oct 21, 2013 at 3:23 PM, Serega Sheypak <[email protected]>wrote: > > > >I also see no way to kill the Coordinator job from the Oozie web > interface? > Which interface you are talking about? > > > 2013/10/21 <[email protected]> > > > After launching a coordinator job that had flawed settings and will never > > run, I tried to kill it from the command line, but I'm getting an error: > > > > $ oozie job -kill 0000115-131007154641248-oozie-oozi-C; > > Error: E0509 : E0509: User [?] not authorized for Coord job > > [0000115-131007154641248-oozie-oozi-C] > > > > > > I googled this and found nothing. > > > > I also see no way to kill the Coordinator job from the Oozie web > interface? > > How do I kill it? > > > > -Michael > > >
