Still, it would be convenient if the log messages would be printed to the screen after using supervisorctl.
Having to restart Supervisor in debug mode just to see error messages isn't feasible. In our specific case, we change the location of the Supervisor logs in the configuration, so it's not always obvious where the logs are. We also restart Supervisor processes with Mcollective, and it would help to have the starting of processes and the printing of their error messages all done in the same shell so we can easily send the entire transcript to our deploy tool. On Wed, Aug 22, 2012 at 12: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
