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

Puppet Server won't start

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • SERVER 5.2.0
    • None
    • Puppet Server
    • CentOS Linux release 7.4.1708

    • Froyo
    • Bug Fix
    • Hide
      > ### Potential service failures when upgrading with a modified init configuration
      >
      > If you modified the init configuration file --- for instance, to [configure Puppet Server's JVM memory allocation](./install_from_packages.html#memory-allocation) or [maximum heap size](./tuning_guide.html) --- and upgrade Puppet Server 2.5.0 or newer with a package manager, you might see a warning during the upgrade that the updated package will overwrite the file (`/etc/sysconfig/puppetserver` in Red Hat and derivatives, or `/etc/default/puppetserver` in Debian-based systems).
      >
      > The changes to the file support the new service bootstrapping behaviors. If you don't accept changes to the file during the upgrade, the puppetserver service fails and you might see a `Service ':PoolManagerService' not found` or similar warning. To resolve the issue, set the `BOOTSTRAP_CONFIG` setting in the init configuration file to:
      >
      > BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/services.d"
      >
      > If you modified other settings in the file before upgrading, and then overwrite the file during the upgrade, you might need to reapply those modifications after the upgrade.
      Show
      > ### Potential service failures when upgrading with a modified init configuration > > If you modified the init configuration file --- for instance, to [configure Puppet Server's JVM memory allocation](./install_from_packages.html#memory-allocation) or [maximum heap size](./tuning_guide.html) --- and upgrade Puppet Server 2.5.0 or newer with a package manager, you might see a warning during the upgrade that the updated package will overwrite the file (`/etc/sysconfig/puppetserver` in Red Hat and derivatives, or `/etc/default/puppetserver` in Debian-based systems). > > The changes to the file support the new service bootstrapping behaviors. If you don't accept changes to the file during the upgrade, the puppetserver service fails and you might see a `Service ':PoolManagerService' not found` or similar warning. To resolve the issue, set the `BOOTSTRAP_CONFIG` setting in the init configuration file to: > > BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/services.d" > > If you modified other settings in the file before upgrading, and then overwrite the file during the upgrade, you might need to reapply those modifications after the upgrade.

    Description

      Looks like this issue is coming up once again but affected by a different file after an upgrade from Puppet Server 4 (puppetserver-2.8.1-1.el7.noarch) to Puppet Server 5 (puppetserver-5.2.0-1.el7.noarch). What happens is the ca.cfg from Puppet Server 2.8.1 is not renamed to .rpmsave and replaced with the new ca.cfg from Puppet 5. 

       

      mv /etc/puppetlabs/puppetserver/services.d/ca.cfg /etc/puppetlabs/puppetserver/services.d/ca.cfg.rpmsave
      mv /etc/puppetlabs/puppetserver/services.d/ca.cfg.rpmnew /etc/puppetlabs/puppetserver/services.d/ca.cfg
      

       

      Below is the error that takes place before the file was changed over from the old to new. 

      Exception in thread "main" java.lang.RuntimeException: Service ':FilesystemWatchService' not found
       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
       at clojure.lang.Reflector.invokeConstructor(Reflector.java:180)
       at puppetlabs.trapperkeeper.internal$handle_prismatic_exception_BANG_.invokeStatic(internal.clj:118)
       at puppetlabs.trapperkeeper.internal$handle_prismatic_exception_BANG_.invoke(internal.clj:108)
       at puppetlabs.trapperkeeper.internal$instantiate$fn__13800.invoke(internal.clj:159)
       at puppetlabs.trapperkeeper.internal$instantiate.invokeStatic(internal.clj:156)
       at puppetlabs.trapperkeeper.internal$instantiate.invoke(internal.clj:149)
       at puppetlabs.trapperkeeper.internal$eval14346$build_app_STAR___14355$fn__14356.invoke(internal.clj:564)
       at puppetlabs.trapperkeeper.internal$eval14346$build_app_STAR___14355.invoke(internal.clj:532)
       at puppetlabs.trapperkeeper.internal$eval14448$boot_services_STAR___14457$fn__14458$fn__14459.invoke(internal.clj:634)
       at puppetlabs.trapperkeeper.internal$eval14448$boot_services_STAR___14457$fn__14458.invoke(internal.clj:633)
       at puppetlabs.trapperkeeper.internal$eval14448$boot_services_STAR___14457.invoke(internal.clj:628)
       at puppetlabs.trapperkeeper.core$eval15279$boot_with_cli_data__15286$fn__15287.invoke(core.clj:131)
       at puppetlabs.trapperkeeper.core$eval15279$boot_with_cli_data__15286.invoke(core.clj:96)
       at puppetlabs.trapperkeeper.core$eval15308$run__15313$fn__15314.invoke(core.clj:152)
       at puppetlabs.trapperkeeper.core$eval15308$run__15313.invoke(core.clj:146)
       at puppetlabs.trapperkeeper.core$main.invokeStatic(core.clj:174)
       at puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:160)
       at clojure.lang.RestFn.invoke(RestFn.java:512)
       at clojure.lang.Var.invoke(Var.java:409)
       at clojure.lang.AFn.applyToHelper(AFn.java:178)
       at clojure.lang.Var.applyTo(Var.java:700)
       at clojure.core$apply.invokeStatic(core.clj:646)
       at clojure.core$apply.invoke(core.clj:641)
       at puppetlabs.trapperkeeper.main$_main.invokeStatic(main.clj:7)
       at puppetlabs.trapperkeeper.main$_main.doInvoke(main.clj:4)
       at clojure.lang.RestFn.invoke(RestFn.java:512)
       at clojure.lang.Var.invoke(Var.java:409)
       at clojure.lang.AFn.applyToHelper(AFn.java:178)
       at clojure.lang.Var.applyTo(Var.java:700)
       at clojure.core$apply.invokeStatic(core.clj:646)
       at clojure.main$main_opt.invokeStatic(main.clj:314)
       at clojure.main$main_opt.invoke(main.clj:310)
       at clojure.main$main.invokeStatic(main.clj:421)
       at clojure.main$main.doInvoke(main.clj:384)
       at clojure.lang.RestFn.invoke(RestFn.java:619)
       at clojure.lang.Var.invoke(Var.java:430)
       at clojure.lang.AFn.applyToHelper(AFn.java:195)
       at clojure.lang.Var.applyTo(Var.java:700)
       at clojure.main.main(main.java:37)
      Background process 6143 exited before start had completed

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              metalcated Mike Gomon
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support