•  
      request #17113 Workers complain they cannot write their lock file after a reboot
    Infos
    #17113
    Thomas Gerbet (tgerbet)
    2020-10-05 11:32
    2020-09-25 13:12
    17858
    Details
    Workers complain they cannot write their lock file after a reboot
    After a reboot of a server hosting a Tuleap instance the workers complain they cannot write their lock file. /var/run/tuleap folder is not recreated on boot.



    Trace:
    Sep 25 06:18:35 41b56fc375a5 worker.php[221]: PHP Warning: file_put_contents(/var/run/tuleap/worker.pid): failed to open stream: No such file or directory in /usr/share/tuleap/src/common/System/DaemonLocker.php on line 54
    Sep 25 06:18:35 41b56fc375a5 worker.php[221]: PHP Stack trace:
    Sep 25 06:18:35 41b56fc375a5 worker.php[221]: PHP 1. {main}() /usr/share/tuleap/src/utils/worker.php:0
    Sep 25 06:18:35 41b56fc375a5 worker.php[221]: PHP 2. Tuleap\Queue\Worker->main() /usr/share/tuleap/src/utils/worker.php:26
    Sep 25 06:18:35 41b56fc375a5 worker.php[221]: PHP 3. Tuleap\System\DaemonLocker->isRunning() /usr/share/tuleap/src/common/Queue/Worker.php:71
    Sep 25 06:18:35 41b56fc375a5 worker.php[221]: PHP 4. file_put_contents() /usr/share/tuleap/src/common/System/DaemonLocker.php:54
    Empty
    Other
    All
    CentOS 7
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2020-10-05
    Attachments
    Empty
    References

    List of items referenced by or referencing this item.

    Artifact Tracker v5

    Follow-ups