a2 | Mongoose: applications.findOne({ prefix: 'gleaner' }, { fields: {} })
a2 | POST /api/proxy/gleaner/collector/track 200 28.230 ms - 22
a2 | Mongoose: applications.findOne({ prefix: 'gleaner' }, { fields: {} })
a2 | POST /api/proxy/gleaner/collector/track 200 37.727 ms - 22
a2 | Mongoose: applications.findOne({ prefix: 'gleaner' }, { fields: {} })
a2 | POST /api/proxy/gleaner/collector/track 200 62.107 ms - 22
a2 | Mongoose: applications.findOne({ prefix: 'gamestorage' }, { fields: {} })
a2 | _http_outgoing.js:350
a2 | throw new Error('Can\'t set headers after they are sent.');
a2 | ^
a2 |
a2 | Error: Can't set headers after they are sent.
a2 | at ClientRequest.OutgoingMessage.setHeader (_http_outgoing.js:350:11)
a2 | at ProxyServer.<anonymous> (/app/routes/proxy.js:35:18)
a2 | at ProxyServer.emit (/app/node_modules/http-proxy/node_modules/eventemitter3/index.js:119:35)
a2 | at ClientRequest.<anonymous> (/app/node_modules/http-proxy/lib/http-proxy/passes/web-incoming.js:125:27)
a2 | at emitOne (events.js:82:20)
a2 | at ClientRequest.emit (events.js:169:7)
a2 | at tickOnSocket (_http_client.js:484:7)
a2 | at onSocketNT (_http_client.js:496:5)
a2 | at doNTCallback2 (node.js:439:9)
a2 | at process._tickCallback (node.js:353:17)
a2 |
a2 | npm info Authentication-Authorization-Module@0.0.2 Failed to exec start script
a2 | npm ERR! Linux 4.4.0-71-generic
a2 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
a2 | npm ERR! node v4.2.1
a2 | npm ERR! npm v2.14.7
a2 | npm ERR! code ELIFECYCLE
a2 | npm ERR! Authentication-Authorization-Module@0.0.2 start: `node ./bin/www`
a2 | npm ERR! Exit status 1
a2 | npm ERR!
a2 | npm ERR! Failed at the Authentication-Authorization-Module@0.0.2 start script 'node ./bin/www'.
a2 | npm ERR! This is most likely a problem with the Authentication-Authorization-Module package,
a2 | npm ERR! not with npm itself.
a2 | npm ERR! Tell the author that this fails on your system:
a2 | npm ERR! node ./bin/www
a2 | npm ERR! You can get their info via:
a2 | npm ERR! npm owner ls Authentication-Authorization-Module
a2 | npm ERR! There is likely additional logging output above.
a2 |
a2 | npm ERR! Please include the following file with any support request:
a2 | npm ERR! /app/npm-debug.log
a2 |
a2 | npm info Authentication-Authorization-Module@0.0.2 Failed to exec docker-start script
a2 | npm ERR! Linux 4.4.0-71-generic
a2 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "docker-start"
a2 | npm ERR! node v4.2.1
a2 | npm ERR! npm v2.14.7
a2 | npm ERR! code ELIFECYCLE
a2 | npm ERR! Authentication-Authorization-Module@0.0.2 docker-start: `npm run fast-setup && npm run register-root && npm start`
a2 | npm ERR! Exit status 1
a2 | npm ERR!
a2 | npm ERR! Failed at the Authentication-Authorization-Module@0.0.2 docker-start script 'npm run fast-setup && npm run register-root && npm start'.
a2 | npm ERR! This is most likely a problem with the Authentication-Authorization-Module package,
a2 | npm ERR! not with npm itself.
a2 | npm ERR! Tell the author that this fails on your system:
a2 | npm ERR! npm run fast-setup && npm run register-root && npm start
a2 | npm ERR! You can get their info via:
a2 | npm ERR! npm owner ls Authentication-Authorization-Module
a2 | npm ERR! There is likely additional logging output above.
a2 |
a2 | npm ERR! Please include the following file with any support request:
a2 | npm ERR! /app/npm-debug.log
