[10:34] hi [10:34] is there a tool to log and track all the events emited and handled by upstart and jobs? [13:13] upstart-monitor [17:44] hello. In my upstart scripts I often do the following /usr/local/bin/node /release/thanks-jetpack/current/bin/txjp >> /media/ephemeral0/logs/txjp_web 2>&1 [17:45] but now I'm trying to attach logrotate to that log file and trying to figure out how to cause upstart to reopen the file after rotation [19:35] gansbrest: recent enough upstart, collects all stdout & stderr, and does log rotation [19:35] into /var/log/upstart/$job.log [19:36] gansbrest: so don't do that at all =) [19:36] gansbrest: otherwise, you should use logger [19:36] e.g. see $ man logger. I believe that correctly reopens files etc. [20:17] xnox: you mean just keep /usr/local/bin/node /release/thanks-jetpack/current/bin/txjp and upstart will do the rest? [20:17] will it create 2 files, .out and .err? [20:25] gansbrest: no single .log with both stdout & stderr. [20:25] in /var/log/upstart/ [20:25] gansbrest: do you have /var/log/upstart/ on your system? [20:25] or what's the output of $ sudo initctl version [20:26] I think I'm out of luck here [20:26] init (upstart 0.6.5) [20:26] very old version [20:26] it's interesting that upstart is installed to amazon AMI seem like which is REHL and CentOS [20:27] I mean it's installed for us, someone installed it ) [20:30] I think logger may be an answer as you say [20:31] or writing log directly from the app, and handle HUP signal cause by upstart reload