[KARAF-1748] Karaf startup fails with NullPointerException when logfile can't be written

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.9, 2.3.0
• Fix Version/s: 2.3.1
• Component/s: karaf
• Assignee: Andreas Pieber
• Reporter: Christoph Läubrich
• Created: 20/Aug/12 10:40
• Updated: 14/Sep/18 08:36
• Resolved: 15/Feb/13 13:07

Description

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.open(BootstrapLogManager.java:115)
at org.apache.karaf.main.BootstrapLogManager$SimpleFileHandler.<init>(BootstrapLogManager.java:104)
at org.apache.karaf.main.BootstrapLogManager.getDefaultHandler(BootstrapLogManager.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 starting Karaf",
OR
try to allocate a logfile with a different name.

Issue Links

• is cloned by: KARAF-2191 Karaf 3.0.x CLONE - Karaf startup fails with NullPointerException when logfile can't be written