因此，我决定在自己的服务器上设置自己的Parse Server + MongoDB。 使用mongodb进行的设置工作正常，但是当我想通过在控制台中键入“ npm start”从github启动我的parse-server-example克隆时，会得到以下日志：
> parse-server-example@1.4.0 start /opt/parse-server-example
> node index.js
DATABASE_URI not specified, falling back to localhost.
parse-server-example running on port 1337.
info: Parse LiveQuery Server starts running
{ MongoParseError: Value for `compressors` must be at least one of: `snappy`, `zlib`
at applyConnectionStringOption (/opt/parse-server-example/node_modules/mongodb/lib/core/uri_parser.js:252:13)
at parseQueryString (/opt/parse-server-example/node_modules/mongodb/lib/core/uri_parser.js:410:5)
at parseConnectionString (/opt/parse-server-example/node_modules/mongodb/lib/core/uri_parser.js:565:21)
at connect (/opt/parse-server-example/node_modules/mongodb/lib/operations/connect.js:272:3)
at cb (/opt/parse-server-example/node_modules/mongodb/lib/mongo_client.js:215:5)
at maybePromise (/opt/parse-server-example/node_modules/mongodb/lib/utils.js:719:3)
at MongoClient.connect (/opt/parse-server-example/node_modules/mongodb/lib/mongo_client.js:211:10)
at Function.MongoClient.connect (/opt/parse-server-example/node_modules/mongodb/lib/mongo_client.js:421:22)
at MongoStorageAdapter.connect (/opt/parse-server-example/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:159:42)
at MongoStorageAdapter._schemaCollection (/opt/parse-server-example/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:214:17)
name: 'MongoParseError',
[Symbol(mongoErrorContextSymbol)]: {} }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! parse-server-example@1.4.0 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the parse-server-example@1.4.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/leon/.npm/_logs/2020-06-14T13_47_04_969Z-debug.log
日志文件如下所示：
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@6.14.5
3 info using node@v10.21.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle parse-server-example@1.4.0~prestart: parse-server-example@1.4.0
6 info lifecycle parse-server-example@1.4.0~start: parse-server-example@1.4.0
7 verbose lifecycle parse-server-example@1.4.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle parse-server-example@1.4.0~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/parse-server-example/node_modules/.bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle parse-server-example@1.4.0~start: CWD: /opt/parse-server-example
10 silly lifecycle parse-server-example@1.4.0~start: Args: [ '-c', 'node index.js' ]
11 silly lifecycle parse-server-example@1.4.0~start: Returned: code: 1 signal: null
12 info lifecycle parse-server-example@1.4.0~start: Failed to exec start script
13 verbose stack Error: parse-server-example@1.4.0 start: `node index.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid parse-server-example@1.4.0
15 verbose cwd /opt/parse-server-example
16 verbose Linux 5.6.0-kali2-amd64
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v10.21.0
19 verbose npm v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error parse-server-example@1.4.0 start: `node index.js`
22 error Exit status 1
23 error Failed at the parse-server-example@1.4.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
感谢您的任何建议！