Ask Your Question
0

Unable to start puppetserver after "yum update"

asked 2016-09-01 19:45:20 -0500

newcomer gravatar image

updated 2016-09-01 19:48:00 -0500

Hi Guys,

I had a good running puppetserver daemon but after

sudo yum update -y

It is not running, complaining Specified bootstrap config file does not exist: '/etc/puppetlabs/puppetserver/bootstrap.cfg'. detailed log output from puppetserver-daemon.log is as below:

OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Exception in thread "main" java.lang.IllegalArgumentException: Specified bootstrap config file does not exist: '/etc/puppetlabs/puppetserver/bootstrap.cfg'
        at puppetlabs.trapperkeeper.bootstrap$eval14658$wrap_uri_error__14663$fn__14664.invoke(bootstrap.clj:131)
        at puppetlabs.trapperkeeper.bootstrap$eval14658$wrap_uri_error__14663.invoke(bootstrap.clj:127)
        at puppetlabs.trapperkeeper.bootstrap$eval14681$read_config__14686$fn__14687.invoke(bootstrap.clj:150)
        at puppetlabs.trapperkeeper.bootstrap$eval14681$read_config__14686.invoke(bootstrap.clj:134)
        at puppetlabs.trapperkeeper.bootstrap$eval14704$get_annotated_bootstrap_entries__14709$fn__14710$iter__14711__14717$fn__14718.invoke(bootstrap.clj:160)
        at clojure.lang.LazySeq.sval(LazySeq.java:40)
        at clojure.lang.LazySeq.seq(LazySeq.java:49)
        at clojure.lang.RT.seq(RT.java:507)
        at clojure.core$seq__4128.invoke(core.clj:137)
        at clojure.core.protocols$seq_reduce.invoke(protocols.clj:30)
        at clojure.core.protocols$fn__6506.invoke(protocols.clj:101)
        at clojure.core.protocols$fn__6452$G__6447__6465.invoke(protocols.clj:13)
        at clojure.core$reduce.invoke(core.clj:6519)
        at puppetlabs.trapperkeeper.bootstrap$eval14944$remove_duplicate_entries__14949$fn__14950.invoke(bootstrap.clj:284)
        at puppetlabs.trapperkeeper.bootstrap$eval14944$remove_duplicate_entries__14949.invoke(bootstrap.clj:263)
        at puppetlabs.trapperkeeper.bootstrap$eval14970$parse_bootstrap_configs_BANG___14977$fn__14978.invoke(bootstrap.clj:304)
        at puppetlabs.trapperkeeper.bootstrap$eval14970$parse_bootstrap_configs_BANG___14977.invoke(bootstrap.clj:293)
        at puppetlabs.trapperkeeper.core$eval15252$boot_with_cli_data__15259$fn__15260.invoke(core.clj:129)
        at puppetlabs.trapperkeeper.core$eval15252$boot_with_cli_data__15259.invoke(core.clj:95)
        at puppetlabs.trapperkeeper.core$eval15281$run__15286$fn__15287.invoke(core.clj:151)
        at puppetlabs.trapperkeeper.core$eval15281$run__15286.invoke(core.clj:145)
        at puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:173)
        at clojure.lang.RestFn.invoke(RestFn.java:457)
        at clojure.lang.Var.invoke(Var.java:394)
        at clojure.lang.AFn.applyToHelper(AFn.java:165)
        at clojure.lang.Var.applyTo(Var.java:700)
        at clojure.core$apply.invoke(core.clj:630)
        at puppetlabs.trapperkeeper.main$_main.doInvoke(main.clj:7)
        at clojure.lang.RestFn.invoke(RestFn.java:457)
        at clojure.lang.Var.invoke(Var.java:394)
        at clojure.lang.AFn.applyToHelper(AFn.java:165)
        at clojure.lang.Var.applyTo(Var.java:700)
        at clojure.core$apply.invoke(core.clj:630)
        at clojure.main$main_opt.invoke(main.clj:316)
        at clojure.main$main.doInvoke(main.clj:421)
        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.main.main(main.java:37)
Caused by: java.lang.IllegalArgumentException: URI is not absolute
        at java.net.URI.toURL(URI.java:1088)
        at clojure.java.io$fn__9197.invoke(io.clj:248)
        at clojure.java.io$fn__9102$G__9095__9109.invoke(io.clj:69)
        at clojure.java.io$fn__9163.invoke(io.clj:165)
        at clojure.java.io$fn__9115$G__9091__9122.invoke(io.clj:69)
        at clojure.java.io$reader.doInvoke(io.clj:102)
        at ...
(more)
edit retag flag offensive close merge delete

Comments

Found bootstrap.cfg here: [root@puppet /]# find / -xdev -type f -iname "bootstrap.cfg" /opt/puppetlabs/server/apps/puppetserver/config/services.d/bootstrap.cfg [root@puppet /]#

newcomer gravatar imagenewcomer ( 2016-09-01 20:02:47 -0500 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2016-09-10 18:29:09 -0500

camlow325 gravatar image

This appears to be the same question which was filed as SERVER-1542. I've included below some portions of the comment I had left on that ticket.

It sounds like you have encountered the scenario documented in the Puppet Server 2.5.0 release notes here.

For the Puppet Server 2.5.0 release, the bootstrap.cfg file has been split into separate .cfg files across two directories – /etc/puppetlabs/puppetserver/services.d/ and /opt/puppetlabs/server/apps/puppetserver/config/services.d/ – whereas the original file at /etc/puppetlabs/puppetserver/bootstrap.cfg has been deleted. Because the BOOTSTRAP_CONFIG variable from the puppetserver.conf file was not updated to include the new directory paths, Puppet Server fails to start with the error message that you mentioned in the description:

...Specified bootstrap config file does not exist: '/etc/puppetlabs/puppetserver/bootstrap.cfg'.

In order for your Puppet Server to start properly, you probably would just need to change the BOOTSTRAP_CONFIG variable in the /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf file to..

BOOTSTRAP_CONFIG="/etc/puppetlabs/puppetserver/services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/"

... and then restart the puppetserver service.

You may also want to read through the Puppet Server 2.5.0 release notes for more information on the precautions to take when upgrading.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2016-09-01 19:45:20 -0500

Seen: 139 times

Last updated: Sep 10 '16