amazon web services - AWS EMR Cluster terminates while custom bootstrapping -

i running following command create emr cluster , cluster terminates in bootstrapping phase

aws emr create-cluster --ami-version 3.1.0 \ --ami-version 3.8.0 \ --service-role emr.sentmtemrservicerole \ --bootstrap-actions path=s3://ae1-s3-sentmt-anlys/config-nltk.sh,name="custom action" \ --log-uri s3://aws-logs-476270297889-us-east-1/elasticmapreduce \ --ec2-attributes instanceprofile=ec2-sentmt.role,keyname=ae1-nat-sentmt-anlys \ --instance-groups instancegrouptype=master,instancecount=1,instancetype=m1.medium instancegrouptype=core,instancecount=1,instancetype=m1.medium 

and log file has following entry in s3 bucket:

another app holding yum lock; waiting exit...   other application is: yum     memory :  28 m rss (412 mb vsz)     started: wed jul 15 08:25:44 2015 - 00:18 ago     state  : running, pid: 1430   transaction check error:   file /etc/init.d install of chkconfig-1.3.49.3-2.14.amzn1.x86_64 conflicts file package emrmetrics-1.0-1.noarch   file /etc/init.d install of chkconfig-1.3.49.3-2.14.amzn1.x86_64 conflicts file package service-nanny-1.0-1.noarch   file /etc/init.d install of chkconfig-1.3.49.3-2.14.amzn1.x86_64 conflicts file package instance-controller-1.0-1.noarch   file /etc/init.d install of chkconfig-1.3.49.3-2.14.amzn1.x86_64 conflicts file package hadoop-state-pusher-1.0-1.noarch  error summary -------------  /usr/bin/python: no module named nltk 

can please tell me wrong command? thank in advance :)

this late, else running was. solution can found here: https://forums.aws.amazon.com/message.jspa?messageid=614195

there 2 ways fix. easiest use more date ami version. if copied someones command line start cluster, replace ami version tag with: --ami-version 3.9.0

if stuck on current ami version, can around issue modifying yum command releasever:

yum --releasever=2014.09 install <package_name>