Hi Muhammad,

On Mon, Nov 10, 2014 at 9:11 PM, Muhammad Kashif <kashif.as...@ebryx.com> wrote:
> Can you please help me out to resolve the following issue on heroku
> platform.
>
> For issue details please follow the link below.
>
> http://stackoverflow.com/questions/26757380/heroku-web-process-timeout-while-running-a-daemon-server-of-node-js-backed-with

I don't know much about Node.js and Express, but if I'm reading your
code snippet correctly, it looks like the code is never binding to a
port.  In other words, it looks like your running a background job,
not a web server.  In that case, rename 'web' in your Procfile to
'worker' and then run 'heroku ps:scale web=0 worker=1'.  Processes
called 'web' are expected to bind to the port identified by the PORT
environment variable within 60 seconds.  If a process doesn't do that
the runtime system automatically restarts it.

There's more information about the R10 code in your logs here:

  https://devcenter.heroku.com/articles/error-codes#r10-boot-timeout

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to