rikkaapps / fcm-for-mojo-server Goto Github PK

unable to prepare context: unable to 'git clone' to temporary context directory: error initializing submodules: usage: git submodule [--quiet] add [-b <branch>] [-f|--force] [--name <name>] [--reference <repository>] [--] <repository> [<path>]
   or: git submodule [--quiet] status [--cached] [--recursive] [--] [<path>...]
   or: git submodule [--quiet] init [--] [<path>...]
   or: git submodule [--quiet] deinit [-f|--force] [--] <path>...
   or: git submodule [--quiet] update [--init] [--remote] [-N|--no-fetch] [-f|--force] [--rebase] [--reference <repository>] [--merge] [--recursive] [--] [<path>...]
   or: git submodule [--quiet] summary [--cached|--files] [--summary-limit <n>] [commit] [--] [<path>...]
   or: git submodule [--quiet] foreach [--recursive] <command>
   or: git submodule [--quiet] sync [--recursive] [--] [<path>...]
: exit status 1

> [email protected] start C:\mojowebqq\FCM-for-Mojo-Server
> node node/index.js

[FFM] client config file: client.json not exist, use empty data
[FFM] restart called...
[FFM] starting Mojo-Webqq...
[FFM] start Mojo-Webqq... args=C:\mojowebqq\FCM-for-Mojo-Server/perl/start.pl,--
node-port=5004,--openqq-port=5003
[FFM] ids =
[FFM] no https configuration found
[FFM] no basic auth configuration found
[FFM] listening 5005, 193.112.185.37
[FFM] exit with code: 1
[FFM] killing Mojo-Webqq...
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL 193.112.185.37:5005
    at Server.setupListenHandle [as _listen2] (net.js:1343:19)
    at listenInCluster (net.js:1401:12)
    at doListen (net.js:1510:7)
    at _combinedTickCallback (internal/process/next_tick.js:142:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
    at Function.Module.runMain (module.js:696:11)
    at startup (bootstrap_node.js:204:16)
    at bootstrap_node.js:625:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node node/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Ghost\AppData\Roaming\npm-cache\_logs\2018-10-11T05_39_40_
602Z-debug.log