[Puppet Users] package require to run puppet using mcollective on RHEL

[Ankit Mittal]

Hi All,

Please help in finding that the following packages are require to run 
puppet,factor,mcollective and ruby on RHEL :

1)gdbm-devel
2)zlib-devel
3)openssl-devel
4)readline-devel

Actually i am installing yaml ,ruby,puppet,factor and mcollective inside a 
common folder on one server and then copy the folder to other node for 
running client .
so i want to know that the above packages are require on the nodes to run 
puppet using mcollective

-- 
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.

Re: [Puppet Users] Packages for Ubuntu 13.04 (raring)

[Colin Hudler]

Watch this space: 

On 06/13/2013 06:49 PM, Vlad wrote:

Any news about the packages for Raring?

On Monday, June 10, 2013 10:24:25 AM UTC-5, Andreas Ntaflos wrote:

It seems there are no packages available for Ubuntu 13.04. There is a
puppetlabs-release package for raring, but except for that the
directory
http://apt.puppetlabs.com/pool/raring/main/p/
 is empty.

I see no packages anywhere else for 13.04, only the ones in the
official
Ubuntu repos. This doesn't seem right, does it?

Andreas

--
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.




--
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] Managing (and pinning) package versions with puppet

[Andres Olarte]

I have an installation that I'm trying to manage with puppet. For some of 
the packages we want to have very tight control over the versions. Since 
they are critical to our application, we only upgrade them after testing in 
our test environment, and we schedule upgrades during low traffic times. I 
don't want puppet to upgrade my database whenever a new package appears. I 
specified the version in my puppet manifest to prevent the package from 
automatically upgrading, however when I went to generate another instance 
using the same config, that version of the package was gone from the Ubuntu 
repo. Only the more recent ones are there.

For some of the packages, I've been packing them myself into my own repo, 
however packaging the database (postgresql) has proven too be too much 
overhead.

Any solutions or ideas?

We're using Ubuntu 12.04.1 LTS.


Thanks,


Andres

-- 
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] Service wouldn't start

[Pan Luo]

I'm trying to set up gitlab on the RHEL 6 server 
using https://github.com/sbadia/puppet-gitlab with modifications to use RVM.

The problem I'm having is gitlab service wouldn't start even it says so. 
Here is the service code:

>   service {
> 'gitlab':
>   ensure => running,
>   pattern=> 'puma',
>   hasrestart => true,
>   enable => true,
>   hasstatus  => false,
>   subscribe  => File['/etc/init.d/gitlab'],
>   }


Here is the message from agent with debug on:

> Debug: Service[gitlab](provider=redhat): Executing 'ps -ef'
> Debug: Executing '/sbin/chkconfig gitlab'
> Debug: Executing '/sbin/service gitlab start'
> Debug: Executing '/sbin/chkconfig gitlab'
> Notice: /Stage[main]/Gitlab::Server/Service[gitlab]/ensure: ensure changed 
> 'stopped' to 'running'
> Debug: /Stage[main]/Gitlab::Server/Service[gitlab]: The container 
> Class[Gitlab::Server] will propagate my refresh event
> Info: /Stage[main]/Gitlab::Server/Service[gitlab]: Unscheduling refresh on 
> Service[gitlab]
> Debug: Class[Gitlab::Server]: The container Stage[main] will propagate my 
> refresh event
> Debug: Finishing transaction 69986165764840 



It did run /sbin/service gitlab start, but nothing happend. The gitlab 
service is still stopped and nothing appears in the server log. I noticed 
one line saying  "Unscheduling refresh on Service[gitlab]" and wondering if 
it has something to do with it. But why unscheduling my refresh? Any 
advice? Thanks.

-- 
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] puppetlabs-apt and package resource dependency

[nic]

Hi

I have only recently started using modules off the forge and running a 
recent version of Puppet (the majority of our network is still utilising 
0.25.4).  I spent a significant amount of time ensuring that dependencies 
in our existing Puppet implementation result in a single Puppet run will 
always succeed with the intended config applied to a node.

When making use of puppetlabs-apt I notice that there is nothing included 
in that module that would make the Exec['apt_update'] run before other 
package resources in my catalogue.  My thought would be to add something 
like this to update.pp:
  
Exec['apt_update'] -> Package <| title != "python-software-properties" and 
title != "software-properties-common" |>

I have also tried using the tag metaparameter ( tag != "apt" ) but then 
ended up with a dependency cycle.

Does anyone have an opinion as to why this is a terrible idea?  I ask 
because I have submitted a pull request for the change prior to reading the 
very informative page about contributing to puppetlabs modules and would 
value any community feedback on my approach.

Regards,
Nic

-- 
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] package require for running puppet with mcollective

[Ankit Mittal]

Hi All,
please help to find that the following packages are require to run puppet 
using mcollective on RHEL 64 bit :
1) *gdbm-devel.x86_64*
2) *zlib-devel.x86_64*
3) *openssl-devel.x86_64*
4)* readline-devel.x86_64*
*
*
or we can* *use the above packages without *devel *(like *gdbm.x86_64)*
Actually we are making the package of all file puppet,factor,ruby and 
mcollective , from one server and then moving the package to other node to 
run the client from that node.
if  the above packages gdbm,zlib,openssl and readline of type *devel *is 
not at client.
The package that contain ruby,puppet,factor and mcollective will work.
Please give your suggestion.

Thanks
Ankit 

-- 
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] Service wouldn't restart/refresh

[Pan Luo]

I was trying to set up gitlab using this module 
(https://github.com/sbadia/puppet-gitlab) with some modification to work 
with RVM and RHEL 6. I got everything working except the gitlab service 
wouldn't start.

The service is defined as:

>  service {
> 'gitlab':
>   ensure => running,
>   pattern=> 'puma',
>   hasrestart => true,
>   enable => true,
>   hasstatus  => false,
>   subscribe  => File['/etc/init.d/gitlab'],
>   }


The related output from agent with debug enabled:

> Debug: Service[gitlab](provider=redhat): Executing 'ps -ef'
> Debug: Executing '/sbin/chkconfig gitlab'
> Debug: Executing '/sbin/service gitlab start'
> Debug: Executing '/sbin/chkconfig gitlab'
> Notice: /Stage[main]/Gitlab::Server/Service[gitlab]/ensure: ensure changed 
> 'stopped' to 'running'
> Debug: /Stage[main]/Gitlab::Server/Service[gitlab]: The container 
> Class[Gitlab::Server] will propagate my refresh even
> t
> Info: /Stage[main]/Gitlab::Server/Service[gitlab]: Unscheduling refresh on 
> Service[gitlab]
> Debug: Class[Gitlab::Server]: The container Stage[main] will propagate my 
> refresh event
> Debug: Finishing transaction 70257873749220


It seems the /sbin/service gitlab start got executed. But the service is 
not started (no entries in log either). However, if I manually run service 
gitlab start, it works fine. 

I noticed that there is a line saying "Unscheduling refresh on 
Service[gitlab]". Not sure why and if it has anything to do with it. Any 
advice? Thanks.

Cheers,
Pan

-- 
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] New to Puppet bash: command not found

[gfdaddy14]

I have installed PE 2.8 server
None of the commands work =, for example... puppet --server list, puppet 
agent --test,puppet agent --test --server=`hostname`, 
puppetca, I get the following error: 
*bash: puppetca: command not found  * I get this no matter which 
command I try to run.
** 
*lease help, extremely frustrated.*
*I have installed the server without issue and the agent on another server 
without issue. I am stuck like chuck.*

-- 
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.

Re: [Puppet Users] New to Puppet bash: command not found

[Peter Bukowinski]

Make sure the puppet binaries are in your path. 

-- Peter (from phone)

> On Jun 15, 2013, at 12:11 PM, gfdadd...@gmail.com wrote:
> 
> I have installed PE 2.8 server
> None of the commands work =, for example... puppet --server list, puppet 
> agent --test,puppet agent --test --server=`hostname`, 
> puppetca, I get the following error:
> bash: puppetca: command not found   I get this no matter which command I 
> try to run.
>  
> lease help, extremely frustrated.
> I have installed the server without issue and the agent on another server 
> without issue. I am stuck like chuck.
> -- 
> 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.
>  
>  

-- 
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.

Re: [Puppet Users] Service wouldn't start

[Rilindo Foster]

I guess this piece of code is what you created , because puppet-gitlab has that 
already defined service.pp already has that defined:

file {
'/etc/init.d/gitlab':
  ensure  => file,
  content => template('gitlab/gitlab.init.erb'),
  owner   => root,
  group   => root,
  mode=> '0755',
  notify  => Service['gitlab'],
  require => Exec['Setup gitlab DB'];
  }

  service {
'gitlab':
  ensure => running,
  require=> File['/etc/init.d/gitlab'],
  pattern=> 'puma',
  hasrestart => true,
  enable => true;
  }


If that is the case, the service code you created is probably not necessary. In 
fact, it is probably getting the way of the puppet module trying to start up 
gitlab.

 - Rilindo
 
On Jun 14, 2013, at 2:54 AM, Pan Luo  wrote:

> I'm trying to set up gitlab on the RHEL 6 server using 
> https://github.com/sbadia/puppet-gitlab with modifications to use RVM.
> 
> The problem I'm having is gitlab service wouldn't start even it says so. Here 
> is the service code:
>   service {
> 'gitlab':
>   ensure => running,
>   pattern=> 'puma',
>   hasrestart => true,
>   enable => true,
>   hasstatus  => false,
>   subscribe  => File['/etc/init.d/gitlab'],
>   }
> 
> Here is the message from agent with debug on:
> Debug: Service[gitlab](provider=redhat): Executing 'ps -ef'
> Debug: Executing '/sbin/chkconfig gitlab'
> Debug: Executing '/sbin/service gitlab start'
> Debug: Executing '/sbin/chkconfig gitlab'
> Notice: /Stage[main]/Gitlab::Server/Service[gitlab]/ensure: ensure changed 
> 'stopped' to 'running'
> Debug: /Stage[main]/Gitlab::Server/Service[gitlab]: The container 
> Class[Gitlab::Server] will propagate my refresh event
> Info: /Stage[main]/Gitlab::Server/Service[gitlab]: Unscheduling refresh on 
> Service[gitlab]
> Debug: Class[Gitlab::Server]: The container Stage[main] will propagate my 
> refresh event
> Debug: Finishing transaction 69986165764840 
> 
> 
> It did run /sbin/service gitlab start, but nothing happend. The gitlab 
> service is still stopped and nothing appears in the server log. I noticed one 
> line saying  "Unscheduling refresh on Service[gitlab]" and wondering if it 
> has something to do with it. But why unscheduling my refresh? Any advice? 
> Thanks.
> 
> -- 
> 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.
>  
>  

-- 
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: New to Puppet bash: command not found

[gfdaddy14]

Forgot to mention that I am ne to LInux also...
 
Do you have an example?
 
On Saturday, June 15, 2013 12:11:17 PM UTC-4, gfda...@gmail.com wrote:

> I have installed PE 2.8 server
> None of the commands work =, for example... puppet --server list, puppet 
> agent --test,puppet agent --test --server=`hostname`, 
> puppetca, I get the following error: 
> *bash: puppetca: command not found  * I get this no matter which 
> command I try to run.
> ** 
> *lease help, extremely frustrated.*
> *I have installed the server without issue and the agent on another 
> server without issue. I am stuck like chuck.*
>

-- 
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.

Re: [Puppet Users] ruby issue

[Greg Chavez]

I don't have access to the Optional repo, full stop, so I can't mirror
it.  However, I do have access to its constituent packages, so what
you can do is search for "rubgems" at RHN under Downloads -> Packages
and download the rpm.  I then dropped it into a one-file mrepo, added
the mrepo info to my puppetlabs yum.repo file that I instantiate with
Cobbler and then control with puppet, and viola, my kicks and spins
come up with a working puppet client.  Easy enough to do this every
time I upgrade puppet.

I think Puppet is making a mistake here too, but there are worse
things.  My problem will be solved in total when my company
transitions to CentOS later this year.

Cheers.

--Greg Chavez

On Fri, Jun 14, 2013 at 10:44 PM, Stuart Cracraft  wrote:
> Boo!!! Hiss!!
>
> Be a One-Stop-Shop!
>
> It's YOUR collective after all
>
> --Stuart
>
> On Jun 14, 2013, at 7:13 PM, Michael Stahnke  wrote:
>
>> On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez  wrote:
>>> Which is just fine if your company has the Optional subscription.
>>> Mine doesn't.  So I'm screwed unless I write a script to manually pull
>>> updates from Fedora or CentOS into a custom mrepo repository. Bit of a
>>> pain, that is.
>>
>> The optional repo is free from what I can tell. It's included with a
>> RHEL subscription. Puppet Labs doesn't try to replace packages in
>> provided by the upstream OS vendor. Therefore, we don't supply
>> packages that replace things in the RHEL repo since they work just
>> fine with Puppet et al.
>>
>>
>>>
>>> On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens  
>>> wrote:
 We supply rubygems for rhel 5 because it is not available in centos or
 rhel 5 core (it is in EPEL). In rhel6 and cent6, it is widely and
 easily available (in cent6 base, and in rhel6 optional repos), so we
 don't supply it for el6.

 On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez  wrote:
> The rubygems package is available from here:
>
> https://yum.puppetlabs.com/el/5/dependencies/x86_64/
>
> So why wouldn't it be available from 6?  I'm pretty sure it used to be
> there since I've kicked several rhel 6 systems that had no problem
> installing puppet from puppetlabs.  Was it mistakenly dropped from the
> puppetlabs rhel 6 repo?
>
> Thanks
> --Greg Chavez
>
> On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft  
> wrote:
>> You are most welcome.
>>
>> On Jun 10, 2013, at 7:40 AM, Lab Yizhar  wrote:
>>
>> Thanks m8 for the mental support :)
>>
>> As you already know, as an open source believer ,I'm kind of into it and 
>> the
>> solution is there, But I want to do it without RHN subscription that will
>> used on our production env.
>>
>> Couple of humps and I'll be there this way or the offical other...
>>
>> On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft  
>> wrote:
>>>
>>> It's not that hard!
>>>
>>> You can do it!!!
>>>
>>> Also, you could buy some books on the subject!
>>>
>>> On Jun 10, 2013, at 5:51 AM, Yizhar A.  wrote:
>>>
>>> Hi,
>>>
>>> Finish my things on this issue for now as the last one in this chain
>>> talented enough to be asking for pay for answering this
>>>
>>> I'll update when I'll figure it out else.
>>>
>>> Stay tuned,
>>>
>>> Yizhar
>>>
>>> "Don't ask what the community can contribute to you ? ask what I can
>>> contribute the community"
>>> On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:

 Dear Stuart,

 Kind of my first steps into puppet on RHEL 6 and I wonder how you 
 manage
 to solve the rubygems issue.

 Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs
 repo I can't see from where I can get the rubygems missing package.

 As you after wiki'd it :) can you give me a piece of advise in here or
 attached your docs to help me through ?

 Thanks,

 --Yizhar


 On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
>
> Hey, good news.
>
> All is well.
>
> Ruby & related are good. Puppet too. And Red Hat.
>
> Also, I've documented/wiki'd the Puppet Master + Client install with
> respect
> to bare metal to delivered system for all related aspects and
> transmitted, fully,
> disclosed entirely, to staff.
>
> Next week, I will be tuning the configuration file on master and 
> agents
> and
> writing many more puppet patterns plus training staff.
>
> As it is their only hope!
>
> --Stuart
>
> P.S. The firm's personnel have had heart attacks, strokes and other
> major maladies amongst
> staff in the past year du

[Puppet Users] puppet-dashboard not linking both filebucket md5 links

[cko]

Hi everyone,

I have the following problem with the puppet-dashboard / filebucket "diff" 
functionality:






It doesnt show the content of the "new / changed" file.

I configured the client and server as instructed 
here: http://links.puppetlabs.com/enabling_the_filebucket_viewer.

Any ideas?


-- 
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.

Re: [Puppet Users] Re: New to Puppet bash: command not found

[Gabriel Filion]

On 15/06/13 02:15 PM, gfdadd...@gmail.com wrote:
> Forgot to mention that I am ne to LInux also...
>  
> Do you have an example?

the path that was mentioned by Peter is a set of directory paths
separated by ":" where binaries are searched when invoked. it is set in
the environment variable $PATH.

with puppet, it is considered a good practice to set a global $PATH
value that corresponds to your system with the below snippet (the
capital letter at the beginning of "Exec" is important).

Exec {
  path => '/bin:/sbin:/usr/bin:/usr/sbin',
}

-- 
Gabriel Filion



signature.asc
Description: OpenPGP digital signature