[jira] [Resolved] (SLING-9118) Sling fails to start when database exists but 'sling' directory is missing

["Robert Munteanu (Jira)" <ji...@apache.org>]

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

Robert Munteanu resolved SLING-9118.
------------------------------------
    Fix Version/s: Starter 12
       Resolution: Fixed

[~carlosmunoz], [~benradey] - I'm going to consider this fixed since the fixes in org.apache.sling.jcr.base 3.1.4 are now included in the Sling Starter.

Please reopen if you still see the problem.

> 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
>             Fix For: Starter 12
>
>         Attachments: drop-mongo.sh, error.log, fm-launch.zip, 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)