Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #13987 Cannot stop httpd due to tuleap worker
    Actions
    Infos
    #13987
    Thomas Cottier (tcottier)
    2019-10-11 14:21
    2019-10-10 10:01
    15204
    Details
    Cannot stop httpd due to tuleap worker

    When I try to start httpd after starting tuleap service, there are httpd process that prevent httpd to start

    To reproduce:

    • On CentOS 7
    • systemctl stop httpd
    • systemctl stop tuleap
    • systemctl start tuleap
    • systemctl start httpd

    You should have the following state:

    • httpd process trying to stop
    • Unable to restart httpd as previous process are blocking

    Stopping tuleap and starting httpd before solve the problem.

    Other
    11.6
    EL7 (CentOS|RHEL)
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Manuel Vacelet (vaceletm)
    Closed
    2019-10-11
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #13800 Tuleap Releases 11.7 Delivered 2019-10-17 15:09 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #13987

    Git commit

    tuleap/tuleap/stable

    Do not force deploy tuleap-svn-updater everywhere e1a9f6721b
    User avatar Manuel Vacelet (vaceletm) , 2019-10-10 16:19
    Referenced by request #13987

    Artifact Tracker v5

    rel #13800 11.7

    Other

    gerrit #16445
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2019-10-10 10:27

    As a workaround until it's fixed you can disable the service that generate the issue

    systemctl disable tuleap-svn-updater

    • Status changed from New to Under implementation
    User avatar
    Thomas Cottier (tcottier)2019-10-10 10:16
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes