Where does supervisorctl tail take the log information of a certain process from? How do I get a full log?
Where does supervisorctl tail take the log information of a certain process from? How
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
From the command line help (
supervisorctl help tail):tail [-f] <name> [stdout|stderr] (default stdout) Ex: tail -f <name> Continuous tail of named process stdout Ctrl-C to exit. tail -100 <name> last 100 *bytes* of process stdout tail <name> stderr last 1600 *bytes* of process stderrSo by default, the
tailcommand tails the process stdout. If you need to get the full log, thestdout_logfileoption of the[program:x]section determines where that is stored; there is astderr_logfileoption as well.If that option is not set or set to
AUTO, a logfile will be created when the process starts, but cleaned up whenever supervisord restarts. This file is created in the directory set by the[supervisord]childlogdiroption (which is your platform’sTMPdirectory by default), and have a generated filename of the form<program-name>-<stdout|stderr>---<supervisor-identifier>-<6-random-characters>.log, e.g.varnish-stdout---supervisor-AqY52e.log.Thus, if you want to access the whole stdout log, you need to at the very least set the
childlogdiroption to a fixed directory to save you from having to search for the right temporary directory.