Hi Brian,

I am not seeing this trouble on a similar version locally:

harsh@~]$ hadoop fs -ls
drwxr-xr-x   - harsh harsh          0 2012-09-28 04:21 outfoo
[harsh@~]$ hadoop fs -chmod 1777 outfoo
[harsh@~]$ hadoop fs -chmod -R 1777 outfoo
[harsh@~]$ hadoop fs -chmod -R +t outfoo
[harsh@~]$

What is your JVM/Java version? There's one known issue with Java 7
(vs. 6) that may break things in the regex areas (I recall Oozie
facing a similar issue with one of the Patterns it was using). Make
sure you use Java 6 (1.6) for now, until there's been more testing
with Java 7 for Hadoop/etc.

On Wed, Nov 7, 2012 at 11:27 PM, Brian Derickson <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> When setting up the namenode, some of the commands that we run are:
> hadoop fs -mkdir /tmp
> hadoop fs -chmod -R 1777 /tmp
>
> This has worked for previous CDH releases of Hadoop.
>
> We recently upgraded our test cluster to CDH 4.1 and the chmod no longer
> works.
>
> sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
> chmod: chmod : mode '1777' does not match the expected pattern.
>
> sudo -u hdfs hadoop fs -chmod -R +t /tmp
> chmod: chmod : mode '+t' does not match the expected pattern.
>
> This disagrees with the docs here:
> https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7
>
> Has anyone else encountered this? Let me know if you need more information,
> and thanks for your time.
>

--
Harsh J

Pls ask Cloudera lists...

On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:

> Hey all,
>
> When setting up the namenode, some of the commands that we run are:
> hadoop fs -mkdir /tmp
> hadoop fs -chmod -R 1777 /tmp
>
> This has worked for previous CDH releases of Hadoop.
>
> We recently upgraded our test cluster to CDH 4.1 and the chmod no longer works.
>
> sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
> chmod: chmod : mode '1777' does not match the expected pattern.
>
> sudo -u hdfs hadoop fs -chmod -R +t /tmp
> chmod: chmod : mode '+t' does not match the expected pattern.
>
> This disagrees with the docs here: https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7
>
> Has anyone else encountered this? Let me know if you need more information, and thanks for your time.
>

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Have you tried hadoop fs -chmod a+rwx /tmp
From: Arun C Murthy [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 07, 2012 3:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Sticky Bit Problem (CDH4.1)

Pls ask Cloudera lists...

On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:
Hey all,

When setting up the namenode, some of the commands that we run are:
hadoop fs -mkdir /tmp
hadoop fs -chmod -R 1777 /tmp

This has worked for previous CDH releases of Hadoop.

We recently upgraded our test cluster to CDH 4.1 and the chmod no longer works.

sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
chmod: chmod : mode '1777' does not match the expected pattern.

sudo -u hdfs hadoop fs -chmod -R +t /tmp
chmod: chmod : mode '+t' does not match the expected pattern.

This disagrees with the docs here: https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7

Has anyone else encountered this? Let me know if you need more information, and thanks for your time.

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

NOTICE: This e-mail message and any attachments are confidential, subject to copyright and may be privileged. Any unauthorized use, copying or disclosure is prohibited. If you are not the intended recipient, please delete and contact the sender immediately. Please consider the environment before printing this e-mail. AVIS : le pr?sent courriel et toute pi?ce jointe qui l'accompagne sont confidentiels, prot?g?s par le droit d'auteur et peuvent ?tre couverts par le secret professionnel. Toute utilisation, copie ou divulgation non autoris?e est interdite. Si vous n'?tes pas le destinataire pr?vu de ce courriel, supprimez-le et contactez imm?diatement l'exp?diteur. Veuillez penser ? l'environnement avant d'imprimer le pr?sent courriel

This is resolved, now. We were having some problems yesterday with the
Puppet infrastructure we use to manage our cluster that resulted in daemons
being installed on hosts they shouldn't be on (datanode/tasktracker running
on master nodes, for example) that I wasn't aware of when I made my
original post. Once we figured that out, this sticky bit problem went away.

I wish I could be more specific just so anyone that finds this thread in
the archives could have something useful...

Thanks for your time!
On Wed, Nov 7, 2012 at 2:44 PM, Kartashov, Andy <[EMAIL PROTECTED]>wrote:

>  Have you tried hadoop fs -chmod a+rwx /tmp
>
>
>
>
>
> *From:* Arun C Murthy [mailto:[EMAIL PROTECTED]]
> *Sent:* Wednesday, November 07, 2012 3:11 PM
> *To:* [EMAIL PROTECTED]
> *Subject:* Re: Sticky Bit Problem (CDH4.1)
>
>
>
> Pls ask Cloudera lists...
>
>
>
> On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:
>
>
>
>  Hey all,
>
> When setting up the namenode, some of the commands that we run are:
> hadoop fs -mkdir /tmp
> hadoop fs -chmod -R 1777 /tmp
>
> This has worked for previous CDH releases of Hadoop.
>
> We recently upgraded our test cluster to CDH 4.1 and the chmod no longer
> works.
>
> sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
> chmod: chmod : mode '1777' does not match the expected pattern.
>
> sudo -u hdfs hadoop fs -chmod -R +t /tmp
> chmod: chmod : mode '+t' does not match the expected pattern.
>
> This disagrees with the docs here:
> https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7
>
> Has anyone else encountered this? Let me know if you need more
> information, and thanks for your time.
>
>
>
> --
>
> Arun C. Murthy
>
> Hortonworks Inc.
> http://hortonworks.com/
>
>
>  NOTICE: This e-mail message and any attachments are confidential,
> subject to copyright and may be privileged. Any unauthorized use, copying
> or disclosure is prohibited. If you are not the intended recipient, please
> delete and contact the sender immediately. Please consider the environment
> before printing this e-mail. AVIS : le présent courriel et toute pièce
> jointe qui l'accompagne sont confidentiels, protégés par le droit d'auteur
> et peuvent être couverts par le secret professionnel. Toute utilisation,
> copie ou divulgation non autorisée est interdite. Si vous n'êtes pas le
> destinataire prévu de ce courriel, supprimez-le et contactez immédiatement
> l'expéditeur. Veuillez penser à l'environnement avant d'imprimer le présent
> courriel
>

Glad to know it is resolved for you. Highly odd error - I haven't been
able to reproduce with JDK 7u3 either, so am unsure of what caused the
parser to fail. Probably mixed versions of jars by any chance?

On Thu, Nov 8, 2012 at 10:45 PM, Brian Derickson <[EMAIL PROTECTED]> wrote:
> This is resolved, now. We were having some problems yesterday with the
> Puppet infrastructure we use to manage our cluster that resulted in daemons
> being installed on hosts they shouldn't be on (datanode/tasktracker running
> on master nodes, for example) that I wasn't aware of when I made my original
> post. Once we figured that out, this sticky bit problem went away.
>
> I wish I could be more specific just so anyone that finds this thread in the
> archives could have something useful...
>
> Thanks for your time!
>
>
>
> On Wed, Nov 7, 2012 at 2:44 PM, Kartashov, Andy <[EMAIL PROTECTED]>
> wrote:
>>
>> Have you tried hadoop fs -chmod a+rwx /tmp
>>
>>
>>
>>
>>
>> From: Arun C Murthy [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, November 07, 2012 3:11 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: Sticky Bit Problem (CDH4.1)
>>
>>
>>
>> Pls ask Cloudera lists...
>>
>>
>>
>> On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:
>>
>>
>>
>> Hey all,
>>
>> When setting up the namenode, some of the commands that we run are:
>> hadoop fs -mkdir /tmp
>> hadoop fs -chmod -R 1777 /tmp
>>
>> This has worked for previous CDH releases of Hadoop.
>>
>> We recently upgraded our test cluster to CDH 4.1 and the chmod no longer
>> works.
>>
>> sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
>> chmod: chmod : mode '1777' does not match the expected pattern.
>>
>> sudo -u hdfs hadoop fs -chmod -R +t /tmp
>> chmod: chmod : mode '+t' does not match the expected pattern.
>>
>> This disagrees with the docs here:
>> https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7
>>
>> Has anyone else encountered this? Let me know if you need more
>> information, and thanks for your time.
>>
>>
>>
>> --
>>
>> Arun C. Murthy
>>
>> Hortonworks Inc.
>> http://hortonworks.com/
>>
>>
>>
>> NOTICE: This e-mail message and any attachments are confidential, subject
>> to copyright and may be privileged. Any unauthorized use, copying or
>> disclosure is prohibited. If you are not the intended recipient, please
>> delete and contact the sender immediately. Please consider the environment
>> before printing this e-mail. AVIS : le présent courriel et toute pièce
>> jointe qui l'accompagne sont confidentiels, protégés par le droit d'auteur
>> et peuvent être couverts par le secret professionnel. Toute utilisation,
>> copie ou divulgation non autorisée est interdite. Si vous n'êtes pas le
>> destinataire prévu de ce courriel, supprimez-le et contactez immédiatement
>> l'expéditeur. Veuillez penser à l'environnement avant d'imprimer le présent
>> courriel
>
>

--
Harsh J

Very possible it's a mixed version thing, though I'm not sure where in the
mess we created it would be. :)

As far as I can tell, we were never using Java version 7.

Most of these complications arose when we attempted to upgrade to CDH 4.1
via Puppet. Somewhere along the line things were installed on hosts where
they shouldn't have been. It's also possible there was a mix of versions
installed. (CDH4.0 and CDH4.1)

We also had some problems with Avro around the same time... Since version
1.7.1 is supposed to be used with CDH4, I was trying to remove the 1.5.4
jar that comes with the distribution and put 1.7.1 jars in place instead.
This particular task wasn't a priority until I forgot to specify a 1.7.1
jar when running a job and it started using the 1.5.4 jar.

I discovered during this work that putting the avro-tools jar in
/usr/lib/hadoop/lib causes the jobtracker to stop working. It fails
immediately after launch with this error: "java.lang.NoSuchMethodError:
org.apache.hadoop.ipc.RPC.getServer". I can reproduce this and provide a
more detailed stack trace or whatever if needed. There may have been some
other fallout from this that I'm not aware of.

I think that's it. Like I said, it was a bit of a mess for awhile but all
seems well now. :)
On Thu, Nov 8, 2012 at 11:26 PM, Harsh J <[EMAIL PROTECTED]> wrote:

> Glad to know it is resolved for you. Highly odd error - I haven't been
> able to reproduce with JDK 7u3 either, so am unsure of what caused the
> parser to fail. Probably mixed versions of jars by any chance?
>
> On Thu, Nov 8, 2012 at 10:45 PM, Brian Derickson <[EMAIL PROTECTED]>
> wrote:
> > This is resolved, now. We were having some problems yesterday with the
> > Puppet infrastructure we use to manage our cluster that resulted in
> daemons
> > being installed on hosts they shouldn't be on (datanode/tasktracker
> running
> > on master nodes, for example) that I wasn't aware of when I made my
> original
> > post. Once we figured that out, this sticky bit problem went away.
> >
> > I wish I could be more specific just so anyone that finds this thread in
> the
> > archives could have something useful...
> >
> > Thanks for your time!
> >
> >
> >
> > On Wed, Nov 7, 2012 at 2:44 PM, Kartashov, Andy <[EMAIL PROTECTED]>
> > wrote:
> >>
> >> Have you tried hadoop fs -chmod a+rwx /tmp
> >>
> >>
> >>
> >>
> >>
> >> From: Arun C Murthy [mailto:[EMAIL PROTECTED]]
> >> Sent: Wednesday, November 07, 2012 3:11 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: Sticky Bit Problem (CDH4.1)
> >>
> >>
> >>
> >> Pls ask Cloudera lists...
> >>
> >>
> >>
> >> On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:
> >>
> >>
> >>
> >> Hey all,
> >>
> >> When setting up the namenode, some of the commands that we run are:
> >> hadoop fs -mkdir /tmp
> >> hadoop fs -chmod -R 1777 /tmp
> >>
> >> This has worked for previous CDH releases of Hadoop.
> >>
> >> We recently upgraded our test cluster to CDH 4.1 and the chmod no longer
> >> works.
> >>
> >> sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
> >> chmod: chmod : mode '1777' does not match the expected pattern.
> >>
> >> sudo -u hdfs hadoop fs -chmod -R +t /tmp
> >> chmod: chmod : mode '+t' does not match the expected pattern.
> >>
> >> This disagrees with the docs here:
> >>
> https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7
> >>
> >> Has anyone else encountered this? Let me know if you need more
> >> information, and thanks for your time.
> >>
> >>
> >>
> >> --
> >>
> >> Arun C. Murthy
> >>
> >> Hortonworks Inc.
> >> http://hortonworks.com/
> >>
> >>
> >>
> >> NOTICE: This e-mail message and any attachments are confidential,
> subject
> >> to copyright and may be privileged. Any unauthorized use, copying or
> >> disclosure is prohibited. If you are not the intended recipient, please
> >> delete and contact the sender immediately. Please consider the
> environment
> >> before printing this e-mail. AVIS : le présent courriel et toute pièce

Thanks for following up Brian. I'll try to reproduce this out with
some more version hints from your post just in case we aren't missing
anything bad.

Also, in future, if your problem feels CDH-specific, please do mail
the [EMAIL PROTECTED] lists instead of the Apache ones (Groups:
https://groups.google.com/a/cloudera.org/forum/?fromgroups=#!forum/cdh-user).

On Fri, Nov 9, 2012 at 10:57 PM, Brian Derickson <[EMAIL PROTECTED]> wrote:
> Very possible it's a mixed version thing, though I'm not sure where in the
> mess we created it would be. :)
>
> As far as I can tell, we were never using Java version 7.
>
> Most of these complications arose when we attempted to upgrade to CDH 4.1
> via Puppet. Somewhere along the line things were installed on hosts where
> they shouldn't have been. It's also possible there was a mix of versions
> installed. (CDH4.0 and CDH4.1)
>
> We also had some problems with Avro around the same time... Since version
> 1.7.1 is supposed to be used with CDH4, I was trying to remove the 1.5.4 jar
> that comes with the distribution and put 1.7.1 jars in place instead. This
> particular task wasn't a priority until I forgot to specify a 1.7.1 jar when
> running a job and it started using the 1.5.4 jar.
>
> I discovered during this work that putting the avro-tools jar in
> /usr/lib/hadoop/lib causes the jobtracker to stop working. It fails
> immediately after launch with this error: "java.lang.NoSuchMethodError:
> org.apache.hadoop.ipc.RPC.getServer". I can reproduce this and provide a
> more detailed stack trace or whatever if needed. There may have been some
> other fallout from this that I'm not aware of.
>
> I think that's it. Like I said, it was a bit of a mess for awhile but all
> seems well now. :)
>
>
>
>
>
> On Thu, Nov 8, 2012 at 11:26 PM, Harsh J <[EMAIL PROTECTED]> wrote:
>>
>> Glad to know it is resolved for you. Highly odd error - I haven't been
>> able to reproduce with JDK 7u3 either, so am unsure of what caused the
>> parser to fail. Probably mixed versions of jars by any chance?
>>
>> On Thu, Nov 8, 2012 at 10:45 PM, Brian Derickson <[EMAIL PROTECTED]>
>> wrote:
>> > This is resolved, now. We were having some problems yesterday with the
>> > Puppet infrastructure we use to manage our cluster that resulted in
>> > daemons
>> > being installed on hosts they shouldn't be on (datanode/tasktracker
>> > running
>> > on master nodes, for example) that I wasn't aware of when I made my
>> > original
>> > post. Once we figured that out, this sticky bit problem went away.
>> >
>> > I wish I could be more specific just so anyone that finds this thread in
>> > the
>> > archives could have something useful...
>> >
>> > Thanks for your time!
>> >
>> >
>> >
>> > On Wed, Nov 7, 2012 at 2:44 PM, Kartashov, Andy <[EMAIL PROTECTED]>
>> > wrote:
>> >>
>> >> Have you tried hadoop fs -chmod a+rwx /tmp
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> From: Arun C Murthy [mailto:[EMAIL PROTECTED]]
>> >> Sent: Wednesday, November 07, 2012 3:11 PM
>> >> To: [EMAIL PROTECTED]
>> >> Subject: Re: Sticky Bit Problem (CDH4.1)
>> >>
>> >>
>> >>
>> >> Pls ask Cloudera lists...
>> >>
>> >>
>> >>
>> >> On Nov 7, 2012, at 9:57 AM, Brian Derickson wrote:
>> >>
>> >>
>> >>
>> >> Hey all,
>> >>
>> >> When setting up the namenode, some of the commands that we run are:
>> >> hadoop fs -mkdir /tmp
>> >> hadoop fs -chmod -R 1777 /tmp
>> >>
>> >> This has worked for previous CDH releases of Hadoop.
>> >>
>> >> We recently upgraded our test cluster to CDH 4.1 and the chmod no
>> >> longer
>> >> works.
>> >>
>> >> sudo -u hdfs hadoop fs -chmod -R 1777 /tmp
>> >> chmod: chmod : mode '1777' does not match the expected pattern.
>> >>
>> >> sudo -u hdfs hadoop fs -chmod -R +t /tmp
>> >> chmod: chmod : mode '+t' does not match the expected pattern.
>> >>
>> >> This disagrees with the docs here:
>> >>
>> >> https://ccp.cloudera.com/display/CDH4DOC/Deploying+MapReduce+v1+%28MRv1%29+on+a+Cluster#DeployingMapReducev1%28MRv1%29onaCluster-Step7

Harsh J