Open zeigerpuppy opened 6 years ago
Did you ever solve this? I am having exactly the same problem :sob:
This is on a Debian stretch server (with systemd).
@georgeowell
Did you read troubleshooting tips? https://docs.sandstorm.io/en/latest/administering/faq/#mongod-failed-to-start-whats-going-on
Does your server have any cgroups limitations, like for example OVH servers have? You can see it by testing does Docker or Snap work for installing Wekan https://wekan.github.io . If those work, Sandstorm works too. Sandstorm requires server that does not limit cgroups etc, and that kernel is new enough, like 3.x or 4.x.
I do have Sandstorm running on Ubuntu 16.04 64bit and Ubuntu 18.04 64bit on KVM.
I am trying to migrate an old sandstorm install (sandstorm-230) to a new server and then update.
The old server was a Xen VM based on Debian Wheezy, the new server is a KVM VM based on Debian Stretch (withouts systemd). The sandstorm installer installs fine and the new instance (sandstorm-234) starts.
I have then copied the old
/opt/sandstorm
folder to the new server and tried starting with/etc/init.d/sandstorm start
.However, sandstorm bails out saying it can't start mongodb, from the
sandstorm.log
:Strangely, the
mongo.log
is not having any new info written to it, it's the old log from the last VM:Are there some more diagnostics I can do to see why mongod is not starting?