Yeah, that's not what the original question was though, and it still isn't a great way to do it.
Essentially, the OP was asking for the ability for it to show the last X number of log lines if the start fails, rather than having to type tail X after every failed start. This doesn't apply so much to automation scripts (as in our deploy scripts, we auto check if it fails and then do a tail if it did anyway), but applies more to manual CLI usage Cal On Wed, Aug 22, 2012 at 5:15 PM, Chris McDonough <[email protected]> wrote: > On 08/22/2012 12:09 PM, Neil Hooey wrote: > >> When I start a supervisor process like this: >> >> sudo supervisorctl start $process >> >> And it fails, I just get this error: >> >> $group:$process: ERROR (abnormal termination) >> >> Is there a way to get supervisor to capture and print the part of the >> process' log relevant to the error? >> > > The command > > supervisord -n -edebug > > Starts supervisord in the foreground and sends debugging output to the > console. > > - C > > > ______________________________**_________________ > Supervisor-users mailing list > Supervisor-users@lists.**supervisord.org<[email protected]> > http://lists.supervisord.org/**mailman/listinfo/supervisor-**users<http://lists.supervisord.org/mailman/listinfo/supervisor-users> >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
