Tell your application to log to STDOUT instead of to the file. Logging to STDOUT is the Heroku way.
- Daniel On Tue, Apr 17, 2012 at 9:26 AM, Alex Brown <[email protected]> wrote: > I've opened a support request on this as my app isn't running.... > Will post details here when I receive a fix. > > If anyone has any ideas in the meantime, i'd be very grateful! > > > > On Tuesday, 17 April 2012 14:23:46 UTC+1, Alex Brown wrote: >> >> I'm deploying a node.js app to heroku (cedar stack) >> >> I've set the NODE_ENV like this: >> >> heroku config:add NODE_ENV=production >> >> I then do: >> >> git push heroku >> >> However, after starting (i've got a console.log generating the first log >> entry) the app crashes. >> >> I run: >> >> heroku logs >> >> and get the below error. >> >> How can I open the /app/log/production.log that it's referring to? >> >> app[web.1]: listening on port 32168 within production environment >> app[web.1]: >> app[web.1]: events.js:48 >> app[web.1]: throw arguments[1]; // Unhandled 'error' event >> app[web.1]: ^ >> app[web.1]: Error: ENOENT, open '/app/log/production.log' >> heroku[web.1]: Process exited with status 1 >> heroku[web.1]: State changed from starting to crashed >> >> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/heroku/-/PAJjYYVthVMJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
