Question

我正在帮助朋友将Parse应用程序迁移到专用服务器而不是托管服务提供商，而且我一直试图解决我在服务器上的Parse Server实例中发生的错误。

首先，这是PM2日志中的错误堆栈，每次向服务器发出GET或POST时都会抛出它：

parse-wrapper-0 (err):     at null.<anonymous> (/usr/lib/node_modules   /parse-server/node_modules/mongodb-core/lib/connection/pool.js:119:12)
parse-wrapper-0 (err):     at g (events.js:273:16)
parse-wrapper-0 (err):     at emitTwo (events.js:100:13)
parse-wrapper-0 (err):     at emit (events.js:185:7)
parse-wrapper-0 (err):     at Socket.<anonymous> (/usr/lib/node_modules/parse-server/node_modules/mongodb-core/lib/connection/connection.js:144:49)
parse-wrapper-0 (err):     at Socket.g (events.js:273:16)
parse-wrapper-0 (err):     at emitOne (events.js:90:13)
parse-wrapper-0 (err): error: Uncaught internal server error. { [MongoError: server localhost:27017 received an error {"name":"MongoError","message":"write EPIPE"}]
parse-wrapper-0 (err):   name: 'MongoError',
parse-wrapper-0 (err):   message: 'server localhost:27017 received an error {"name":"MongoError","message":"write EPIPE"}' } MongoError: server localhost:27017 received an error {"name":"MongoError","message":"write EPIPE"}
parse-wrapper-0 (err):     at null.<anonymous> (/usr/lib/node_modules/parse-server/node_modules/mongodb-core/lib/topologies/server.js:308:40)
parse-wrapper-0 (err):     at emitTwo (events.js:100:13)
parse-wrapper-0 (err):     at emit (events.js:185:7)
parse-wrapper-0 (err):     at null.<anonymous> (/usr/lib/node_modules/parse-server/node_modules/mongodb-core/lib/connection/pool.js:119:12)
parse-wrapper-0 (err):     at g (events.js:273:16)
parse-wrapper-0 (err):     at emitTwo (events.js:100:13)
parse-wrapper-0 (err):     at emit (events.js:185:7)
parse-wrapper-0 (err):     at Socket.<anonymous> (/usr/lib/node_modules/parse-server/node_modules/mongodb-core/lib/connection/connection.js:144:49)
parse-wrapper-0 (err):     at Socket.g (events.js:273:16)
parse-wrapper-0 (err):     at emitOne (events.js:90:13)

由于我不确定问题的本质（我查看写EPIPE错误是什么，但不确定为什么它会在GET上发生或为什么它每次都关闭），我是我将提供有关我能想到的与此相关的服务器的每条信息。

这是相关的用户结构：

root -defuser：运行mongo实例以及nginx -parse：通过PM2运行解析

这是PM2正在使用的ecosystem.json文件：

{
  "apps":[{
    "name" : "parse-wrapper",
    "script" : "/usr/bin/parse-server",
    "watch" : true,
    "merge_logs" : true,
    "cwd" : "/home/parse",
    "env" : {
      "PARSE_SERVER_CLOUD_CODE_MAIN": "cloud/main.js",
      "PARSE_SERVER_DATABASEURI": "mongodb://parse:SUPERPASSWORDHERE@domain.here:27017/beerdb?ssl=true",
      "PARSE_SERVER_APPLICATION_ID": "super secret Parse key",
      "PARSE_SERVER_MASTER_KEY" : " master key"
   }
  }]
}

这是mongo.conf文件：

# mongod.conf

# for documentation of all options, see:
#   http://docs.mongodb.org/manual/reference/configuration-options/

# Where and how to store data.
storage:
  dbPath: /var/lib/mongodb
  journal:
    enabled: true
#  engine:
#  mmapv1:
#  wiredTiger:

# where to write logging data.
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log

# network interfaces
net:
  port: 27017
  bindIp: 0.0.0.0
  ssl:
    mode: requireSSL
    PEMKeyFile: /etc/ssl/mongo.pem


#processManagement:

security:
  authorization: enabled

#operationProfiling:

#replication:

#sharding:

setParameter:
  failIndexKeyTooLong: false

## Enterprise-Only Options:

#auditLog:

#snmp:

我不认为nginx与此有任何关系，但这是配置，无论如何：

# HTTP - redirect all requests to HTTPS
server {
    listen 80;
    listen [::]:80 default_server ipv6only=on;
    return 301 https://$host$request_uri;
}

# HTTPS - serve HTML from /usr/share/nginx/html, proxy requests to /parse/
# through to Parse Server
server {
    listen 443;
    server_name domain.here;

    root /usr/share/nginx/html;
    index index.html index.htm;

    ssl on;
    # Use certificate and key provided by Let's Encrypt:
    ssl_certificate /etc/letsencrypt/live/domain.here/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/domain.here/privkey.pem;
    ssl_session_timeout 5m;
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

    # Pass requests for /parse/ to Parse Server instance at localhost:1337
    location / {
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-NginX-Proxy true;
            proxy_pass http://localhost:1337/parse/;
            proxy_ssl_session_reuse off;
            proxy_set_header Host $http_host;
            proxy_redirect off;
    }


}

我基本上没有想法，虽然我不仅仅是设置Apache的专家，所以它可能是一个愚蠢的疏忽或者是我的头脑。所以，如果它很简单，那么任何帮助都会受到赞赏和抱歉。

Answer 1

我的部署遇到了同样的问题。事实证明，Parse Dashboard与MongoDB建立了很多连接（在我的情况下是> 1k连接）所以我们必须增加mongo.conf中的最大连接限制和文件描述符限制（取决于你的操作系统）。

例如，在Linux中：

修改mongo.conf文件并添加maxConns = 10000
修改/etc/sysctl.conf文件并添加fs.file-max = 10000
正在运行ulimit -n 50000

MongoError在Parse-Server安装中写入EPIPE

1 个答案: