We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Under the foreman gem (used by Heroku) forever monitor instantly crashes.
Output of node application.js
node application.js
12:12:22 leo@xcom angry-wizard master node application.js Listening on *:300
Output of foreman start (where Procfile contains only web: node application.js)
foreman start
Procfile
web: node application.js
12:04:10 leo@xcom angry-wizard master foreman start 12:12:22 web.1 | started with pid 5815 12:12:22 web.1 | 12:12:22 web.1 | _stream_readable.js:745 12:12:22 web.1 | while (!paused && (null !== (c = stream.read()))) 12:12:22 web.1 | ^ 12:12:22 web.1 | TypeError: Property 'read' of object #<Socket> is not a function 12:12:22 web.1 | at Socket.<anonymous> (_stream_readable.js:745:45) 12:12:22 web.1 | at Socket.EventEmitter.emit (events.js:92:17) 12:12:22 web.1 | at emitDataEvents (_stream_readable.js:771:10) 12:12:22 web.1 | at Socket.Readable.on (_stream_readable.js:692:5) 12:12:22 web.1 | at Monitor.startLogs (/home/leo/development/projects/angry-wizard/node_modules/deployd/node_modules/forever-monitor/lib/forever-monitor/plugins/logger.js:56:28) 12:12:22 web.1 | at Monitor.EventEmitter.emit (/home/leo/development/projects/angry-wizard/node_modules/deployd/node_modules/forever-monitor/node_modules/broadway/node_modules/eventemitter2/lib/eventemitter2.js:332:22) 12:12:22 web.1 | at /home/leo/development/projects/angry-wizard/node_modules/deployd/node_modules/forever-monitor/lib/forever-monitor/monitor.js:152:10 12:12:22 web.1 | at process._tickDomainCallback (node.js:459:13) 12:12:22 web.1 | at Function.Module.runMain (module.js:499:11) 12:12:22 web.1 | at startup (node.js:119:16) 12:12:22 web.1 | exited with code 8 12:12:22 system | sending SIGTERM to all processe
This is stopping me deploying an app using forever-monitor to Heroku. No idea why this is happening.
The text was updated successfully, but these errors were encountered:
Pretty sure this is a duplicate of #36 which was fixed by #78. Will leave it open as we investigate.
Sorry, something went wrong.
No branches or pull requests
Under the foreman gem (used by Heroku) forever monitor instantly crashes.
Output of
node application.js
Output of
foreman start
(whereProcfile
contains onlyweb: node application.js
)This is stopping me deploying an app using forever-monitor to Heroku. No idea why this is happening.
The text was updated successfully, but these errors were encountered: