Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-557

puppetserver fails to start, TimeoutStartSec=120 is too short

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: SERVER 2.0.0
    • Fix Version/s: SERVER 2.4.0
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Server Emerald 2016-03-23

      Description

      I have the problem that starting puppetserver fails because the 120 seconds systemd timeout is reached.
      The TimeoutStartSec=120 in /usr/lib/systemd/system/puppetserver.service is too short.
      That value is also not configurable via /etc/sysconfig/puppetserver.

      I'm experimenting with running puppetserver 2.0.0 in a Vagrant VM, the initial run fails around half of the time.
      Normal restarts after the initial run come also very close to the timeout:

      [root@puppet ~]# time systemctl start puppetserver.service
       
      real    1m18.108s
      user    0m0.011s
      sys     0m0.021s
      

      Tested on CentOS 7.

      I think that value should be raised and also made configurable.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  chris Chris Price
                  Reporter:
                  faker Roman Mueller
                  QA Contact:
                  Erik Dasher
                • Votes:
                  3 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support