You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Mark Grover (JIRA)" <ji...@apache.org> on 2013/07/14 08:24:48 UTC

[jira] [Created] (BIGTOP-1025) Starting hadoop-mapreduce-historyserver prints error on Ubuntu Lucid

Mark Grover created BIGTOP-1025:
-----------------------------------

             Summary: Starting hadoop-mapreduce-historyserver prints error on Ubuntu Lucid
                 Key: BIGTOP-1025
                 URL: https://issues.apache.org/jira/browse/BIGTOP-1025
             Project: Bigtop
          Issue Type: Bug
          Components: Debian
    Affects Versions: 0.6.0
            Reporter: Mark Grover


When starting the hadoop-mapreduce-historyserver service, an error is printed like the following:
{code}
vagrant@lucid64:~$ sudo service hadoop-mapreduce-historyserver start
 * Starting Hadoop historyserver: 
chown: changing ownership of `/var/log/hadoop-mapreduce': Operation not permitted
starting historyserver, logging to /var/log/hadoop-mapreduce/mapred-mapred-historyserver-lucid64.out
vagrant@lucid64:~$ sudo service hadoop-mapreduce-historyserver status^C
vagrant@lucid64:~$ echo $?
130
vagrant@lucid64:~$ sudo service hadoop-mapreduce-historyserver status
 * Hadoop historyserver is running
vagrant@lucid64:~$ ps -ef | grep -i history
mapred   17007     1 14 08:20 pts/0    00:00:04 /usr/lib/jvm/j2sdk1.6-oracle/bin/java -Dproc_historyserver -Xmx1000m -Djava.net.preferIPv4Stack=true -Xmx128m -Dhadoop.log.dir=/usr/lib/hadoop/logs -Dhadoop.log.file=hadoop.log -Dhadoop.home.dir=/usr/lib/hadoop -Dhadoop.id.str=mapred -Dhadoop.root.logger=INFO,console -Djava.library.path=/usr/lib/hadoop/lib/native -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true -Dhadoop.log.dir=/var/log/hadoop-mapreduce -Dhadoop.log.file=mapred-mapred-historyserver-lucid64.log -Dhadoop.root.logger=INFO,RFA -Dmapred.jobsummary.logger=INFO,JSA -Dhadoop.security.logger=INFO,NullAppender org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer
{code}
The service start command returns an error code but the service seems to have started correctly.

We should fix the start command and ensure that it returns success.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira