Petals ESB Container

Unable to start Petals containers using systemd

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.2
  • Fix Version/s: 5.1.0
  • Component/s: Packaging
  • Security Level: Public
  • Description:
    Hide
    1. I install Petals ESB using Debian package,
    2. I add a container into /etc/petals-esb/container-enable,
    3. I execute sudo service petals-esb start or sudo systemctl start petals-esb

    ===>> No container is launched, without error

    It is needed to do a restart to have the container started.

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

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:17:36 +0100

Fixed in trunk: No more automatic startup during package installation

Show
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:17:36 +0100 Fixed in trunk: No more automatic startup during package installation
Hide
Permalink
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:16:18 +0100

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

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

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

Show
Christophe DENEUX added a comment - Fri, 1 Dec 2017 - 12:16:18 +0100 When installing package, we automatically start the daemon. As no container is enable, no container is running. Next, when trying to start the Petals container, nothing is done because the daemon is already started (see result of systemctl status petals-esb). We should remove the starting up during package installation that has no sens because no container is enable.

People

Dates

  • Created:
    Fri, 1 Dec 2017 - 12:13:43 +0100
    Updated:
    Fri, 1 Dec 2017 - 12:17:36 +0100
    Resolved:
    Fri, 1 Dec 2017 - 12:17:36 +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.