Re: How to resolve--- Unauthorized request to start container. This token is expired.

Duh. try running ntpdate as root (sudo). On Fri, Feb 27, 2015 at 11:39 PM, daemeon reiydelle daeme...@gmail.com wrote: try ntpdate -b -p8 whichever server However, you flat should not be seeing 13 minutes. Something wrong. Suggest nptdate -d -b -p8 whichever server and look at the results.

Re: How to resolve--- Unauthorized request to start container. This token is expired.

try ntpdate -b -p8 whichever server However, you flat should not be seeing 13 minutes. Something wrong. Suggest nptdate -d -b -p8 whichever server and look at the results. On Thu, Feb 26, 2015 at 10:54 AM, Jan van Bemmelen j...@tokyoeye.net wrote: Hi Tariq, So this is not really an Hadoop

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Dear Jan, I changed the data of the node by sudo date *newdatetimestring* Thanks for your help Regards, On Thu, Feb 26, 2015 at 6:31 PM, Jan van Bemmelen j...@tokyoeye.net wrote: Hi Tariq, You seem to be using debian or ubuntu. The documentation here will guide you through setting up

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Thanks Jan. I did the follwoing: 1) Manually set the timezone of all the nodes using sudo dpkg-reconfigure tzdata 2) Re-booted the nodes Still having the same exception. How can I configure NTP? Regards, Tariq On Thu, Feb 26, 2015 at 5:33 PM, Jan van Bemmelen j...@tokyoeye.net wrote:

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Could you check for any time differences between your servers? If so, please install and run NTP, and retry your job. Regards, Jan On 26 Feb 2015, at 17:57, tesm...@gmail.com wrote: I am getting Unauthorized request to start container. This token is expired. How to resovle it. The

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Hi Tariq, You seem to be using debian or ubuntu. The documentation here will guide you through setting up ntp: http://www.cyberciti.biz/faq/debian-ubuntu-linux-install-ntpd/ http://www.cyberciti.biz/faq/debian-ubuntu-linux-install-ntpd/ . When you have finished these steps you can check the

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Please take a look at: http://www.tldp.org/LDP/sag/html/basic-ntp-config.html On Thu, Feb 26, 2015 at 10:19 AM, tesm...@gmail.com tesm...@gmail.com wrote: Thanks Jan. I did the follwoing: 1) Manually set the timezone of all the nodes using sudo dpkg-reconfigure tzdata 2) Re-booted the

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Thanks Jan, I followed the link and re-booted the node. Still no success. Time on this node is about 13 minutes behind the other nodes. Any otehr suggestion please This node is workig as my namenode On Thu, Feb 26, 2015 at 6:31 PM, Jan van Bemmelen j...@tokyoeye.net wrote: Hi Tariq,

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Hi Tariq, So this is not really an Hadoop issue, but more a general Linux time question. Here’s how to manually get the time synchronised: /etc/init.d/ntp stop (or whatever way you prefer to kill ntpd) ntpdate 0.centos.pool.ntp.org http://0.centos.pool.ntp.org/ This should sync time with the

Re: How to resolve--- Unauthorized request to start container. This token is expired.

Hey, Tariq: Definitely this is the time problem. But if this is not the production cluster, and to unblock your progress, you could set yarn.resourcemanager.rm.container-allocation.expiry-interval-ms a larger number in your yarn-site.xml. The current default number is 60 which is