Question

我正在尝试部署由几个微服务组成的应用程序，每个服务都位于不同的Docker容器中。其中之一（如下所示，主要服务）挂在pm2：client调用守护程序方法for i in `hive -e 'show databases;'`; do echo $i; hive --database=$i -e 'show tables;' | tee -a output.txt; done消息中，并继续打印相同的消息。我试图阅读pm2源代码，阅读文档，并在Internet上到处查找，但是找不到解决方案。这是调试日志。

Calling daemon method pm2:getMonitorData on rpc socket:/root/.pm2/rpc.sock

这是我用于mainService的Dockerfile

main-service_1    | 2018-12-07T18:03:49.482Z axon:sock attempting reconnect
main-service_1    | 2018-12-07T18:03:49.482Z axon:sock closing
main-service_1    | 2018-12-07T18:03:49.482Z axon:sock closing 0 connections
main-service_1    | 2018-12-07T18:03:49.482Z pm2:client Daemon not launched
main-service_1    | 2018-12-07T18:03:49.482Z axon:sock connect attempt null:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49: PM2 log: Launching in no daemon mode
main-service_1    | 2018-12-07T18:03:49.596Z axon:sock bind null:/root/.pm2/pub.sock
main-service_1    | 2018-12-07T18:03:49.597Z axon:sock bind null:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49.602Z interactor:client Interaction file does not exists
main-service_1    | 2018-12-07T18:03:49.602Z interactor:client Secret key is not defined in configuration { version_management: { active: true },
main-service_1    |   public_key: undefined,
main-service_1    |   secret_key: undefined,
main-service_1    |   machine_name: '572eeba2cd52',
main-service_1    |   pm2_version: '3.2.2',
main-service_1    |   reverse_interact: true,
main-service_1    |   info_node: 'https://root.keymetrics.io',
main-service_1    |   agent_transport_websocket: 'false',
main-service_1    |   agent_transport_axon: 'true' }
main-service_1    | 2018-12-07T18:03:49.604Z pm2:client Launching RPC client on socket file /root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock connect attempt null:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock attempting reconnect
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock closing
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock closing 0 connections
main-service_1    | 2018-12-07T18:03:49.604Z interactor:client Interactor Daemon not launched
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock connect attempt null:/root/.pm2/interactor.sock
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock attempting reconnect
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock closing
main-service_1    | 2018-12-07T18:03:49.604Z axon:sock closing 0 connections
main-service_1    | 2018-12-07T18:03:49.605Z interactor:client Interactor Daemon not launched
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock connect attempt null:/root/.pm2/interactor.sock
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock error ENOENT
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock ignored ENOENT
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock error ENOENT
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock ignored ENOENT
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock error ENOENT
main-service_1    | 2018-12-07T18:03:49.605Z axon:sock ignored ENOENT
main-service_1    | 2018-12-07T18:03:49.606Z axon:sock accept /root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49.607Z axon:sock add socket 0
main-service_1    | 2018-12-07T18:03:49.608Z axon:sock connect
main-service_1    | 2018-12-07T18:03:49.608Z axon:sock add socket 0
main-service_1    | 2018-12-07T18:03:49.608Z axon:queue flush 0 messages
main-service_1    | 2018-12-07T18:03:49.608Z pm2:client RPC Connected to Daemon
main-service_1    | 2018-12-07T18:03:49.614Z axon:sock connect attempt null:/root/.pm2/pub.sock
main-service_1    | 2018-12-07T18:03:49.614Z axon:sock accept /root/.pm2/pub.sock
main-service_1    | 2018-12-07T18:03:49.614Z axon:sock add socket 0
main-service_1    | 2018-12-07T18:03:49.614Z axon:sock connect
main-service_1    | 2018-12-07T18:03:49.614Z axon:sock add socket 0
main-service_1    | 2018-12-07T18:03:49.615Z axon:sub subscribe to "log:*"
main-service_1    | 2018-12-07T18:03:49.615Z pm2:cli Resolved filepath /ecosystem.config.js
main-service_1    | 2018-12-07T18:03:49.639Z pm2:client Calling daemon method pm2:getMonitorData on rpc socket:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49.662Z pm2:client Calling daemon method pm2:prepare on rpc socket:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:49: PM2 log: App [API:0] starting in -fork mode-
main-service_1    | 2018-12-07T18:03:49.665Z pm2:fork_mode stds: {"out":"/root/.pm2/logs/API-out-0.log","err":"/root/.pm2/logs/API-error-0.log"}
main-service_1    | 2018-12-07T18:03:49: PM2 log: App [API:0] online
main-service_1    | 2018-12-07T18:03:49.677Z pm2:god Error vizion::analyze() for given folder: /
main-service_1    | 2018-12-07T18:03:49.678Z pm2:god Error vizion::analyze() for given folder: /
main-service_1    | 2018-12-07T18:03:55.680Z pm2:client Calling daemon method pm2:getMonitorData on rpc socket:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:57.689Z pm2:client Calling daemon method pm2:getMonitorData on rpc socket:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:03:59.693Z pm2:client Calling daemon method pm2:getMonitorData on rpc socket:/root/.pm2/rpc.sock
main-service_1    | 2018-12-07T18:04:01.697Z pm2:client Calling daemon method pm2:getMonitorData on rpc socket:/root/.pm2/rpc.sock

这是我的ecosystem.config.js

FROM keymetrics/pm2:latest-jessie
COPY ./ ./
ENV MONGO_URL=http://localhost:3007/slickpoll_polls
ENV DEBUG=*
EXPOSE 3002
RUN npm install
RUN npm install -D ts-node
RUN npm install -D typescript
RUN pm2 install typescript
CMD [ "pm2-runtime", "start", "ecosystem.config.js" ]

这是docker-compose.yml

module.exports = {
  apps : [{
    name: 'API',
    script: 'app.ts',

    // Options reference: https://pm2.io/doc/en/runtime/reference/ecosystem-file/
    instances: 1,
    autorestart: true,
    env: {
      NODE_ENV: 'development'
    },
    env_production: {
      NODE_ENV: 'production'
    }
  }]
};

我花了整整一整天的时间解决此问题，但未能成功。我没有太大的希望解决它了。希望您能找到解决方案。

docker上的PM2卡在getMonitorData

0 个答案: