Re: [Puppet Users] Re: puppetserver unable to start after yum update

[Matthaus Owens]

John,
Thanks for the correction. I definitely mixed up my words while responding
here.

On Wed, Sep 7, 2016 at 5:54 AM, jcbollinger 
wrote:

>
>
> On Tuesday, September 6, 2016 at 12:22:03 PM UTC-5, Matthaus Litteken
> wrote:
>>
>> [...] In answer to your second question, rpmnew files are for when a
>> configuration file has been changed by the user and a package update
>> changes it. Because yum/rpm can't safely replace the configuration file, it
>> drops an rpmnew version of the file with a diff of the updated config file
>> from the package. This allows the user to manually merge in any needed
>> changes (in this case the needed change is the change to the
>> BOOTSTRAP_CONFIG setting).
>>
>>
> It's at best misleading to describe .rpmnew files as containing a diff.
> An x.rpmnew file is the version of x that RPM would have installed if x had
> no local modifications.  If you don't need to preserve the local
> modifications then you can replace x with x.rpmnew.  Otherwise, you can *make
> your own diff* between the two to judge how to merge the changes.
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/8c9d7ace-dceb-4fc1-bdb7-4955543dfc0e%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CACD%3DwAd9JsZ%2BvVnBr-Uz6Hcq_QN5kiEbYqfy%3DSQ3r2oFv55Dvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppetserver unable to start after yum update

[jcbollinger]

On Tuesday, September 6, 2016 at 12:22:03 PM UTC-5, Matthaus Litteken wrote:
>
> [...] In answer to your second question, rpmnew files are for when a 
> configuration file has been changed by the user and a package update 
> changes it. Because yum/rpm can't safely replace the configuration file, it 
> drops an rpmnew version of the file with a diff of the updated config file 
> from the package. This allows the user to manually merge in any needed 
> changes (in this case the needed change is the change to the 
> BOOTSTRAP_CONFIG setting).
>
>
It's at best misleading to describe .rpmnew files as containing a diff.  An 
x.rpmnew file is the version of x that RPM would have installed if x had no 
local modifications.  If you don't need to preserve the local modifications 
then you can replace x with x.rpmnew.  Otherwise, you can *make your own 
diff* between the two to judge how to merge the changes.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8c9d7ace-dceb-4fc1-bdb7-4955543dfc0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: puppetserver unable to start after yum update

[Matthaus Owens]

Jim,
The puppet server 2.5.0 release had a few changes with respect to
bootstrap.cfg (there are details about it here:
https://docs.puppet.com/puppetserver/2.5/bootstrap_upgrade_notes.html). In
your case it looks like you had modified /etc/sysconfig/puppetserver to
change the heap size, so yum was unable to update your sysconfig file to
point to the new bootstrap config locations (there is some description of
this issue here
https://docs.puppet.com/puppetserver/2.5/release_notes.html#potential-warnings-when-upgrading-with-a-modified-init-configuration).
To get going again, I would recommend updating the BOOTSTRAP_CONFIG setting
in /etc/sysconfig/puppetserver to match what is in
/etc/sysconfig/puppetserver.rpmnew ("/etc/puppetlabs/puppetserver/
services.d/,/opt/puppetlabs/server/apps/puppetserver/config/services.d/").
In answer to your second question, rpmnew files are for when a
configuration file has been changed by the user and a package update
changes it. Because yum/rpm can't safely replace the configuration file, it
drops an rpmnew version of the file with a diff of the updated config file
from the package. This allows the user to manually merge in any needed
changes (in this case the needed change is the change to the
BOOTSTRAP_CONFIG setting).

Hope that helps,
Matthaus

On Sat, Sep 3, 2016 at 6:38 AM, Jim Jim 
wrote:

> Not sure why I am not able to see my email. I don't think it has any
> offensive or rude language ?
>
> On Fri, Sep 2, 2016 at 7:09 PM, Jim Jim 
> wrote:
>
>> 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.boots
>> trap$eval14658$wrap_uri_error__14663$fn__14664.invoke(bootstrap.clj:131)
>> at puppetlabs.trapperkeeper.boots
>> trap$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.boots
>> trap$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__645
>> 2$G__6447__6465.invoke(protocols.clj:13)
>> at clojure.core$reduce.invoke(core.clj:6519)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14944$remove_duplicate_entries__14949$fn__14950.
>> invoke(bootstrap.clj:284)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14944$remove_duplicate_entries__14949.invoke(bootstrap.clj:263)
>> at puppetlabs.trapperkeeper.boots
>> trap$eval14970$parse_bootstrap_configs_BANG___14977$fn__
>> 14978.invoke(bootstrap.clj:304)
>> at puppetlabs.trapperkeeper.boots
>> trap$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)
>>