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