You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: spawn ENOMEM
at exports.errnoException (util.js:874:11)
at ChildProcess.spawn (internal/child_process.js:298:11)
at exports.spawn (child_process.js:339:9)
at Object.exports.execFile (child_process.js:141:15)
at Object.exports.exec (child_process.js:101:18)
at TimedExecuter.execute (/home/vagrant/CTFd/lib/timedexecuter.js:20:31)
at ServiceCommandExecuter.execute (/home/vagrant/CTFd/lib/servicecommandexecuter.js:78:19)
at /home/vagrant/CTFd/lib/servicecommandexecuter.js:58:14
at Array.forEach (native)
at Function..each..forEach (/home/vagrant/CTFd/node_modules/underscore/underscore.js:76:11)
And it crashes the first time it tries to "check".
I even suceeded in getting
P{ [MongoError: topology was destroyed] name: 'MongoError', message: 'topology was destroyed' }
How to approach this?
some info
$ mongod --version
db version v2.4.14
Sat Nov 21 00:09:23.926 git version: nogitversion
I'm working with the team server from prosa2014, and have tweaked the config.js to match.
And it works - for 30 minutes...
Then it craches and I need to restart mongodb
With errors like this
And it crashes the first time it tries to "check".
I even suceeded in getting
How to approach this?
some info
$ npm list
[email protected] /home/vagrant/CTFd
├── [email protected]
├── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
└── [email protected]
The text was updated successfully, but these errors were encountered: