NO_FILE error about supervisord-monitor HOT 4 CLOSED

@najamhaq @VStepulo
Hey, I've solved this warning.

Check your supervisord.conf file.
eg.
[program:test]
process_name=%(program_name)s_%(process_num)02d
...
redirect_stderr=false
stdout_logfile=path_to_stdout_logfile
stderr_logfile=path_to_stderr_logfile

Notice that stderr_logfile is necessary for supervisord-monitor. And DONT set redirect_stderr to true .

If true, cause the process’ stderr output to be sent back to supervisord on its stdout file
http://supervisord.org/configuration.html?highlight=redirect_stderr

from supervisord-monitor.

Hey najamhaq, you still have permission issue - nginx is not reading the logs. Supervisord service is the one that is reading them.

from supervisord-monitor.

Have the same error. In my case Supervisord and supervisord-monitor runs on different servers.

supervisord log on first server have 0777 permissions
worker.log have 0666 permissions

Is there any way to debug this? Can you give me some hints? For example - where I can find log where supervisord-monitor tries to get logs from server with Supervisord and without success?
Or, which permission requires RPC of Supervisord to give logs to your supervisord-monitor?

P. S. Already enabled logs with loglevel - all and didn't find any info in */supervisord-monitor/application/logs/

from supervisord-monitor.

This Worked @sunliver 👍 Thanks.

from supervisord-monitor.