Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 22 May 2017 06:44:04 +0000 (UTC)
From: "Surendra Singh Lilhore (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13073093.1495107108000.260363.1495435444144@Atlassian.JIRA>
In-Reply-To: <JIRA.13073093.1495107108000@Atlassian.JIRA>
References: <JIRA.13073093.1495107108000@Atlassian.JIRA> <JIRA.13073093.1495107108846@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-11849) JournalNode startup failure
 exception should be logged in log file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 22 May 2017 06:44:09 -0000


    [ https://issues.apache.org/jira/browse/HDFS-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019194#comment-16019194 ] 

Surendra Singh Lilhore commented on HDFS-11849:
-----------------------------------------------

Thanks [~vinayrpet] and [~brahmareddy] for review.. 
Attached updated patch, Please review..


> JournalNode startup failure exception should be logged in log file
> ------------------------------------------------------------------
>
>                 Key: HDFS-11849
>                 URL: https://issues.apache.org/jira/browse/HDFS-11849
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: journal-node
>    Affects Versions: 2.7.0
>            Reporter: Surendra Singh Lilhore
>            Assignee: Surendra Singh Lilhore
>         Attachments: HDFS-11849-001.patch, HDFS-11849-002.patch
>
>
> JournalNode failed to start because of kerberos login. 
> {noformat}
> Exception in thread "main" java.io.IOException: Login failure for xxx/yyyy@ZZZZ.COM from keytab dummy.keytab: javax.security.auth.login.LoginException: host1
>         at org.apache.hadoop.security.UserGroupInformation.loginUserFromKeytab(UserGroupInformation.java:994)
>         at org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:281)
>         at org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:153)
>         at org.apache.hadoop.hdfs.qjournal.server.JournalNode.run(JournalNode.java:132)
>         at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
>         at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
>         at org.apache.hadoop.hdfs.qjournal.server.JournalNode.main(JournalNode.java:318)
> {noformat}
> but this exception is not written in log file.
> {noformat}
> STARTUP_MSG:   java = 1.x.x
> ************************************************************/
> 2017-05-18 16:08:14,961 INFO org.apache.hadoop.hdfs.qjournal.server.JournalNode: registered UNIX signal handlers for [TERM, HUP, INT]
> 2017-05-18 16:08:15,511 INFO org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from hadoop-metrics2.properties
> 2017-05-18 16:08:15,660 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s).
> 2017-05-18 16:08:15,660 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JournalNode metrics system started
> 2017-05-18 16:08:16,429 INFO org.apache.hadoop.hdfs.qjournal.server.JournalNode: SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down JournalNode at w-x-y-z
> ************************************************************/
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org