You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/04/09 16:11:12 UTC

[jira] [Resolved] (KARAF-3471) Karaf can't start if etc/config.properties is not writable

     [ https://issues.apache.org/jira/browse/KARAF-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-3471.
-----------------------------------------
    Resolution: Fixed

> Karaf can't start if etc/config.properties is not writable
> ----------------------------------------------------------
>
>                 Key: KARAF-3471
>                 URL: https://issues.apache.org/jira/browse/KARAF-3471
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> The Karaf main loads the config.properties (as a org.apache.felix.utils.properties.Properties) and load some additional properties in it (like System env/properties).
> Especially, it writes one thing (and the only thing ;)): the shutdown command.
> It's the:
> {code}
> karaf.shutdown.command
> {code}
> property, containing an unique/random UUID to "secure" the Karaf shutdown.
> If the property is not in etc/config.properties, Karaf will try to create one and write in etc/config.properties.
> If the property is already there, it just uses it.
> So, as a workaround, you can modify etc/config.properties to add:
> {code}
> karaf.shutdown.command=321DE18U23187
> {code}
> (or whatever you want).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)