> Which OS you use? I'm using a CentOS VMWare VM running Hortonworks HDP 1.3 in pseudo-distributed mode (single node). Oozie version: 3.3.2.1.3.2.0-111
> Looks like some kind of impersonalization has happened. Your user is undefined? I looked in the logs: When I run oozie job -run xyz it runs as my user (root). When I run oozie job -kill it comes up as null user: oozie-audit.log:2013-10-21 16:26:39,546 INFO oozieaudit:539 - USER [null], GROUP [null], APP [null], JOBID [null], OPERATION [kill], PARAMETER [0000115-131 007154641248-oozie-oozi-C], STATUS [FAILED], HTTPCODE [401], ERRORCODE [E0509], ERRORMESSAGE [E0509: User [?] not authorized for Coord job [0000115-13100715 4641248-oozie-oozi-C]] oozie.log:2013-10-21 16:26:39,546 WARN V1JobServlet:542 - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] URL[PUT http://localhost:11000/oozie/v1/job/000 0115-131007154641248-oozie-oozi-C?action=kill] error[E0509], E0509: User [?] not authorized for Coord job [0000115-131007154641248-oozie-oozi-C] oozie.log:org.apache.oozie.servlet.XServletException: E0509: User [?] not authorized for Coord job [0000115-131007154641248-oozie-oozi-C] oozie.log:Caused by: org.apache.oozie.service.AuthorizationException: E0509: User [?] not authorized for Coord job [0000115-131007154641248-oozie-oozi-C] > Where is your "submitter" is located? I submit and kill from the command line of this one machine. > Where is oozie server running? Same machine - localhost on the VM. > Where is coordinator "killer" located? Same machine - localhost on the VM. My proxy user settings are: michael-hadoop-5 oozie$ grep -C 2 oozie /etc/hadoop/conf/core-site.xml <property> <name>hadoop.proxyuser.oozie.groups</name> <value>*</value> </property> -- <property> <name>hadoop.proxyuser.oozie.hosts</name> <value>michael-hadoop-5.tsh.thomson.com</value> </property> I have other aspects of oozie working now, but this is the next impediment to solve. -Michael On Mon, Oct 21, 2013 at 3:57 PM, Serega Sheypak <[email protected]>wrote: > 2013/10/21 <[email protected]> > > > > 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. > > > >Error: E0509 : E0509: User [?] not authorized for Coord job > Ok, good to know that you use the same user. See "User [?]" in your log. > Looks like some kind of impersonalization has happened. Your user is > undefined? > Where is your "submitter" is located? > Where is oozie server running? > Where is coordinator "killer" located? > Which OS you use? > > > > > Which interface you are talking about? > > > > The Oozie Web Console, running on port 11000 (on my Hortonworks HDP > > system). Screen shot attached. > > > It;s not the best tool to monitor oozie. I suggest you to install fresh HUE > and you'll get a lot of useful stuff there. > > > > > [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 > >> > > >> > > > > >
