[Puppet Users] Re: upgrade puppet client

[Joseph Mwesigwa Bbaale]

UPDATE:

I have used this...

package { puppet:
   ensure => latest,
   }

...but I get this...

warning: Could not retrieve fact fqdn
err: /Stage[main]//Package[puppet]/ensure: change from 2.7.18-5 to 
3.2.4-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get 
-q -y -o DPkg::Options::=--force-confold install puppet' returned 100: 
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  facter hiera libruby puppet-common ruby-rgen virt-what
Suggested packages:
  puppet-el vim-puppet ruby-selinux libselinux-ruby1.8 librrd-ruby1.9.1
  librrd-ruby1.8
The following NEW packages will be installed:
  hiera libruby ruby-rgen virt-what
The following packages will be upgraded:
  facter puppet puppet-common
3 upgraded, 4 newly installed, 0 to remove and 21 not upgraded.
Need to get 1241 kB of archives.
After this operation, 1798 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian/ wheezy/main virt-what amd64 1.12-1 
[12.9 kB]
Get:2 http://ftp.de.debian.org/debian/ wheezy/main libruby all 1:1.9.3 
[6218 B]
Get:3 http://apt.puppetlabs.com/ wheezy/main facter amd64 
1.7.3-1puppetlabs1 [75.2 kB]
Get:4 http://apt.puppetlabs.com/ wheezy/main hiera all 1.2.1-1puppetlabs1 
[18.7 kB]
Get:5 http://apt.puppetlabs.com/ wheezy/dependencies ruby-rgen all 
0.6.5-1puppetlabs1 [82.3 kB]
Get:6 http://apt.puppetlabs.com/ wheezy/main puppet all 3.2.4-1puppetlabs1 
[68.4 kB]
Get:7 http://apt.puppetlabs.com/ wheezy/main puppet-common all 
3.2.4-1puppetlabs1 [977 kB]
Fetched 1241 kB in 3s (332 kB/s)
Selecting previously unselected package virt-what.
(Reading database ... 41033 files and directories currently installed.)
Unpacking virt-what (from .../virt-what_1.12-1_amd64.deb) ...
Preparing to replace facter 1.6.10-1 (using 
.../facter_1.7.3-1puppetlabs1_amd64.deb) ...
Unpacking replacement facter ...
Selecting previously unselected package libruby.
Unpacking libruby (from .../libruby_1%3a1.9.3_all.deb) ...
Selecting previously unselected package hiera.
Unpacking hiera (from .../hiera_1.2.1-1puppetlabs1_all.deb) ...
Selecting previously unselected package ruby-rgen.
Unpacking ruby-rgen (from .../ruby-rgen_0.6.5-1puppetlabs1_all.deb) ...
Preparing to replace puppet 2.7.18-5 (using 
.../puppet_3.2.4-1puppetlabs1_all.deb) ...
Stopping puppet agent.
Unpacking replacement puppet ...
dpkg: error processing 
/var/cache/apt/archives/puppet_3.2.4-1puppetlabs1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man8/puppet-kick.8.gz', which is also 
in package puppet-common 2.7.18-5
insserv: warning: script 'jetty' missing LSB tags and overrides
Starting puppet agent.
Preparing to replace puppet-common 2.7.18-5 (using 
.../puppet-common_3.2.4-1puppetlabs1_all.deb) ...
Unpacking replacement puppet-common ...
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/puppet_3.2.4-1puppetlabs1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
 at /tmp/puppetugrade.pp:3
notice: Finished catalog run in 9.13 seconds

Any help is highly appreciated

On Thursday, 19 September 2013 11:50:33 UTC+3, Joseph Mwesigwa Bbaale wrote:
>
> Hi,
>
> I have a puppet client running 2.7.18
> I wish to upgrade it to 3.2 but I am not sure how to go about it.
>
> OS = Debian Wheezy
>
> Thanks in advance
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] upgrade puppet client

[Joseph Mwesigwa Bbaale]

Hi,

I have a puppet client running 2.7.18
I wish to upgrade it to 3.2 but I am not sure how to go about it.

OS = Debian Wheezy

Thanks in advance

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: a different ssh::auth problem

[Joseph Mwesigwa Bbaale]

Hi Stephen,

Thank you so much for the clarification.
I am going to the documents that you have recommended.

Regards,

Joseph

On Monday, 29 July 2013 20:26:41 UTC+3, Stephen Brown II wrote:
>
> Greetings,
>
> I'm also new to puppet, but the documentation is basically informing you 
> about the way puppet modules are laid out. From the Puppet documentation (
> http://docs.puppetlabs.com/puppet/3/reference/modules_fundamentals.html):
> On disk, a module is simply a directory tree with a specific, predictable 
> structure:
>
> MODULE NAME
> |--manifests
> |--files
> |--templates
> |--lib
> |--tests
> \--spec1
>
> So it is perfectly fine for you to create the ssh/manifests directory and 
> place the auth.pp file in there. That's where Puppet expects it to be.
>
> I'd recommend going through the Puppet reference to get more information 
> on it, and possbly trying out the Learning Puppet VM Tutorial (
> http://docs.puppetlabs.com/learning/), which also has a section on 
> Modules and Classes (http://docs.puppetlabs.com/learning/modules1.html)
>
> Hope this helps!
> Stephen
>
> On Monday, July 29, 2013 4:12:48 AM UTC-4, Joseph Mwesigwa Bbaale wrote:
>>
>> Hi,
>>
>> I am very new to puppet.
>>
>> I installed puppet 3.2.3 (open source) on Debian Wheezy. Everything seems 
>> to work fine.
>>
>> Now I want to setup ssh::auth on the puppet master. The documentation 
>> states that:
>>
>> "To install ssh::auth, place the file 
>> auth.pp<http://projects.reductivelabs.com/attachments/935/auth.pp> (attached 
>> to this page) into the ssh/manifests directory in your module path: for 
>> example, /etc/puppet/modules/ssh/manifests/auth.pp."
>>
>>
>> Unfortunately my system does not have ssh/manifest and therefore I 
>> wonder, I this a minor issue? If not, how do I go about setting up ssh:auth 
>> in this environment?
>>
>> Any help offered is highly appreciated.
>>
>> Joseph
>>
>>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] a different ssh::auth problem

[Joseph Mwesigwa Bbaale]

Hi,

I am very new to puppet.

I installed puppet 3.2.3 (open source) on Debian Wheezy. Everything seems 
to work fine.

Now I want to setup ssh::auth on the puppet master. The documentation 
states that:

"To install ssh::auth, place the file 
auth.pp (attached 
to this page) into the ssh/manifests directory in your module path: for 
example, /etc/puppet/modules/ssh/manifests/auth.pp."


Unfortunately my system does not have ssh/manifest and therefore I wonder, 
I this a minor issue? If not, how do I go about setting up ssh:auth in this 
environment?

Any help offered is highly appreciated.

Joseph

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet agent --test errors

[Joseph Mwesigwa Bbaale]

Hello puppet-users.

I am really new to puppet so, please pardon me if my question has rather an 
obvious answer.

I have tried to install puppet on both a Debian 6 VM and CentOS 6.3 VM but 
always get this error along the way:

## Setting up the database... 
Configuring postgresql server... 
PostgreSQL server configured. 
!! ERROR: The PostgreSQL server failed to start; unable to proceed 


I decided to separate the roles. The puppet-master role installs without a 
problem but the puppetDB component has always failed with the same error 
above.

Yesterday I looked at this "install_log.lastrun." file on the VM 
intended for the DB role and noticed these errors: 


Line 64: Warning: Error 400 on SERVER: Failed to find pptconsole.ca.local 
via exec: Execution of '/etc/puppetlabs/puppet-dashboard/external_node 
pptconsole.ca.local' returned 7: 
Line 213: Error: Could not retrieve catalog from remote server: Error 400 
on SERVER: Failed to submit 'replace facts' command for pptconsole.ca.local 
to PuppetDB at pptconsole.ca.local:8081: No route to host - connect(2) 
Line 213: Error: Could not retrieve catalog from remote server: Error 400 
on SERVER: Failed to submit 'replace facts' command for pptconsole.ca.local 
to PuppetDB at pptconsole.ca.local:8081: No route to host - connect(2) 
Line 215: Error: Could not retrieve catalog; skipping run 
Line 347: Error: Could not start Service[postgresqld]: Execution of 
'/sbin/service pe-postgresql start' returned 1: 
Line 348: Error: 
/Stage[main]/Postgresql::Server/Service[postgresqld]/ensure: change from 
stopped to running failed: Could not start Service[postgresqld]: Execution 
of '/sbin/service pe-postgresql start' returned 1: 


Today I decided to redo the setup, on a different machine. But after 
installing the puppet-master component, the "puppet agent --test" command 
produces these error:

Warning: Unable to fetch my node definition, but the agent run will 
continue:
Warning: Error 400 on SERVER: Failed to find pptbasic.ca.local via exec: 
Execution of '/etc/puppetlabs/puppet-dashboard/external_node 
pptbasic.ca.local' returned 7: 
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Failed to submit 'replace facts' command for pptbasic.ca.local to PuppetDB 
at pptbasic.ca.local:8081: Connection refused - connect(2)
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


On this VM, I have enabled traffic on port 8081 with the commands:

iptables -A INPUT -i eth4 -p tcp --dport 8081 -m state --state 
NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth4 -p tcp --sport 8081 -m state --state ESTABLISHED 
-j ACCEPT


However, telnet pptbasic.ca.local 8081 brings the error: connect to address 
192.168.60.130: Connection refused

I have so far failed to figure out how to proceed.

Any help is highly appreciated.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.