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

Oliver Lietz commented on SLING-9118:
-------------------------------------

[~carlosmunoz], You have to build a [custom 
distribution|http://karaf.apache.org/manual/latest/#_custom_distributions] 
yourself or edit {{org.apache.karaf.features.cfg}} and add 
{{sling-quickstart-oak-tar}} or {{sling-quickstart-oak-mongo}} feature to 
{{featuresBoot}}. The [Sling Karaf 
Distribution|https://github.com/apache/sling-org-apache-sling-karaf-distribution]
 just collects all dependencies for offline usage and allows users to 
select/start the preferred quickstart feature.

The recommended way is to build a custom distribution anyway because you want 
to tweak some configurations for production and add your application feature(s).

> Sling fails to start when database exists but 'sling' directory is missing
> --------------------------------------------------------------------------
>
>                 Key: SLING-9118
>                 URL: https://issues.apache.org/jira/browse/SLING-9118
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Ben Radey
>            Assignee: Robert Munteanu
>            Priority: Major
>         Attachments: drop-mongo.sh, error.log, karaf.log, 
> recreateSlingReplicaSet.sh, run-mongo.sh, run-sling-initial.sh, 
> run-sling-second.sh, sling-startup-error.log.txt
>
>
> # Create a persistent mongodb to use with Sling.
>  # Start sling using the mongodb.
>  # Stop sling.
>  # Remove 'sling' directory.
>  # Attempt to restart sling. Ultimately, sling fails to start.
> ----
> Steps to reproduce with attached scripts:
> # Run [^run-mongo.sh] . This creates a MongoDB 3.6 container named 
> _mongo-sling_
> # Run [^run-sling-initial.sh]. This starts up Sling in the oak_mongo runmode, 
> shuts it down after it's (probably) started up
> # Run [^run-sling-second.sh]. This moves away the sling directory and starts 
> up a new instance. This always fails
> For cleanup, the [^drop-mongo.sh] script stops and removes the _mongo-sling_ 
> container.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to