Server start SST read error

Stardog-server start fails with:

corrupt SST file ahead of WALs in CF

  • after we ran low on disk space.

Is there a way/flag to start the server ignoring the WALs error?

We're having issues with this as well. We keep the /var as small as possible, but after the necessary config (including setting $STARDOG_HOME), it still seems to write logs and sst files to /var/opt/stardog/


It sounds like you're running stardog through systemd, in which case the $STARDOG_HOME that you're setting would be overwritten at service startup when it sources /etc/ If you want a permanent different home, you would need to make sure that STARDOG_HOME is being set properly in /etc/

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.