Skip to main content
Version: 1.0

Troubleshooting

Install stopped midway — how to clean up and retry

Stop and remove any partially-created containers, then re-run the installer:

~/xplurdata/manage.sh stop 2>/dev/null
cd ~/xplurdata && docker compose down
bash -c "$(curl -fsSL https://raw.githubusercontent.com/xplurdata/oss-stack/main/install.sh)"
Stack not starting

Check container status and follow the logs to find the failing service:

~/xplurdata/manage.sh status
~/xplurdata/manage.sh logs

Most first-boot failures are Doris still initialising — give it up to ~10 minutes on the first run.

Doris FE fails with "insufficient memory"

Doris needs enough RAM for its JVM heap. On machines with less than 8 GB the installer applies reduced JVM settings automatically — but if you're still short on memory, free some up or move to a host that meets the recommended requirements (8 GB RAM).

~/xplurdata/manage.sh logs doris-fe
No data in otel_db.otel_logs
  1. Confirm the OTel Collector is running: ~/xplurdata/manage.sh logs otel-collector
  2. Verify your app points at http://<your-ip>:4318 over OTLP/HTTP.
  3. Run the telemetrygen test to isolate whether the problem is the pipeline or your app.

Remember the pre-seeded demo data lives in demo_otel_db.otel_logs, not otel_db.

App not ready after 5 minutes

First boot can take longer while Doris initialises. Watch the application logs:

~/xplurdata/manage.sh logs

If it's still not ready well past 5 minutes, check the Doris backend: ~/xplurdata/manage.sh logs doris-be.

Port 80 or 4318 already in use

Find and stop whatever is holding the port:

sudo lsof -i :80
sudo lsof -i :4318

Free the port (or reconfigure the conflicting service), then restart: ~/xplurdata/manage.sh restart.

macOS: process.lock AccessDeniedException

This is typically a stale lock from an interrupted run on Docker Desktop. Stop the stack, remove the volume's lock state, and restart:

~/xplurdata/manage.sh stop
~/xplurdata/manage.sh restart

Ensure Docker Desktop is running and has sufficient resources allocated (Settings → Resources).

Full reset (wipes all data)
danger

This permanently deletes all stored telemetry.

~/xplurdata/manage.sh uninstall
cd ~/xplurdata && docker compose down -v   # -v removes the data volumes

Then re-run the installer for a clean start.