Where does forever store console log output

Question

I installed forever and am using it  finding it quite funny   But I realized that the logs are placed to somewhere else  Is there any tips

User · Answer

Need to do normal forever start script js to start  and to check console error logs use forever logs this will print list of all logs being stored by forever and then you can use tail -f  path to logs file log and this will print live logs to your window  hit ctrl z to stop logs print

User · Answer

if you run the command  forever logs   you can see where are the logs files   Source  https   github com foreverjs forever

User · Answer

Forever  by default  will put logs into a random file in    forever  folder   You should run forever list to see the running processes and their corresponding log file   Sample output   gt  gt  gt  forever list info     Forever processes running data         uid  command       script forever pid  logfile                         uptime data      0  6n71  usr bin node app js 2233    2239  home vagrant  forever 6n71 log 0 0 0 1 590   However  it s probably best to specify with -l as mentioned by bryanmac

User · Answer

You need to add the log destination specifiers before the filename to run  So  forever -e  path error txt -o  path output txt start index js

User · Answer

It is a old question but i ran across the same issues  If you wanna see live output you can run   forever logs   This would show the path of the logs file as well as the number of the script  You can then use   forever logs 0 -f   0 should be replaced by the number of the script you wanna see the output for

User · Answer

By default forever places all of the files it needs into   HOME  forever  If you would like to change that location just set the FOREVER ROOT environment variable when you are running forever   FOREVER ROOT  etc forever forever start index js

User · Answer

try the command   gt  forever logs   or   gt  sudo forever logs   you will get the log file s location

User · Answer

This worked for me    forever -a -o out log -e err log app js

User · Answer

Help is your best saviour  there is a logs action that you can call to check logs for all running processes   forever --help   Shows the commands  logs                Lists log files for all forever processes logs  lt script index gt  Tails the logs for  lt script index gt    Sample output of the above command  for three processes running  console log output s are stored in these logs   info     Logs for running Forever processes data         script    logfile data      0  server js  root  forever 79ao log data      1  server js  root  forever ZcOk log data      2  server js  root  forever L30K log

User · Answer

Forever takes command line options for output   -l  LOGFILE      Logs the forever output to LOGFILE -o  OUTFILE      Logs stdout from child script to OUTFILE -e  ERRFILE      Logs stderr from child script to ERRFILE   For example    forever start -o out log -e err log my-script js   See here for more info

User · Answer

Based on bryanmac s answer  I m just saving all logs into one file and then reading it with tail  Simple  but effective way to do this   forever -o common log -e common log index js  amp  amp  tail -f common log

[node.js] Where does forever store console.log output?

Examples related to node.js

Examples related to forever