Ticket #12289 (confirmed Bug)

Opened 4 years ago

Last modified 4 years ago

"bin/instance start" and "bin/instance stop" don't work on windows since 4.1

Reported by: kleist Owned by: runyaga
Priority: minor Milestone: 4.x
Component: Installers Version: 4.1
Keywords: windows Cc:

Description

reported on #plone: "bin/instance start" and "bin/instance stop" don't work on windows since 4.1 (maybe because the windows service has changed name from "zope" to "plone"?

Change History

comment:1 Changed 4 years ago by anthonygerrard

I have "bin/instance start" and "bin/instance stop" working on my development laptop with Plone 4.1.

I installed the windows service using "bin/instance install" rather than using the installer - this is definitely an installer issue I think.

comment:2 Changed 4 years ago by smcmahon

  • Owner changed from smcmahon to runyaga

comment:3 Changed 4 years ago by kleist

  • Status changed from new to confirmed
  • Version set to 4.1

comment:4 Changed 4 years ago by kleist

After having used the Plone 4.2 Windows installer, two services have been installed: "Plone 4.2" and "Plone 4.2 Zeo". (Note that the pre-4.0.9 installer didn't install ZEO.)

So a fix might include amending plone.recipe.zope2instance.ctl.AdjustedZopeCmd._get_service_name():

 https://github.com/plone/plone.recipe.zope2instance/blob/master/src/plone/recipe/zope2instance/ctl.py#L85

No idea from where the correct service name should be fetched, however.

Note: See TracTickets for help on using tickets.