Changelog History
Page 3
-
v3.2.2 Changes
March 04, 2016- ๐ Parsing the config file will now fail with an error message if an
inet_http_server
orunix_http_server
section contains ausername=
but nopassword=
. In previous versions,supervisord
would start with this invalid configuration but the HTTP server would always return a 500 Internal Server Error. Thanks to Chris Ergatides for reporting this issue.
- ๐ Parsing the config file will now fail with an error message if an
-
v3.2.1 Changes
February 06, 2016- ๐ Fixed a server exception
OverflowError: int exceeds XML-RPC limits
that madesupervisorctl status
unusable if the system time was far into the future. The XML-RPC API returns timestamps as XML-RPC integers, but timestamps will exceed the maximum value of an XML-RPC integer in January 2038 ("Year 2038 Problem"). For now, timestamps exceeding the maximum integer will be capped at the maximum to avoid the exception and retain compatibility with existing API clients. In a future version of the API, the return type for timestamps will be changed.
- ๐ Fixed a server exception
-
v3.2.0 Changes
November 30, 2015Files included via the
[include]
section are read in sorted order. In past versions, the order was undefined. Patch by Ionel Cristian Mฤrieศ.supervisorctl start
andsupervisorctl stop
now complete more quickly when handling many processes. Thanks to Chris McDonough for this patch. See: https://github.com/Supervisor/supervisor/issues/131Environment variables are now expanded for all config file options. Patch by Dexter Tad-y.
โ Added
signalProcess
,signalProcessGroup
, andsignalAllProcesses
XML-RPC methods to supervisor RPC interface. Thanks to Casey Callendrello, Marc Abramowitz, and Moriyoshi Koizumi for the patches.โ Added
signal
command to supervisorctl. Thanks to Moriyoshi Koizumi and Marc Abramowitz for the patches.Errors caused by bad values in a config file now show the config section to make debugging easier. Patch by Marc Abramowitz.
Setting
redirect_stderr=true
in an[eventlistener:x]
section is now disallowed because any messages written tostderr
would interfere with the eventlistener protocol onstdout
.๐ Fixed a bug where spawning a process could cause
supervisord
to crash if anIOError
occurred while setting up logging. One way this could happen is if a log filename was accidentally set to a directory instead of a file. Thanks to Grzegorz Nosek for reporting this issue.๐ Fixed a bug introduced in 3.1.0 where
supervisord
could crash when attempting to display a resource limit error.๐ Fixed a bug where
supervisord
could crash with the messageAssertion failed for processname: RUNNING not in STARTING
if a time change caused the last start time of the process to be in the future. Thanks to Rรณbert Nagy, Sergey Leschenko, and samhair for the patches.โ A warning is now logged if an eventlistener enters the UNKNOWN state, which usually indicates a bug in the eventlistener. Thanks to Steve Winton and detailyang for reporting issues that led to this change.
๐ Errors from the web interface are now logged at the
ERROR
level. Previously, they were logged at theTRACE
level and easily missed. Thanks to Thomas Gรผttler for reporting this issue.๐ Fixed
DeprecationWarning: Parameters to load are deprecated. Call .resolve and .require separately.
on setuptools >= 11.3.If
redirect_stderr=true
andstderr_logfile=auto
, no stderr log file will be created. In previous versions, an empty stderr log file would be created. Thanks to ลukasz Koลผuchowski for the initial patch.๐ Fixed an issue in Medusa that would cause
supervisorctl tail -f
to disconnect if many othersupervisorctl
commands were run in parallel. Patch by Stefan Friesel.
-
v3.1.4 Changes
July 24, 2017- ๐ Backported from Supervisor 3.3.3: Fixed CVE-2017-11610. A vulnerability
was found where an authenticated client can send a malicious XML-RPC request
to
supervisord
that will run arbitrary shell commands on the server. The commands will be run as the same user assupervisord
. Depending on howsupervisord
has been configured, this may be root. See https://github.com/Supervisor/supervisor/issues/964 for details.
- ๐ Backported from Supervisor 3.3.3: Fixed CVE-2017-11610. A vulnerability
was found where an authenticated client can send a malicious XML-RPC request
to
-
v3.1.3 Changes
October 28, 2014- ๐ Fixed an XML-RPC bug where the ElementTree-based parser handled strings
like
<value><string>hello</string></value>
but not strings like<value>hello</value>
, which are valid in the XML-RPC spec. This fixes compatibility with the Apache XML-RPC client for Java and possibly other clients.
- ๐ Fixed an XML-RPC bug where the ElementTree-based parser handled strings
like
-
v3.1.2 Changes
September 07, 2014๐ Fixed a bug where
tail group:*
insupervisorctl
would show a 500 Internal Server Error rather than a BAD_NAME fault.๐ Fixed a bug where the web interface would show a 500 Internal Server Error instead of an error message for some process start faults.
โ Removed medusa files not used by Supervisor.
-
v3.1.1 Changes
August 11, 2014๐ Fixed a bug where
supervisorctl tail -f name
output would stop if log rotation occurred while tailing.Prevent a crash when a greater number of file descriptors were attempted to be opened than permitted by the environment when starting a bunch of programs. Now, instead a spawn error is logged.
Compute "channel delay" properly, fixing symptoms where a supervisorctl start command would hang for a very long time when a process (or many processes) are spewing to their stdout or stderr. See comments attached to https://github.com/Supervisor/supervisor/pull/263 .
โ Added
docs/conf.py
,docs/Makefile
, andsupervisor/scripts/*.py
to the release package.
-
v3.1.0 Changes
July 29, 2014The output of the
start
,stop
,restart
, andclear
commands insupervisorctl
has been changed to be consistent with thestatus
command. Previously, thestatus
command would show a process likefoo:foo_01
but starting that process would showfoo_01: started
(note the group prefixfoo:
was missing). Now, starting the process will showfoo:foo_01: started
. Suggested by Chris Wood.๐ The
status
command insupervisorctl
now supports group name syntax:status group:*
.The process column in the table output by the
status
command insupervisorctl
now expands to fit the widest name.โก๏ธ The
update
command insupervisorctl
now accepts optional group names. When group names are specified, only those groups will be updated. Patch by Gary M. Josack.Tab completion in
supervisorctl
has been improved and now works for more cases. Thanks to Mathieu Longtin and Marc Abramowitz for the patches.Attempting to start or stop a process group in
supervisorctl
with thegroup:*
syntax will now show the same error message as theprocess
syntax if the name does not exist. Previously, it would show a Python exception. Patch by George Ang.Added new
PROCESS_GROUP_ADDED
andPROCESS_GROUP_REMOVED
events. These events are fired when process groups are added or removed from Supervisor's runtime configuration when using theadd
andremove
commands insupervisorctl
. Patch by Brent Tubbs.Stopping a process in the backoff state now changes it to the stopped state. Previously, an attempt to stop a process in backoff would be ignored. Patch by Pascal Varet.
The
directory
option is now expanded separately for each process in a homogeneous process group. This allows each process to have its own working directory. Patch by Perttu Ranta-aho.โ Removed
setuptools
from therequires
list insetup.py
because it caused installation issues on some systems.๐ Fixed a bug in Medusa where the HTTP Basic authorizer would cause an exception if the password contained a colon. Thanks to Thomas Gรผttler for reporting this issue.
๐ Fixed an XML-RPC bug where calling supervisor.clearProcessLogs() with a name like
group:*
would cause a 500 Internal Server Error rather than returning a BAD_NAME fault.๐ Fixed a hang that could occur in
supervisord
if log rotation is used and an outside program deletes an active log file. Patch by Magnus Lycka.โ A warning is now logged if a glob pattern in an
[include]
section does not match any files. Patch by Daniel Hahler.
-
v3.0.1 Changes
July 24, 2017- ๐ Backported from Supervisor 3.3.3: Fixed CVE-2017-11610. A vulnerability
was found where an authenticated client can send a malicious XML-RPC request
to
supervisord
that will run arbitrary shell commands on the server. The commands will be run as the same user assupervisord
. Depending on howsupervisord
has been configured, this may be root. See https://github.com/Supervisor/supervisor/issues/964 for details.
- ๐ Backported from Supervisor 3.3.3: Fixed CVE-2017-11610. A vulnerability
was found where an authenticated client can send a malicious XML-RPC request
to
-
v3.0 Changes
July 30, 2013๐ Parsing the config file will now fail with an error message if a process or group name contains characters that are not compatible with the eventlistener protocol.
๐ Fixed a bug where the
tail -f
command insupervisorctl
would fail if the combined length of the username and password was over 56 characters.Reading the config file now gives a separate error message when the config file exists but can't be read. Previously, any error reading the file would be reported as "could not find config file". Patch by Jens Rantil.
๐ Fixed an XML-RPC bug where array elements after the first would be ignored when using the ElementTree-based XML parser. Patch by Zev Benjamin.
๐ Fixed the usage message output by
supervisorctl
to show the correct default config file path. Patch by Alek Storm.