Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server won't start with error "storage directory is not a directory" #11086

Open
rafaelpac opened this issue Mar 2, 2025 · 1 comment
Open
Labels

Comments

@rafaelpac
Copy link

rafaelpac commented Mar 2, 2025

Describe the bug

I am following the bare metal deployment with systemd (home server)

The only change I made was the OCIS_BASE_DATA_PATH
Instead of /var/lib/ocis, I want to use /mnt/HDD/ocis (storage constraints on the system boot disk).
I created the folder and it is mounted, I followed all procedures described.

When started, I get this error: ### Can't start JetStream: storage directory is not a directory
rafael@twist:/mnt/HDD$ sudo systemctl restart ocis
rafael@twist:/mnt/HDD$ sudo journalctl -f -u ocis
Mar 02 18:14:20 twist systemd[1]: ocis.service: Failed with result 'exit-code'.
Mar 02 18:14:21 twist systemd[1]: ocis.service: Scheduled restart job, restart counter is at 4.
Mar 02 18:14:21 twist systemd[1]: Started ocis.service - OCIS server.
Mar 02 18:14:21 twist ocis[46624]: {"level":"fatal","service":"nats","time":"2025-03-02T18:14:21-03:00","message":"Can't start JetStream: storage directory is not a directory"}
Mar 02 18:14:21 twist systemd[1]: ocis.service: Main process exited, code=exited, status=1/FAILURE
Mar 02 18:14:21 twist systemd[1]: ocis.service: Failed with result 'exit-code'.
Mar 02 18:14:21 twist systemd[1]: ocis.service: Scheduled restart job, restart counter is at 5.
Mar 02 18:14:21 twist systemd[1]: ocis.service: Start request repeated too quickly.
Mar 02 18:14:21 twist systemd[1]: ocis.service: Failed with result 'exit-code'.
Mar 02 18:14:21 twist systemd[1]: Failed to start ocis.service - OCIS server.

Steps to reproduce

Follow the bare metal deployment

Expected behavior

Service started

If I use the suggested /var/lib/ocis, it does work.

Actual behavior

Service not started

Setup

Please describe how you started the server and provide a list of relevant environment variables or configuration files.

OCIS_CONFIG_DIR=/etc/ocis
OCIS_BASE_DATA_PATH=/mnt/HDD/ocis

Additional context

Add any other context about the problem here.

@rafaelpac
Copy link
Author

The exact same error happens in the docker deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant