No config file path set by default in 0.20

[hvelarde]

I just upgraded one site from version 0.19 to version 0.20 and got the following error:

$ bin/supervisord
Error: No config file found at default paths (etc/supervisord.conf, supervisord.conf, supervisord.conf, etc/supervisord.conf, /etc/supervisord.conf); use the -c option to specify a config file at a different path
For help, use bin/supervisord -h

Seems to me a regression was caused by #2.

Reverting to 0.19 fixes the issue.

[mauritsvanrees]

For most of our clients, we have been using 0.20 for years. I haven't seen this error.
Sample buildout config:

[supervisor]
recipe = collective.recipe.supervisor
file = ${buildout:directory}/var/supervisor.sock
http-socket = unix
logfile-maxbytes = 5MB
logfile-backups = 5
supervisord-environment = PYTHONUNBUFFERED=true
programs =
    10 zeoserver (startsecs=5 stderr_logfile=NONE stdout_logfile=${buildout:directory}/var/log/zeo-stdout.log) ${zeoserver:location}/bin/runzeo ${zeoserver:location} true
    20 zeoclient (startsecs=10 stderr_logfile=NONE stdout_logfile=${buildout:directory}/var/log/zeoclient-stdout.log) ${buildout:directory}/bin/zeoclient [console] ${zeoclient:location} true
    30 varnish   (startsecs=4 stderr_logfile=NONE stdout_logfile=${buildout:directory}/var/log/varnish-stdout.log) ${buildout:directory}/bin/varnishd true

Sample contents of bin/supervisord:

#!/usr/bin/python2.7

import sys
sys.path[0:0] = [
  '/srv/zope/shared-eggs/supervisor-3.3.3-py2.7.egg',
  '/srv/zope/shared-eggs/setuptools-36.8.0-py2.7.egg',
  '/srv/zope/shared-eggs/meld3-1.0.2-py2.7.egg',
  ]

import sys; sys.argv.extend(["-c","/srv/zope/website/parts/supervisor/supervisord.conf"])

import supervisor.supervisord

if __name__ == '__main__':
    sys.exit(supervisor.supervisord.main())

[hvelarde]

@mauritsvanrees our configuration is this one:

https://github.com/plonegovbr/portal.buildout/blob/2.0b3/production.cfg#L29-L48

we usually add a [supervisor-settings] part like this:

[supervisor-settings]
user = admin
password = admin

@idgserpro can you help me verify this, please?

[hvelarde]

@mauritsvanrees what version of Supervisor are you using?

superlance = 0.14
supervisor = 3.3.4

previously I had:

superlance = 0.11
supervisor = 3.1.4

[mauritsvanrees]

In more recent buildouts we don't use superlance anymore. (I don't even know what it does.) For those that do use it, I see versions ranging from 0.5 to 1.0.0.

For supervisor itself, I see 3.3.3 as highest. You have 3.3.4, but the changelog does not look like that may cause problems. But you could try 3.3.3 to see if that fixes things anyway.

Here is what I have in most buildouts:

[conf]
# var directory, may be overridden on production to share a var directory between releases.
var = ${buildout:directory}/var

[supervisor]
recipe = collective.recipe.supervisor
file = ${conf:var}/supervisord.sock
# Next two are only useful when your var directory is not in the default place
logfile = ${conf:var}/log/supervisord.log
pidfile = ${conf:var}/supervisord.pid
http-socket = unix
logfile-maxbytes = 5MB
logfile-backups = 5
supervisord-environment = PYTHONUNBUFFERED=true
programs =
    10 zeoserver (startsecs=10 stderr_logfile=NONE stdout_logfile=${conf:var}/log/zeo-stdout.log) ${buildout:directory}/bin/zeoserver [fg] true
    20 instance (startsecs=30 stderr_logfile=NONE stdout_logfile=${conf:var}/log/zeoclient.log) ${buildout:directory}/bin/zeoclient [console] true
    30 varnish    (startsecs=10 stderr_logfile=NONE stdout_logfile=${conf:var}/log/varnish-stdout.log) ${buildout:directory}/bin/varnishd true

[versions]
# In one project:
collective.recipe.supervisor = 0.20
superlance = 1.0.0
supervisor = 3.3.1
# In a different project:
collective.recipe.supervisor = 0.20
supervisor = 3.3.3

[hvelarde]

superlance is a collection of plugins for supervisor; we used because it includes the memmon which is a must have in all our Plone deployments.