Also If I execute this command

*hadoop fs -ls workflows/oozie-examples/oozie-examples/job.properties*

I get the output

*Found 1 items*
*-rw-rw-rw-   3 cloudera cloudera        165 2013-11-22 05:59
workflows/oozie-examples/oozie-examples/job.properties*




On 22 November 2013 19:38, Mahin Khan <[email protected]> wrote:

> here is the output:
>
> *Error: E0901 : E0901: Namenode [debian:8020] not allowed, not in Oozies
> whitelist*
>
>
>
>
> On 22 November 2013 19:21, Richard Ross <[email protected]>wrote:
>
>> Please execute this following command from the oozie-examples dir, and
>> post the entire output:
>>
>> ls ./job.properties;oozie job -config ./job.properties -run
>>
>> Thanks,
>> Richard.
>>
>> On Nov 22, 2013, at 9:04 AMEST, Mahin Khan wrote:
>>
>> > Thanks a lot for the valuable info Richard. I still can't solve the
>> problem.
>> > is there any chance that there is something wrong with the parameters I
>> > give in config-default.
>> > Mahin
>> >
>> >
>> > On 22 November 2013 18:26, Richard Ross <[email protected]>
>> wrote:
>> >
>> >> If you are executing from oozie-examples, then change your command to:
>> >>
>> >> oozie job -config ./job.properties -run
>> >>
>> >> If you are executing from the directory containing oozie-examples, then
>> >> change your command to:
>> >>
>> >> oozie job -config ./oozie-examples/job.properties -run
>> >>
>> >> The argument to -config must be a path, relative or absolute, to the
>> >> job.properties file on the local filesystem. Put another way, wherever
>> you
>> >> are executing the oozie run command, the argument to -config should
>> also
>> >> show the properties file when you do an 'ls':
>> >>
>> >> ls <path_to_properties_file>;
>> >> oozie job -config <path_to_properties_file> -run
>> >>
>> >> Richard.
>> >>
>> >> On Nov 22, 2013, at 8:13 AMEST, Mahin Khan wrote:
>> >>
>> >>> my current directory is the target folder. the command
>> >>>
>> >>> *ls /oozie-examples/job.properties*
>> >>>
>> >>>
>> >>> gives the result:
>> >>>
>> >>> *ls: cannot access /oozie-examples/job.properties: No such file or
>> >>> directory*
>> >>>
>> >>>
>> >>> but if I change the current directory and then list all the files it
>> >> shows
>> >>> job.properties to be present in the directory
>> >>>
>> >>> *cd oozie-examples*
>> >>> *ls*
>> >>>
>> >>>
>> >>>
>> >>> On 22 November 2013 17:33, Richard Ross <[email protected]>
>> >> wrote:
>> >>>
>> >>>> Can you verify that the properties file can be found on the local
>> >>>> filesystem by executing:
>> >>>>
>> >>>> ls /oozie-examples/job.properties
>> >>>>
>> >>>> It wasn't clear to me that the location on the local filesystem
>> matches
>> >>>> the location in the command:
>> >>>>
>> >>>> oozie job -config /oozie-examples/job.properties -run
>> >>>>
>> >>>> which is key here.
>> >>>>
>> >>>> Richard.
>> >>>>
>> >>>> On Nov 22, 2013, at 7:19 AMEST, Mahin Khan wrote:
>> >>>>
>> >>>>> Yes, I have it on local file system too and when I upload it on hdfs
>> >>>> using
>> >>>>> command
>> >>>>>
>> >>>>> hadoop fs -put oozie-examples /workflows/oozie-examples
>> >>>>>
>> >>>>> I can also see it using file browser at
>> >>>>>
>> >>>>> /user/cloudera/workflows/oozie-examples/job.properties
>> >>>>>
>> >>>>>
>> >>>>> On 22 November 2013 11:43, Giridhar Addepalli <
>> [email protected]
>> >>>>> wrote:
>> >>>>>
>> >>>>>> Hi Mahir,
>> >>>>>>
>> >>>>>> do you have your job.properties at /oozie-examples/job.properties
>> on
>> >>>> your
>> >>>>>> local filesystem ?
>> >>>>>> From the exception it looks like job.properties is not present at
>> path
>> >>>> you
>> >>>>>> mentioned on your oozie job command.
>> >>>>>>
>> >>>>>> Thanks,
>> >>>>>> Giridhar.
>> >>>>>>
>> >>>>>>
>> >>>>>> On Fri, Nov 22, 2013 at 11:22 AM, Mahin Khan <[email protected]
>> >
>> >>>> wrote:
>> >>>>>>
>> >>>>>>> Hi, I am new on oozie and hadoop. i am using cdh4 on cloudera
>> virtul
>> >>>>>>> machine single node. i am trying to run oozie project following
>> below
>> >>>>>> link
>> >>>>>>>
>> >>>>>>> https://github.com/jrkinley/oozie-examples/blob/master/README.md
>> >>>>>>>
>> >>>>>>> this is my *job.properties* file
>> >>>>>>>
>> >>>>>>> nameNode=${hadoop.name.node}
>> >>>>>>> jobTracker=${hadoop.job.tracker}
>> >>>>>>>
>> >>>>>>> queueName=default
>> >>>>>>> oozie.use.system.libpath=true
>> >>>>>>>
>> >>>>>>> oozie.wf.application.path=${nameNode}/workflows/oozie-examples
>> >>>>>>>
>> >>>>>>> this is my *config-default.xml*
>> >>>>>>> <!-- Default values for the workflow job parameters -->
>> >>>>>>> <configuration>
>> >>>>>>>      <property>
>> >>>>>>>              <name>jobTracker</name>
>> >>>>>>>              <value>localhost.localdomain:8021</value>
>> >>>>>>>      </property>
>> >>>>>>>      <property>
>> >>>>>>>              <name>nameNode</name>
>> >>>>>>>              <value>hdfs://localhost.localdomain:8020</value>
>> >>>>>>>      </property>
>> >>>>>>>      <property>
>> >>>>>>>              <name>queueName</name>
>> >>>>>>>              <value>default</value>
>> >>>>>>>      </property>
>> >>>>>>> </configuration>
>> >>>>>>>
>> >>>>>>> my hdfs directory structure is
>> >>>>>>>
>> >>>>>>> /workflows/oozie-example/job.properties
>> >>>>>>>
>> >>>>>>> /workflows/oozie-example/config-default.xml
>> >>>>>>> ....
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> *i am running job by this command *
>> >>>>>>> oozie job -config /oozie-examples/job.properties -run
>> >>>>>>>
>> >>>>>>> *this give me this error*
>> >>>>>>> .io.IOException: configuration file
>> [/oozie-examples/job.properties]
>> >>>> not
>> >>>>>>> found
>> >>>>>>>      at
>> >>>>>>> org.apache.oozie.cli.OozieCLI.getConfiguration(OozieCLI.java:641)
>> >>>>>>>      at
>> org.apache.oozie.cli.OozieCLI.jobCommand(OozieCLI.java:795)
>> >>>>>>>      at
>> >>>>>> org.apache.oozie.cli.OozieCLI.processCommand(OozieCLI.java:512)
>> >>>>>>>      at org.apache.oozie.cli.OozieCLI.run(OozieCLI.java:485)
>> >>>>>>>      at org.apache.oozie.cli.OozieCLI.main(OozieCLI.java:182)
>> >>>>>>> configuration file [/oozie-examples/job.properties] not found
>> >>>>>>>
>> >>>>>>> Kindly help me out any help would be highly appreciated
>> >>>>>>>
>> >>>>>>
>> >>>>
>> >>>>
>> >>
>> >>
>>
>>
>

Reply via email to