Petals Registry Overlay

Unable to start Petals registry member using systemd

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.0.2-1.1
  • Component/s: Packaging
  • Security Level: Public
  • Description:
    Hide
    1. I install Petals REgistry member using Debian package,
    2. I add a member into /etc/petals-registry/member-enable,
    3. I execute sudo service petals-registry start or sudo systemctl start petals-registry

    ===>> No registry member is launched, without error

    It is needed to do a restart to have the registry member started.

    Show
    1. I install Petals REgistry member using Debian package,
    2. I add a member into /etc/petals-registry/member-enable,
    3. I execute sudo service petals-registry start or sudo systemctl start petals-registry
    ===>> No registry member is launched, without error It is needed to do a restart to have the registry member started.
  • Environment:
    Ubuntu 16.04 that replaced sysV by systemd, or upper or equivalent Debian

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:20:29 +0100

When installing package, we automatically start the daemon. As no registry member is enable, no registry member is running.

Next, when trying to start the Petals registry member, nothing is done because the daemon is already started (see result of systemctl status petals-registry).

We should remove the starting up during package installation that has no sens because no registry member is enable.

Show
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:20:29 +0100 When installing package, we automatically start the daemon. As no registry member is enable, no registry member is running. Next, when trying to start the Petals registry member, nothing is done because the daemon is already started (see result of systemctl status petals-registry). We should remove the starting up during package installation that has no sens because no registry member is enable.
Christophe DENEUX made changes - Fri, 1 Dec 2017 - 12:20:29 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ]
Christophe DENEUX made changes - Fri, 1 Dec 2017 - 12:20:32 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:23:34 +0100

Fixed in trunk: No more automatic startup during package installation

Show
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:23:34 +0100 Fixed in trunk: No more automatic startup during package installation
Christophe DENEUX made changes - Fri, 1 Dec 2017 - 12:23:34 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.0.2-1.1 [ 10760 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
40s
1
Christophe DENEUX
Fri, 1 Dec 2017 - 12:20:29 +0100
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Fri, 1 Dec 2017 - 12:20:32 +0100
In Progress In Progress Resolved Resolved
3m 2s
1
Christophe DENEUX
Fri, 1 Dec 2017 - 12:23:34 +0100



People

Dates

  • Created:
    Fri, 1 Dec 2017 - 12:19:49 +0100
    Updated:
    Fri, 1 Dec 2017 - 12:23:34 +0100
    Resolved:
    Fri, 1 Dec 2017 - 12:23:34 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.