search

juzibot / donut-tester

40 stars 4 forks source link

donut failed to start #30

Closed treeguard closed 3 years ago

treeguard commented 4 years ago

Important：Please file the issue follow the template, or we won't help you to solve the problem.

0. Report Issue Guide

  1. Please run the following command and check whether the problem has been fixed：

    rm -rf package-lock.json
rm -rf node_modules
npm install

    The problem is still there after I run the above commands.

  2. Please search in FAQ List first, and make sure your problem has not been solved before.

Not found

  1. Please search in the issue first, and make sure your problem had not been reported before

1. Versions

18:49:04 INFO Wechaty <wechaty-puppet-hostie>() start() v0.38.4 is starting...
18:49:05 ERR PuppetHostie start() rejection: 14 UNAVAILABLE: failed to connect to all addresses
Error: 14 UNAVAILABLE: failed to connect to all addresses
    at Object.exports.createStatusError (/Users/tree/WeChatProjects/bmzf-bot/node_modules/grpc/src/common.js:91:15)
    at Object.onReceiveStatus (/Users/tree/WeChatProjects/bmzf-bot/node_modules/grpc/src/client_interceptors.js:1209:28)
    at InterceptingListener._callNext (/Users/tree/WeChatProjects/bmzf-bot/node_modules/grpc/src/client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (/Users/tree/WeChatProjects/bmzf-bot/node_modules/grpc/src/client_interceptors.js:618:8)
    at callback (/Users/tree/WeChatProjects/bmzf-bot/node_modules/grpc/src/client_interceptors.js:847:24) {
  code: 14,
  metadata: Metadata { _internal_repr: {}, flags: 0 },
  details: 'failed to connect to all addresses'
}
18:49:05 ERR Wechaty start() exception: 14 UNAVAILABLE: failed to connect to all addresses
18:49:05 ERR StarterBot Error: 14 UNAVAILABLE: failed to connect to all addresses
18:49:05 WARN PuppetHostie stop() is called on a OFF puppet. await ready(off) and return.
18:49:05 ERR PuppetHostie start() rejection: puppetClient had already inited
18:49:05 WARN Puppet reset() exception: Error: puppetClient had already inited
(node:87174) UnhandledPromiseRejectionWarning: Error
    at PuppetHostie.<anonymous> (/Users/tree/WeChatProjects/bmzf-bot/node_modules/wechaty/dist/src/wechaty.js:433:44)
    at PuppetHostie.emit (events.js:315:20)
    at PuppetHostie.EventEmitter.emit (domain.js:485:12)
    at PuppetHostie.emit (/Users/tree/WeChatProjects/bmzf-bot/node_modules/wechaty-puppet/dist/src/puppet.js:162:22)
    at /Users/tree/WeChatProjects/bmzf-bot/node_modules/wechaty-puppet/dist/src/puppet.js:191:18
(node:87174) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:87174) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

3. To Reproduce

This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.

Here is my code

function getWindowBot() {
  const token = ''
  return new Wechaty({
    puppet: 'wechaty-puppet-hostie',
    puppetOptions: {
      token,
    }
  })
}

const bot = new getWindowBot()

Steps to reproduce the behavior:

  1. run '...'
  2. ...
  3. ...

4. Expected behavior

Give a clear and concise description of what you expected to happen.

5. Actual behavior

If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.

6. Full Output Logs

Set env WECHATY_LOG=silly in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)

We need full log instead of log screenshot or log fragments!

Show Logs ```shell $ WECHATY_LOG=silly node yourbot.js Question: Paste your FULL(DO NOT ONLY PROVIDE FRAGMENTS) log messages Answer: ```

7. Additional context

Add any other context about the problem here.

[bug]