Skip to content
New issue

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

forever-monitor crashes under Foreman #53

Open
LeoAdamek opened this issue Nov 21, 2013 · 1 comment
Open

forever-monitor crashes under Foreman #53

LeoAdamek opened this issue Nov 21, 2013 · 1 comment

Comments

@LeoAdamek
Copy link

Under the foreman gem (used by Heroku) forever monitor instantly crashes.

Output of 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)

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.

@indexzero
Copy link
Member

Pretty sure this is a duplicate of #36 which was fixed by #78. Will leave it open as we investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants