Cannot create new boards in latest revision on Sandstorm!

Issue

Impacted version: 0.60.0~2017-11-29

Server Setup Information:

• Operating System: Arch with latest updates
• Deployment Method(tar/sandstorm/snap/docker/etc /http frontend (nginx, httpd, …)): Sandstorm
• Node Version: Sandstorm builtin (host has no nodeJS)
• MongoDB Version: Sandstorm builtin
• ROOT_URL environment variable (Is there a subfolder?):

Problem description: When creating a new board in my sandstorm server, it fails to load it, stating “Error: remote exception: Peer disconnected. C++ location:(remote):?? type: disconnected” The console log reveals it’s missing a module, but I’m not sure that’s the issue:

child process started successfully, parent exiting
** Starting Meteor...
{ [Error: Cannot find module '../build/Release/bson'] code: 'MODULE_NOT_FOUND' }
js-bson: Failed to load c++ bson extension, using pure JS version

/programs/server/node_modules/fibers/future.js:313
						throw(ex);
						^
MongoError: failed to connect to server [127.0.0.1:4001] on first connect
    at Object.Future.wait (/programs/server/node_modules/fibers/future.js:449:15)
    at new MongoConnection (packages/mongo/mongo_driver.js:211:27)
    at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
    at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:10)
    at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
    at new Mongo.Collection (packages/mongo/collection.js:99:40)
    at packages/idmontie_migrations.js:38:15
    at packages/idmontie_migrations.js:255:4
    at packages/idmontie_migrations.js:267:3
    at /programs/server/boot.js:303:34
    - - - - -
    at [object Object].<anonymous> (/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/topologies/server.js:326:35)
    at emitOne (events.js:77:13)
    at [object Object].emit (events.js:169:7)
    at [object Object].<anonymous> (/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:270:12)
    at [object Object].g (events.js:260:16)
    at emitTwo (events.js:87:13)
    at [object Object].emit (events.js:172:7)
    at Socket.<anonymous> (/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/connection.js:175:49)
    at Socket.g (events.js:260:16)
    at emitOne (events.js:77:13)
** HTTP-BRIDGE: App server exited with status code: 1

I’m using the latest version Sandstorm provides and I’ve seen this behavior across multiple accounts. Existing boards are unaffected, but it’d be really nice to be able to create new ones 😉

[xarinatan]

just a note to this old thread; I just found that I can more or less reproduce this issue by pausing/saving the VM that Sandstorm is running on and keeping it paused for a while. For some reason most things work well (using existing boards, creating new grains of a lot of other apps, etc) but creating new Wekan boards causes the original error. Rebooting doesn’t fix it, but turning off the VM and then starting it up again does… The only thing I can think of is time/clock issues, but I’m running ntpd on the VM so I’m not sure what’s up… It’s a very peculiar thing 🤔 it’s not really an issue anymore though, just thought I’d share my findings 😃

[kentonv]

@xarinatan Glad to hear you figured it out.

It’s hard to say what about the hardened kernel could be an issue, since Mongo didn’t report any particular error. We’d probably have to run it in a debugger or strace to find out what exactly it did leading up to the failure. It is surprising that Sandstorm itself (which uses Mongo, after all) worked fine, and only inside Wekan did something go wrong.