CHANGES.txt 3.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. 2.1
  2. - When supervisord was invoked more than once, and its configuration
  3. was set up to use a UNIX domain socket as the HTTP server, the
  4. socket file would be erased in error. The symptom of this was
  5. that a subsequent invocation of supervisorctl could not find the
  6. socket file, so the process could not be controlled (it and all of
  7. its subprocesses would need to be killed by hand).
  8. - When a process was not killable with a "normal" signal at shutdown
  9. time, too many "INFO: waiting for x to die" messages would be sent
  10. to the log until we ended up killing the process with a SIGKILL.
  11. Now a maximum of one every three seconds is sent up until SIGKILL
  12. time. Thanks to Ian Bicking.
  13. - Add an assertion: we never want to try to marshal None to XML-RPC
  14. callers. Issue 223 in the collector from vgatto indicates that
  15. somehow a supervisor XML-RPC method is returning None (which
  16. should never happen), but I cannot identify how. Maybe the
  17. assertion will give us more clues if it happens again.
  18. - Supervisor would crash when run under Python 2.5 because the
  19. xmlrpclib.Transport class in Python 2.5 changed in a
  20. backward-incompatible way. Thanks to Eric Westra for the bug
  21. report and a fix.
  22. - Tests now pass under Python 2.5.
  23. 2.1b2
  24. - Added new tailProcessLog() command to the XML-RPC API that
  25. is more efficient for just tailing than the existing
  26. readProcessLog() command (Mike Naberezny).
  27. 2.1b1
  28. - "supervisord -h" and "supervisorctl -h" did not work (traceback
  29. instead of showing help view (thanks to Damjan from Macedonia for
  30. the bug report).
  31. - Processes which started successfully after failing to start
  32. initially are no longer reported in BACKOFF state once they are
  33. started successfully (thanks to Damjan from Macdonia for the bug
  34. report).
  35. - Add new 'maintail' command to supervisorctl shell, which allows
  36. you to tail the 'main' supervisor log. This uses a new
  37. readMainLog xmlrpc API.
  38. - Various process-state-transition related changes, all internal.
  39. README.txt updated with new state transition map.
  40. - startProcess and startAllProcesses xmlrpc APIs changed: instead of
  41. accepting a timeout integer, these accept a wait boolean (timeout
  42. is implied by process' "startsecs" configuration). If wait is
  43. False, do not wait for startsecs.
  44. Known issues:
  45. Code does not match state transition map. Processes which are
  46. configured as autorestarting which start "successfully" but
  47. subsequently die after 'startsecs' go through the transitions
  48. RUNNING -> BACKOFF -> STARTING instead of the correct transitions
  49. RUNNING -> EXITED -> STARTING. This has no real negative effect,
  50. but should be fixed for correctness.
  51. 2.0
  52. - pidfile written in daemon mode had incorrect pid.
  53. - supervisorctl: tail (non -f) did not pass through proper error
  54. messages when supplied by the server.
  55. - Log signal name used to kill processes at debug level.
  56. - supervisorctl "tail -f" didn't work with supervisorctl sections
  57. configured with an absolute unix:// URL
  58. - New "environment" config file option allows you to add environment
  59. variable values to supervisord environment from config file.
  60. 2.0b1
  61. - fundamental rewrite based on 1.0.6, use distutils (only) for
  62. installation, use ConfigParser rather than ZConfig, use HTTP for
  63. wire protocol, web interface, less lies in supervisorctl.