Ticket #13477 (confirmed Bug)

Opened 3 years ago

Last modified 3 years ago

bin/restart fails after running buildout

Reported by: kleist Owned by:
Priority: major Milestone: 4.x
Component: Backend (Python) Version: 4.2
Keywords: buildout, restart, upstream Cc:

Description

Quoting Mikko Ohtamaa in  http://plone.293351.n2.nabble.com/Mitigate-broken-bin-instance-restart-command-issues-tt7563719.html:

According to [...]  http://stackoverflow.com/a/15292967/315168 bin/restart does not function after running buildout. Observations prove this is the case.

Because bin/instance (bin/plonectl) restart is natural way to restart Plone and we cannot guarantee its to success we have been shipping non-working restart since Plone 3.

So, I suggest we fix the issue is it causes confusion and grief early Plone adaptors and even seasoned developers

  • Remove restart command if doesn't work with buildout
  • Fix it by somehow (mapping to bin/start, bin/stop)
  • Make restart command detect conditions where it cannot success and exit with failure

Change History

comment:1 Changed 3 years ago by kleist

  • Status changed from new to confirmed
  • Priority changed from minor to major
  • Component changed from Unknown to Backend (Python)

comment:2 Changed 3 years ago by kleist

  • Keywords restart, upstream added; restart removed

This is a Zope feature, known for years:

 https://bugs.launchpad.net/zdaemon/+bug/489159

Last edited 3 years ago by kleist (previous) (diff)
Note: See TracTickets for help on using tickets.