Puppet Server Stop After OS Update

Support
1

Hello. Im using Centos 7.2 and after an update, the puppet servers stop
loading. I have this error:

Sep 14 14:13:15 java: Exception in thread "main" java.lang.IllegalArgumentException:
service
:puppetlabs.trapperkeeper.services.status.status-service/status-service
does not appear in configuration
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke(webrouting_service_core.clj:55)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_route.invoke(webrouting_service_core.clj:99)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$reify__25542$service_fnk__5223__auto___positional$reify__25550.get_route(webrouting_service.clj:37)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval25272$fn__25436$G__25256__25442.invoke(webrouting_service.clj:10)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval25272$fn__25436$G__25255__25449.invoke(webrouting_service.clj:10)
Sep 14 14:13:15 java: at clojure.core$partial$fn__4527.invoke(core.clj:2493)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services.status.status_service$reify__36201$service_fnk__5223__auto___positional$reify__36208.start(status_service.clj:31)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services$eval5025$fn__5039$G__5015__5042.invoke(services.clj:8)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.services$eval5025$fn__5039$G__5014__5046.invoke(services.clj:8)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval13757$run_lifecycle_fn_BANG___13764$fn__13765.invoke(internal.clj:200)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval13757$run_lifecycle_fn_BANG___13764.invoke(internal.clj:183)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval13786$run_lifecycle_fns__13791$fn__13792.invoke(internal.clj:234)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval13786$run_lifecycle_fns__13791.invoke(internal.clj:211)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval14257$build_app_STAR___14266$fn$reify__14276.start(internal.clj:587)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval14303$boot_services_for_app_STAR__STAR___14310$fn__14311$fn__14313.invoke(internal.clj:613)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval14303$boot_services_for_app_STAR__STAR___14310$fn__14311.invoke(internal.clj:611)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval14303$boot_services_for_app_STAR__STAR___14310.invoke(internal.clj:605)
Sep 14 14:13:15 java: at clojure.core$partial$fn__4529.invoke(core.clj:2499)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval13825$initialize_lifecycle_worker__13836$fn__13837$fn__13924$state_machine__11796__auto____13925$fn__13927.invoke(internal.clj:251)
Sep 14 14:13:15 java: at
puppetlabs.trapperkeeper.internal$eval13825$initialize_lifecycle_worker__13836$fn__13837$fn__13924$state_machine__11796__auto____13925.invoke(internal.clj:251)
Sep 14 14:13:15 java: at
clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:1011)
Sep 14 14:13:15 java: at
clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:1015)
Sep 14 14:13:15 java: at
clojure.core.async$ioc_alts_BANG_$fn__11964.invoke(async.clj:378)
Sep 14 14:13:15 java: at
clojure.core.async$do_alts$fn__11910$fn__11913.invoke(async.clj:247)
Sep 14 14:13:15 java: at
clojure.core.async.impl.channels.ManyToManyChannel$fn__6731$fn__6732.invoke(channels.clj:95)
Sep 14 14:13:15 java: at clojure.lang.AFn.run(AFn.java:22)
Sep 14 14:13:15 java: at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Sep 14 14:13:15 java: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Sep 14 14:13:15 java: at java.lang.Thread.run(Thread.java:745)
Sep 14 14:13:15 systemd: puppetserver.service: main process exited,
code=exited, status=1/FAILURE
Sep 14 14:13:15 systemd: puppetserver.service: control process exited,
code=exited status=1
Sep 14 14:13:15 systemd: Failed to start puppetserver Service.
Sep 14 14:13:15 systemd: Unit puppetserver.service entered failed state.
Sep 14 14:13:15 systemd: puppetserver.service failed.
Sep 14 14:13:15 systemd: puppetserver.service holdoff time over, scheduling
restart.
Sep 14 14:13:15 systemd: Starting puppetserver Service…

I have modified the file web-routes.conf.erb and added the text:
(https://github.com/theforeman/puppet-puppet/blob/master/templates/server/puppetserver/conf.d/web-routes.conf.erb#L17-L21)
<%- if scope.function_versioncmp([@server_puppetserver_version, '2.6']) >= 0
-%>

This controls the mount point for the status API

"puppetlabs.trapperkeeper.services.status.status-service/status-service":
"/status"
<%- end -%>

Still not working. I appreciate any help.
Thank you.

2

> Hello. Im using Centos 7.2 and after an update, the puppet servers stop
> loading. I have this error:

It's likely that you updated to Puppet Server 2.6.0.

> Sep 14 14:13:15 java: Exception in thread "main"
> java.lang.IllegalArgumentException: service
> :puppetlabs.trapperkeeper.services.status.status-service/status-service
> does not appear in configuration

Add to /etc/puppetlabs/puppetserver/conf.d/web-routes.conf:

"puppetlabs.trapperkeeper.services.status.status-service/status-service":
"/status"

> I have modified the file web-routes.conf.erb and added the text:
> (https://github.com/theforeman/puppet-puppet/blob/master/templates/server/puppetserver/conf.d/web-routes.conf.erb#L17-L21)
[…]
> Still not working. I appreciate any help.
> Thank you.

The file I'm guessing you might have edited (hard to say without knowing
the full path) is part of the Foreman installer. Did you run the
Foreman installer after editing it?

You would need to run it with --puppet-server-puppetserver-version=2.6.0
to apply this 2.6-style configuration.

··· On 14/09/16 18:23, Marcio Costa wrote:

–
Dominic Cleal
dominic@cleal.org

3

Just ran into this issue upgrading from Foreman 1.12 to 1.13 as the test
node also had the puppetlabs-pc1 repo installed.

Setting the puppetserver version worked like a charm.

Thanks!

··· On Thursday, September 15, 2016 at 3:01:07 AM UTC-5, Dominic Cleal wrote: > > On 14/09/16 18:23, Marcio Costa wrote: > > Hello. Im using Centos 7.2 and after an update, the puppet servers stop > > loading. I have this error: > > It's likely that you updated to Puppet Server 2.6.0. > > > Sep 14 14:13:15 java: Exception in thread "main" > > *java.lang.IllegalArgumentException: service > > :puppetlabs.trapperkeeper.services.status.status-service/status-service > > does not appear in configuration* > > Add to /etc/puppetlabs/puppetserver/conf.d/web-routes.conf: > > "puppetlabs.trapperkeeper.services.status.status-service/status-service": > "/status" > > > I have modified the file *web-routes.conf.erb* and added the text: > > ( > https://github.com/theforeman/puppet-puppet/blob/master/templates/server/puppetserver/conf.d/web-routes.conf.erb#L17-L21) > > [..] > > Still not working. I appreciate any help. > > Thank you. > > The file I'm guessing you might have edited (hard to say without knowing > the full path) is part of the Foreman installer. Did you _run_ the > Foreman installer after editing it? > > You would need to run it with --puppet-server-puppetserver-version=2.6.0 > to apply this 2.6-style configuration. > > -- > Dominic Cleal > dom...@cleal.org >