Return-Path: 
 <issues-return-12761-apmail-karaf-issues-archive=karaf.apache.org@karaf.apache.org>
X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org
Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id DFEBAE5F7
	for <apmail-karaf-issues-archive@minotaur.apache.org>;
 Thu, 14 Feb 2013 23:31:12 +0000 (UTC)
Received: (qmail 1261 invoked by uid 500); 14 Feb 2013 23:31:12 -0000
Delivered-To: apmail-karaf-issues-archive@karaf.apache.org
Received: (qmail 1202 invoked by uid 500); 14 Feb 2013 23:31:12 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 1188 invoked by uid 99); 14 Feb 2013 23:31:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 23:31:12 +0000
Date: Thu, 14 Feb 2013 23:31:12 +0000 (UTC)
From: "Heath Kesler (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12604032.1345459214244.290898.1360884672594@arcas>
In-Reply-To: <JIRA.12604032.1345459214244@arcas>
References: <JIRA.12604032.1345459214244@arcas>
Subject: [jira] [Commented] (KARAF-1748) Karaf startup fails with
 NullPointerException when logfile can't be written
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/KARAF-1748?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1357=
8805#comment-13578805 ]=20

Heath Kesler commented on KARAF-1748:
-------------------------------------

Looks like the patch was not applied to 3.0 either.  I will back port this =
to 2.3.x this evening for the release, then apply the patch to 3.0.
               =20
> Karaf startup fails with NullPointerException when logfile can't be writt=
en
> -------------------------------------------------------------------------=
--
>
>                 Key: KARAF-1748
>                 URL: https://issues.apache.org/jira/browse/KARAF-1748
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.2.9, 2.3.0, 3.0.0
>            Reporter: Christoph L=C3=A4ubrich
>            Assignee: Andreas Pieber
>            Priority: Minor
>             Fix For: 2.2.11, 2.3.1, 3.0.0
>
>         Attachments: karaf-3.0_1748.diff
>
>
> The karaf startup fails with a NullPointerException when the logifle can'=
t be accessed:
> java.io.FileNotFoundException: /opt/karaf/data/log/karaf.log (Permission =
denied)
>         at java.io.FileOutputStream.openAppend(Native Method)
>         at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>         at org.apache.karaf.main.BootstrapLogManager$SimpleFileHandler.op=
en(BootstrapLogManager.java:115)
>         at org.apache.karaf.main.BootstrapLogManager$SimpleFileHandler.<i=
nit>(BootstrapLogManager.java:104)
>         at org.apache.karaf.main.BootstrapLogManager.getDefaultHandler(Bo=
otstrapLogManager.java:83)
>         at org.apache.karaf.main.Main.launch(Main.java:234)
>         at org.apache.karaf.main.Main.main(Main.java:429)
> Could not create framework: java.lang.NullPointerException
> java.lang.NullPointerException
>         at java.util.logging.Logger.addHandler(Logger.java:1185)
>         at org.apache.karaf.main.Main.launch(Main.java:234)
>         at org.apache.karaf.main.Main.main(Main.java:429)
> This should be changed to: Output a meaningfull message e.g. "Karaf can't=
 startup, make sure the logifle can be accessed and written by the user sta=
rting Karaf",
> OR
> try to allocate a logfile with a different name.

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