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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Starter 12
• Assignee: Robert Munteanu
• Reporter: Ben Radey
• Created: 21/Feb/20 15:59
• Updated: 18/Mar/22 15:05
• Resolved: 10/Aug/20 13:48

Description

1. Create a persistent mongodb to use with Sling.
2. Start sling using the mongodb.
3. Stop sling.
4. Remove 'sling' directory.
5. Attempt to restart sling. Ultimately, sling fails to start.

---

Steps to reproduce with attached scripts:

1. Run run-mongo.sh . This creates a MongoDB 3.6 container named mongo-sling
2. Run run-sling-initial.sh. This starts up Sling in the oak_mongo runmode, shuts it down after it's (probably) started up
3. 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.

Issue Links

• relates to: SLING-7811 NPE when repository is starting up due to repository manager shutdown