[Puppet Users] Puppet Dashboard

[moonsun1124]

Hi All,

I am using puppet 4.3. I think dashboard is not there any more instead of 
this we have web console. 

Just want to know whether I am right or not.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7b8d163a-10fa-452f-8bc6-fd194f059ce1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[marcos.ata1...@gmail.com]

I understand, thank you for the answers . I try The Foreman.

Em 28-08-2015 09:13, Dirk Heinrichs escreveu:

Am 28.08.2015 um 02:42 schrieb Marcos Renato:

I try to install puppet-dashboard


Puppet Dashboard is also deprecated, I'd recommend you use The Foreman 
 instead.


HTH...

Dirk
--

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 
--
You received this message because you are subscribed to a topic in the 
Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/puppet-users/NMhaHBplYoY/unsubscribe.
To unsubscribe from this group and all its topics, 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/55E05082.7030007%40recommind.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/55E05138.9040301%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[Dirk Heinrichs]

Am 28.08.2015 um 14:12 schrieb marcos.ata1...@gmail.com:
> /etc/apt/sources.list.d/puppetlabs.list
>
> deb http://apt.puppetlabs.com wheezy main
> deb-src http://apt.puppetlabs.com wheezy main
> deb http://apt.puppetlabs.com wheezy dependencies
> deb-src http://apt.puppetlabs.com wheezy dependencies
>
> jessie does not have puppet-dashboard. 

Yep, because it's deprecated. And Jessie doesn't have ruby1.8 anymore.
Try The Foreman  instead of Dashboard.

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/55E05120.3030409%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[Dirk Heinrichs]

Am 28.08.2015 um 02:42 schrieb Marcos Renato:
> I try to install puppet-dashboard

Puppet Dashboard is also deprecated, I'd recommend you use The Foreman
 instead.

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/55E05082.7030007%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[marcos.ata1...@gmail.com]

sorry,


apt-get install puppet-dashboard

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 puppet-dashboard : Depends: ruby1.8 (>= 1.8.7) but it is not installable
Depends: libdbd-mysql-ruby but it is not installable
E: Unable to correct problems, you have held broken packages.



/etc/apt/sources.list.d/puppetlabs.list

deb http://apt.puppetlabs.com wheezy main
deb-src http://apt.puppetlabs.com wheezy main
deb http://apt.puppetlabs.com wheezy dependencies
deb-src http://apt.puppetlabs.com wheezy dependencies

jessie does not have puppet-dashboard.


Em 28-08-2015 09:01, Dirk Heinrichs escreveu:

LC_ALL=C apt-get install puppet-dashboard


--
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/55E05017.5030401%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[Dirk Heinrichs]

Am 28.08.2015 um 02:42 schrieb Marcos Renato:

> I try to install puppet-dashboard from Debian respository, but see the
> error :
>
> puppet-dashboard depends on ruby1.8 (>= 1.8.7); however: Package
> ruby1.8 is not installed.
>
> puppet-dashboard depends on libdbd-mysql-ruby; however: Package
> libdbd-mysql-ruby is not installed.

Guess you tried to use the Wheezy repository on Jessie. Jessie doesn't
have ruby1.8 anymore.

Bye...

dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/55E04FD7.6020202%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[Dirk Heinrichs]

Am 28.08.2015 um 13:58 schrieb marcos.ata1...@gmail.com:

> apt-get install puppet-dashboard
>
> Lendo listas de pacotes... Pronto

Try again please with

LC_ALL=C apt-get install puppet-dashboard

so that I can actually understand the language ;)

Bye...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/55E04DB7.6040106%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[marcos.ata1...@gmail.com]

apt-get install puppet-dashboard

Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Alguns pacotes não puderam ser instalados. Isto pode significar que
você solicitou uma situação impossível ou, se você está usando a
distribuição instável, que alguns pacotes requeridos não foram
criados ainda ou foram retirados da "Incoming".
A informação a seguir pode ajudar a resolver a situação:

Os pacotes a seguir têm dependências desencontradas:
 puppet-dashboard : Depende: ruby1.8 (>= 1.8.7) mas não é instalável
Depende: libdbd-mysql-ruby mas não é instalável
E: Impossível corrigir problemas, você manteve (hold) pacotes quebrados.


Em 28-08-2015 03:34, Dirk Heinrichs escreveu:

Am 28.08.2015 um 02:42 schrieb Marcos Renato:

I try to install puppet-dashboard from Debian respository, but see 
the error :

puppet-dashboard depends on ruby1.8 (>= 1.8.7); however:
   Package ruby1.8 is not installed.
puppet-dashboard depends on libdbd-mysql-ruby; however:
   Package libdbd-mysql-ruby is not installed.


Don't give too much details, people may be able to help you.

So, how do you try to install it (please provide exact command plus 
its complete output)?


Bye...

Dirk
--

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 
--
You received this message because you are subscribed to a topic in the 
Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/puppet-users/NMhaHBplYoY/unsubscribe.
To unsubscribe from this group and all its topics, 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/55E000F1.1090900%40recommind.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/55E04CFC.5010009%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet dashboard Debian Jessie

[Dirk Heinrichs]

Am 28.08.2015 um 02:42 schrieb Marcos Renato:

> I try to install puppet-dashboard from Debian respository, but see the
> error :
> puppet-dashboard depends on ruby1.8 (>= 1.8.7); however:
>   Package ruby1.8 is not installed.
> puppet-dashboard depends on libdbd-mysql-ruby; however:
>   Package libdbd-mysql-ruby is not installed.

Don't give too much details, people may be able to help you.

So, how do you try to install it (please provide exact command plus its
complete output)?

Bye...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/55E000F1.1090900%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet dashboard Debian Jessie

[Marcos Renato]

Hi,

I try to install puppet-dashboard from Debian respository, but see the 
error :

puppet-dashboard depends on ruby1.8 (>= 1.8.7); however:
  Package ruby1.8 is not installed.


puppet-dashboard depends on libdbd-mysql-ruby; however:
  Package libdbd-mysql-ruby is not installed.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a8a62e47-e2fb-4880-b40e-b136c989c959%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Dashboard on Centos 7

[Ramin K]

On 5/13/15 10:22 AM, Ramin K wrote:

Centos shops 2.0


argh. Centos 7 ships 2.0

--
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/5553888D.30408%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Dashboard on Centos 7

[Ramin K]

On 5/13/15 9:16 AM, Gabriele Angeli wrote:

Hi guys,

I tried to install puppet dashboard on Centos 7.

I installed  the right repository for Centos 7 (puppetlabs.repo) but
when I launch the command "yum install puppet-dashboard" the result is
the following:


*No package puppet-dashboard available.*
*Error: Nothing to do*



puppet-dashboard only works on systems that have Ruby 1.8.7. Centos 
shops 2.0. You can use the src files, RVM, Passenger4, gem install into 
RVM ruby 1.8, etc etc which will work, but requires you to know how all 
those technologies fit together. If you're dead set on using the 
dashboard that has been EOL'ed since 2012, you can use the community 
updated edition which should work with 2.0.


https://github.com/sodabrew/puppet-dashboard/

Other dashboard you might consider are http://theforeman.org/ and 
https://github.com/puppet-community/puppetboard


Ramin

--
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/55538842.6010406%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard on Centos 7

[Gabriele Angeli]

Hi guys,

I tried to install puppet dashboard on Centos 7. 

I installed  the right repository for Centos 7 (puppetlabs.repo) but when I 
launch the command "yum install puppet-dashboard" the result is the 
following:


*No package puppet-dashboard available.*
*Error: Nothing to do*

Someone can help me?

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b1b9c469-32cb-499a-94b1-8cd4efe0048c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dashboard nodes show as Unresponsive

[Walid]

the node usually shows unresponsive if it did not report back within the
unresponsive threshold time, how often you are running the agents, and how,
what is the frequency of reports already received?

On 25 April 2015 at 03:48,  wrote:

> Hi,
>
> I am using open source Puppet 3.7.3 with Dashboard.
>
> My puppet agent seems working fine, but on Dashboard, most nodes show as
> Unresponsive.
>
> I have restarted puppet-dashboard-workers, but still no help.
>
> Any clue?
>
> Thanks,
> Stacey
>
>
>
>
>  --
> 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/59f3f81d-1b5b-4aae-b3aa-1c3baaad07e7%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/CAN4dctr-066mJdXZv%3DDEVUs1NxEXk4o0P5WsEQB7vo_OjXwUng%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet dashboard nodes show as Unresponsive

[staceytian4321]

Hi,

I am using open source Puppet 3.7.3 with Dashboard.

My puppet agent seems working fine, but on Dashboard, most nodes show as 
Unresponsive.

I have restarted puppet-dashboard-workers, but still no help.

Any clue?

Thanks,
Stacey




-- 
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/59f3f81d-1b5b-4aae-b3aa-1c3baaad07e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard/console

[sanjay kumar chahar]

Hi 

I am very new to puppet and I have installed puppet master server and 
configure 2 node ( agent ) and its working.

I want to know how can I manage puppet, 

Is there any management console/ Puppet dashboard  ?

If yes answer of above question  Can I installed it on separate  VM/server 

Please provide documentation to configure it.

Thanks 

Sanjay

-- 
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/5de5abc3-df85-43e8-81de-3eae934434c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet-dashboard not importing automatically the reports

[Juan Sierra Pons]

Hi,

I have 3 puppet-masters/puppet-dashboards "supposedly" configured
equally but in one of them the reports are not being imported on the
dashboard. The other two work ok.

If in the failing one I run the RAILS_ENV=production rake
reports:import then the reports are imported on the dashboard

[root@ puppet-dashboard]# RAILS_ENV=production rake reports:import
(in /usr/share/puppet-dashboard)
Importing 23 reports from /var/lib/puppet/reports in the background
Importing: 100%
|##|
Time: 00:00:00
23 of 23 reports queued

They can be seen as pending tasks on the dashboard

Then the puppet delayed jobs can process them:

[...]
2014-10-14T15:54:25+0200: [Worker(delayed_job.0 host:puppet-dashboard
pid:5006)] Report.create_from_yaml_file completed after 1.6418
2014-10-14T15:54:25+0200: [Worker(delayed_job.0 host:puppet-dashboard
pid:5034)] Report.create_from_yaml_file completed after 1.7403
[...]

On the other servers all the process is automatic and I have double
checked the configuration. In fact at the beginning this server worked
ok two but one day it stopped.

Any Idea what am I missing?

Best regards

--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
--

-- 
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/CABS%3Dy9v%3D32d0E6VUN0fFXqzhgLMEEdWsj%2BVAznoBjJHqhQiwdA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard showed "changed" when there is error in exec

[Peiven Cheng]

When there is error occurred during executing the "exec" command  in puppet 
script, the dashboard will show "changed" or "unchanged" instead of 
"failed" as its result.

Is there any configuration that can make dashboard shows "failed" when 
there is execution error?

-- 
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/75e82e62-faa4-40bf-a959-2093e29ffb50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dashboard with \n\n\n

[Nick Triantafillou]

Thanks for this solution Ximena, Debian 7.6 had the same issue. Swapping 
from Ruby 1.9.1 to 1.8.7 also fixed my dashboard. 

On Tuesday, 24 June 2014 00:43:53 UTC+10, Ximena Cardinali wrote:
>
> Me again,  I've changed the link of /etc/alternatives/ruby (Debian) to 
> point to ruby1.8 and everything looks good now on the Dashboard!
>
> Thanks! :)
>
> On Monday, 23 June 2014 15:37:59 UTC+2, Ximena Cardinali wrote:
>>
>> Hello, sorry to bring this back.
>>
>> I just have a question, did you just changed the path of /usr/bin/ruby or 
>> did you did something else to make it work?
>>
>> Thanks in advance,
>> X.
>>
>> On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote:
>>>
>>> On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons  
>>> wrote: 
>>> > 
>>> > El 03/10/2013 14:00, "Matt Zagrabelny"  escribió: 
>>> > 
>>> > 
>>> >> 
>>> >> Greetings, 
>>> >> 
>>> >> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18. 
>>> >> 
>>> >> I am seeing many \n strings all over the place when looking at 
>>> >> reports. Specifically the \n's are in the Metrics, Log, Events links. 
>>> >> 
>>> >> My nodes are showing up okay, and it seems just to be a problem with 
>>> >> the reports. For instance, a Metrics page starts with: 
>>> >> 
>>> >> \n 
>>> >> \n 
>>> >> Metrics 
>>> >> \n 
>>> >> \n 
>>> >> Events 
>>> >> 
>>> >> \n\n\n\n\n\n\n\n\n 
>>> >> 
>>> >> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does 
>>> not 
>>> >> yield any hints. 
>>> >> 
>>> >> Thanks! 
>>> >> 
>>> >> -mz 
>>> >> 
>>> >> -- 
>>> >> 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...@googlegroups.com. 
>>> >> To post to this group, send email to puppet...@googlegroups.com. 
>>> >> Visit this group at http://groups.google.com/group/puppet-users. 
>>> >> For more options, visit https://groups.google.com/groups/opt_out. 
>>> > Hi 
>>> > 
>>> > I had the same problem and the problem was in the ruby version 
>>> > 
>>> > Which one are you using? 
>>>
>>> realpath =ruby 
>>> /usr/bin/ruby1.9.1 
>>>
>>>
>>> > Check the dashboard webpage to find out wich one is the right one. 
>>>
>>> Looks like 1.8 is what is needed. 
>>>
>>> Looks like that worked! 
>>>
>>> Thanks! 
>>>
>>> -mz 
>>>
>>

-- 
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/80328550-e882-4457-ac76-2d21ff744b9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet dashboard not processing reports after https is enabled and shows this error message: Report processor failed: undefined method `+' for nil:NilClass

[Juan Sierra Pons]

Hi

I have been using puppet-dashboard for a long time over http without problem
Today I have configured the https creating the ssl certificate, etc.

puppetmaster, dashboard and workers have been restarted

Also I have already changed the reporturl to https on the puppet.conf
reporturl = https//dashboard.example.org:443/reports/upload

The dashboard works as expected BUT the reports are not being processed.

On the puppetmaster logs the following can be seen:
"
Aug 19 18:20:38 server3 puppet-agent[11671]: Stored state in 0.09 seconds
Aug 19 18:20:38 server3 puppet-agent[11671]: Finished catalog run in
8.66 seconds
Aug 19 18:20:40 server3 puppet-master[10313]: Report processor failed:
undefined method `+' for nil:NilClass
"
 And on the apache+passenger+puppetmaster logs the following appears:
"
server3.example.org:8140 X.X.X.X - - [19/Aug/2014:18:20:37 +0200] "GET
/production/file_metadata/modules/puppetdb/routes.yaml?links=manage&source_permissions=use
HTTP/1.1" 200 6181 "-" "-"
server3.example.org:8140 X.X.X.X - - [19/Aug/2014:18:20:39 +0200] "PUT
/production/report/server3.example.org HTTP/1.1" 200 5865 "-" "-"
"

So as far as i know the report is been pushed to the puppetmaster but
the dashboard is not able to process it

puppetmaster and puppet-dashboard are the same server with aliases:
server3.example.org
puppet -> server3.example.org
dashboard-> server3.example.org

Any idea what am I missing?

Thanks for your time

Best regards

--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
--

-- 
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/CABS%3Dy9sGgtDLKcmakHYPVpUm018%2BGkG4LdEyFbVxAra-0c%2BWcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard HTTP Basic Authentication Issues

[Stella]

Hi, I am trying to configure Puppet (3.6.2) Dashboard (1.2.23) with HTTP 
Basic Authentication. I followed this document's "Security" section:
http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html

Basically, in Dashboard’s vhost configuration, I added those lines:


Order allow,deny
Allow from 192.168.240.110 # your puppet master's IP
Satisfy any
AuthName "Puppet Dashboard"
AuthType Basic
AuthUserFile /etc/httpd/webaccess
Require valid-user


Then I also created a user/password combination:
htpasswd -c /etc/httpd/webaccess myusername

Restart httpd service and Web access to the interface works fine. It 
prompts me for username/password.
However, when I ran "puppet agent --test", it failed. Puppet cannot get 
nodes from the dashboard.

Questions:

1. I googled and found this issue: 
https://projects.puppetlabs.com/issues/4890. It points to another two 
issues. Should I follow those two issues to fix my problem?

issue #7173  -- Puppet cannot submit reports to dashboard. Modify 
puppet/lib/puppet/reports/http.rb to properly parse usernames and passwords 
out of the reporturl configuration option. 
issue #5126  -- Puppet cannot get nodes from the dashboard. Modify the 
external node script to properly parse usernames and passwords out of its 
URL 

2. In the document, it has a notice

Notice that you need to leave an access exception for your puppet 
master. Although it’s possible to configure Puppet to use a password when 
connecting to Dashboard (by adding a username and password to Puppet’s 
reporturl and the URL used by the external_nodes script), this 
currently requires patching Puppet’s http report handler; see issue 7173 
for more details.

I am a little confused here. "you need to leave an access exception for 
your puppet master", does this refer to those two lines in the vhost config:

Order allow,deny
Allow from 192.168.240.110 # your puppet master's IP

If yes, does that mean if I have those two lines to leave an access 
exception for puppet master, I don't need to apply those two patches? But 
now with those two lines, I still can't get puppet agent to get node from 
dashboard. Maybe I should go ahead and apply those two patches?

-- 
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/6b064326-2502-4576-a928-a3dda5370b6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard

[Stella]

Hi, I am trying to configure Puppet (3.6.2) Dashboard (1.2.23) with HTTP 
Basic Authentication. I followed this document's "Security" section:
http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html

Basically, in Dashboard’s vhost configuration, I added those lines:


Order allow,deny
Allow from 192.168.240.110 # your puppet master's IP
Satisfy any
AuthName "Puppet Dashboard"
AuthType Basic
AuthUserFile /etc/httpd/webaccess
Require valid-user


Then I also created a user/password combination:
htpasswd -c /etc/httpd/webaccess myusername

Restart httpd service and Web access to the interface works fine. It 
prompts me for username/password.
However, when I ran "puppet agent --test", it failed. Puppet cannot get 
nodes from the dashboard.

Questions:

1. I googled and found this issue: 
https://projects.puppetlabs.com/issues/4890. It points to another two 
issues. Should I follow those two issues to fix my problem?

issue #7173  -- Puppet cannot submit reports to dashboard. Modify 
puppet/lib/puppet/reports/http.rb to properly parse usernames and passwords 
out of the reporturl configuration option. 
issue #5126  -- Puppet cannot get nodes from the dashboard. Modify the 
external node script to properly parse usernames and passwords out of its 
URL 

2. In the document, it has a notice

Notice that you need to leave an access exception for your puppet 
master. Although it’s possible to configure Puppet to use a password when 
connecting to Dashboard (by adding a username and password to Puppet’s 
reporturl and the URL used by the external_nodes script), this currently 
requires patching Puppet’s http report handler; see issue 7173 for more 
details.

I am a little confused here. "you need to leave an access exception for 
your puppet master", does this refer to those two lines in the vhost config:

Order allow,deny
Allow from 192.168.240.110 # your puppet master's IP

If yes, does that mean if I have those two lines to leave an access 
exception for puppet master, I don't need to apply those two patches? But 
now with those two lines, I still can't get puppet agent to get node from 
dashboard. Maybe I should go ahead and apply those two patches?

Thanks a lot!

-- 
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/2cde8ded-302c-45b9-9aa2-4b9b118bfc63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet-dashboard issues

[Bouny]

Hi !

(sorry for my poor english)


My puppetmaster 3.4.3 run on Ubuntu 14.04 LTS

I've just manage to replace WEBrick, Puppet use Apache/Passenger to work 
now.

I'm a newbie on this, so i've setup Puppet with different docs found on 
internet. I've started with "apt-get" for the basic install. 

For Passenger, I tried gems. Ruby version is 1.9.1, I saw that is the source 
of many problems but i'm a newbie on linux too... I don't know if a downgrad 
of ruby is a good idea or not, or if it is necessary.

Puppet works fine, but my problem concern dashboard.

So here is my problem :

I've configured with success the vhost for apache.
I've created the database on mysql.

but when i run "rake RAILS_ENV=production db:migrate" i've got an error :
Warning: Rails rake tasks currently unavailable because we can't find the 
'rails' gem
rake aborted!
Don't know how to build task 'db:migrate'

trace :

/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/task_manager.rb:62:in `[]'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:149:in 
`invoke_task'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `block 
(2 levels) in top_level'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `each'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `block 
in top_level'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:115:in 
`run_with_threads'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:100:in 
`top_level'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:78:in `block in 
run'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:176:in 
`standard_exception_handling'
/var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:75:in `run'
/var/lib/gems/1.9.1/gems/rake-10.3.2/bin/rake:33:in `'
/usr/local/bin/rake:23:in `load'
/usr/local/bin/rake:23:in `'


Any idea ?

thx


-- 
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/loom.20140729T160101-985%40post.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard 1.2.23 disable link in Main html page

[GregC]

Can someone point me to a way to disable the Puppet Dashboard Version link 
in the top left corner of the main page?
 
Is there a possible way to do this through settings.yml file?
 
The reason I need to do this is that we have no internet access and 
clicking on the link attempts to connect to github and i'd like to avoid 
that.
 
Otherwise any way I can find the source page for the code , I would 
appreciate your help, 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8b0a5553-d859-4ab3-a9cd-7ead0606a8f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dashboard with \n\n\n

[Ximena Cardinali]

Me again,  I've changed the link of /etc/alternatives/ruby (Debian) to 
point to ruby1.8 and everything looks good now on the Dashboard!

Thanks! :)

On Monday, 23 June 2014 15:37:59 UTC+2, Ximena Cardinali wrote:
>
> Hello, sorry to bring this back.
>
> I just have a question, did you just changed the path of /usr/bin/ruby or 
> did you did something else to make it work?
>
> Thanks in advance,
> X.
>
> On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote:
>>
>> On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons  
>> wrote: 
>> > 
>> > El 03/10/2013 14:00, "Matt Zagrabelny"  escribió: 
>> > 
>> > 
>> >> 
>> >> Greetings, 
>> >> 
>> >> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18. 
>> >> 
>> >> I am seeing many \n strings all over the place when looking at 
>> >> reports. Specifically the \n's are in the Metrics, Log, Events links. 
>> >> 
>> >> My nodes are showing up okay, and it seems just to be a problem with 
>> >> the reports. For instance, a Metrics page starts with: 
>> >> 
>> >> \n 
>> >> \n 
>> >> Metrics 
>> >> \n 
>> >> \n 
>> >> Events 
>> >> 
>> >> \n\n\n\n\n\n\n\n\n 
>> >> 
>> >> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not 
>> >> yield any hints. 
>> >> 
>> >> Thanks! 
>> >> 
>> >> -mz 
>> >> 
>> >> -- 
>> >> 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...@googlegroups.com. 
>> >> To post to this group, send email to puppet...@googlegroups.com. 
>> >> Visit this group at http://groups.google.com/group/puppet-users. 
>> >> For more options, visit https://groups.google.com/groups/opt_out. 
>> > Hi 
>> > 
>> > I had the same problem and the problem was in the ruby version 
>> > 
>> > Which one are you using? 
>>
>> realpath =ruby 
>> /usr/bin/ruby1.9.1 
>>
>>
>> > Check the dashboard webpage to find out wich one is the right one. 
>>
>> Looks like 1.8 is what is needed. 
>>
>> Looks like that worked! 
>>
>> Thanks! 
>>
>> -mz 
>>
>

-- 
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/8885ddc7-8627-4078-9303-616383bb253c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet dashboard with \n\n\n

[Ximena Cardinali]

Hello, sorry to bring this back.

I just have a question, did you just changed the path of /usr/bin/ruby or 
did you did something else to make it work?

Thanks in advance,
X.

On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote:
>
> On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons  > wrote: 
> > 
> > El 03/10/2013 14:00, "Matt Zagrabelny" > 
> escribió: 
> > 
> > 
> >> 
> >> Greetings, 
> >> 
> >> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18. 
> >> 
> >> I am seeing many \n strings all over the place when looking at 
> >> reports. Specifically the \n's are in the Metrics, Log, Events links. 
> >> 
> >> My nodes are showing up okay, and it seems just to be a problem with 
> >> the reports. For instance, a Metrics page starts with: 
> >> 
> >> \n 
> >> \n 
> >> Metrics 
> >> \n 
> >> \n 
> >> Events 
> >> 
> >> \n\n\n\n\n\n\n\n\n 
> >> 
> >> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not 
> >> yield any hints. 
> >> 
> >> Thanks! 
> >> 
> >> -mz 
> >> 
> >> -- 
> >> 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...@googlegroups.com . 
> >> To post to this group, send email to puppet...@googlegroups.com 
> . 
> >> Visit this group at http://groups.google.com/group/puppet-users. 
> >> For more options, visit https://groups.google.com/groups/opt_out. 
> > Hi 
> > 
> > I had the same problem and the problem was in the ruby version 
> > 
> > Which one are you using? 
>
> realpath =ruby 
> /usr/bin/ruby1.9.1 
>
>
> > Check the dashboard webpage to find out wich one is the right one. 
>
> Looks like 1.8 is what is needed. 
>
> Looks like that worked! 
>
> Thanks! 
>
> -mz 
>

-- 
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/c83279b6-b99b-4ec9-b915-93f3c884df78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Dashboard behind HTTPS

[Andreas Zuber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello

I just came across the same problem and did some reading of the code of
the http report plugin and the classes it uses to understand what the
problem is. It seams that (at least in the puppet version I use here) it
uses the same classes to get a HTTP connection puppet usually uses to
talk to the master, configured with puppets own cert store.

I am not sure if I interpreted everything correctly, but I don't think
that using the puppet cert store for validation is a good idea in this
case. The Dashboard most likely uses another CA which is also installed
on the browser and in the systems CA store.

I copied and renamed the http plugin (I renamed it to https and deliver
it with pluginsync) and simply use the default cert locations, which
lets puppet successfully report over HTTPS now:

|git remote add origin
https://github.com/ZeroPointEnergy/puppet-https-reports.git|

I am not sure if there is an easier or cleaner way and I just did not
see it.

Sincerely
Andreas

On 02/28/2014 06:05 PM, henriquerodrig...@notonthehighstreet.com wrote:
> Hi,
>
> Can Puppet Master send the reports to Puppet Dashboard via HTTPS?
>
> My Puppet Dashboard is protected with a certificate signed by another
CA and this seems to break the sending of reports because Puppet doesn't
have the necessary certificate to connect securely and I can't seem to
make it work.
>
> Thank you,
> Henrique Rodrigues
> --
> 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/25e293bd-41b0-4eda-b65b-bb0d82caeff3%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.


- -- 
Andreas Zuber
Linux System-Ingenieur
Puzzle ITC GmbH
www.puzzle.ch

Telefon +41 31 370 22 00
Direkt  +41 31 370 22 49
Mobile  +41 79 766 25 51
Fax +41 31 370 22 01

Werfen Sie einen Blick in unseren Blog:

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlOkJXIACgkQc2hfmdKpdfWmkQCfTpQyW+lvBDEuHTVufVDy6Rrj
eUoAnjDcWSYdPsERV/v2HL7TjFPW3Voq
=VW+u
-END PGP SIGNATURE-

-- 
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/53A42572.605%40puzzle.ch.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet-Dashboard All Nodes "Unresponsive", Background Tasks

[Ximena Cardinali]

Hello There,

I've been struggling the last days with this issue. The situation is 
happening since I've upgrade Puppet to 3.6.0.

*- Problem:*
On Puppet-Dashboard all Hosts are shown as *Unresponsive* and thousand of 
tasks are queued as *Failed*.

*- Environment:*
OS: Debian Wheezy
Puppet-Dashboard: 1.2.23
Puppet: 3.6.0
Facter: 2.0.1
Hiera: 1.3.2

*- Applied Solutions:*

* Solution 1:
cd /usr/share/puppet-dashboard/
- Stop dashboard workers
rm -v spool/*
rake jobs:clear RAILS_ENV=production
- Start dashboard workers.

Good solution, but temporary, because the problem after a few days comes 
back.

* Solution 2: 
I've also did the following update to the DB:
mysql> ALTER TABLE delayed_job_failures MODIFY details BLOB;
Which also did not work.

Does anyone have any idea of what can be happening there?

-- 
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/d5e90a32-e8d6-4883-9cd0-d7c6d89d7f5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Dashboard port

[Kwame Bahena]

Hi Don,

You might want to take a look at this url

http://docs.puppetlabs.com/pe/latest/console_config.html#changing-the-consoles-port

Cheers!


On Thu, Jun 5, 2014 at 9:27 AM, Don Dorman  wrote:

> Good morning Everyone.
>
> I have been struggling to change the default port for Dashboard access
> from port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I
> am not mistaken.
>
> My OS is RHEL 6.4, Puppet Master 3.42-1
>
> Any directions would be great.
>
> --
> 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/521a1a3f-7ec4-424d-860a-d54704d19019%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/CANtpaPp_W-kcJ8J3PEAWpu015CmTFXap3iZNOHQPFqYs5eA54A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard port

[Don Dorman]

Good morning Everyone.

I have been struggling to change the default port for Dashboard access from 
port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I am 
not mistaken.

My OS is RHEL 6.4, Puppet Master 3.42-1

Any directions would be great.

-- 
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/521a1a3f-7ec4-424d-860a-d54704d19019%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet dashboard Pending statistics always 0

[Rudy Gevaert]

Hi, 

I've set up puppet dashboard and my puppet master 3.6.0 is sending its 
reports. 

However, when i run an agent in noop mode, the Pending column on the 
dashboard for that node remains 0.  While it should not be 0. 

The nodes pending stats on the left side are always 0 too. 

Any ideas how to troubleshoot this? 

Thanks, 

Rudy 

-- 
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/2d29c7c4-a9b3-433b-b8a4-35fc64f363f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet-dashboard 2.0.0 (open source) and postgresq 8.4l tuning

[Pete Hartman]

I deployed the open source puppet-dashboard 2.0.0 this past weekend for our 
production environment.  I did a fair amount of testing in the lab to 
ensure I had the deployment down, and I deployed as a passenger service 
knowing that we have a large environment and that webrick wasn't likely to 
cut it.  Overall, it appears to be working and behaving reasonably--I get 
the summary run status graph, etc, the rest of the UI.  Load average on the 
box is high-ish but nothing unreasonable, and I certainly appear to have 
headroom in memory and CPU.

However, when I click the "export nodes as CSV" link, it runs forever 
(Hasn't stopped yet).  

I looked into what the database was doing and it appears to be looping over 
some unknown number of report_ids, doing 

7172 | dashboard | SELECT COUNT(*) FROM "resource_statuses"  WHERE 
"resource_statuses"."report_id" = 39467 AND "resource_statuses"."failed" = 
'f' AND (
IN ( | 00:00:15.575955
 :   SELECT resource_statuses.id FROM 
resource_statuses

 : INNER JOIN resource_events ON 
resource_statuses.id = resource_events.resource_status_id

 : WHERE resource_events.status = 'noop'

 : )

 : )



I ran the inner join by hand and it takes roughly 2 - 3 minutes each time.  
The overall query appears to be running 8 minutes per report ID.

I've done a few things to tweak postgresql before this--it could have been 
running longer earlier when I first noticed the problem.

I increased checkpoint segments to 32 from the default of 3, the 
checkpoint_completion_target to 0.9 from the default of 0.5, and to be able 
to observe what's going on I set stats_command_string to on.

Some other details: we have 3400 nodes (dashboard is only seeing 3290 or 
so, which is part of why I want this CSV report to determine why it's a 
smaller number).  This postgresql instance is also the instance supporting 
puppetdb, though obviously a separate database.  The resource statuses 
table has 47 million rows right now, and the inner join returns 4.3 million.

I'm curious if anyone else is running this version on postgresql with a 
large environment and if there are places I ought to be looking to tune 
this so it will run faster, or if I need to be doing something to shrink 
those tables without losing information, etc.

Thanks

Pete

-- 
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/d2909399-b071-43e4-9ad8-2c9d6cbc170c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard Broken on Debian Jesse

[Geoff Goehle]

The latest round of updates to Debian Jesse (testing) has really broken 
puppet-dashboard when using the puppetlabs repo.  I currently have my apt 
sources list set up to use the "unstable" repo (since there isn't a 
"jessie" or "testing" repo).  When I try to install puppet-dashboard I get

 puppet-dashboard : Depends: ruby1.8 (>= 1.8.7) but it is not installable
> Depends: rubygems but it is not installable


This probably has something to do with the lastest upgrades to ruby that 
came down last week, which include a message that says.  

  The Ruby packages in Debian no longer support switching between different
>   Ruby versions using update-alternatives. All unversioned binary names 
> such
>   as `ruby`, `gem` etc are now provided by the `ruby` package, and will be
>   symbolic links pointing to the binaries corresponding to the current 
> default
>   version in Debian.


So it looks like the usual method of switching to ruby 1.8 wont work and as 
far as I can tell ruby 1.8 isn't even available on Debian jessie.  

Geoff.

-- 
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/2db9d6c8-b75b-4dbd-93f5-e36671821cd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard believes a node is unresponsive

[Robert Rothenberg]

Puppet Dashboard is listing a node as unresponsive for several days. But 
the agent has been running twice an hour with no errors, and a manual run 
of the agent shows it runs fine.

I cannot ping it with mcollective, and a query for disabled agents doesn't 
list it.

I looked in the logs on the node and apparently a manual run of Puppet was 
aborted, so it shows "Caught INT; calling stop".

How can I fix this?


-- 
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/a61b400c-ec1a-40b2-83f7-59deed05e0c6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard behind HTTPS

[henriquerodrigues]

Hi,

Can Puppet Master send the reports to Puppet Dashboard via HTTPS?

My Puppet Dashboard is protected with a certificate signed by another CA 
and this seems to break the sending of reports because Puppet doesn't have 
the necessary certificate to connect securely and I can't seem to make it 
work.

Thank you,
Henrique Rodrigues

-- 
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/25e293bd-41b0-4eda-b65b-bb0d82caeff3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard Groups

[kaustubh chaudhari]

Hi,

I was looking for a way to group the servers dynamically. Eg: create a 
"Windows" Group and all the existing nodes and new nodes should be part of 
"Windows" group.
I edit a group and then add each server, but practically its not possible 
with 2k servers in all!!

Is there a way to do that?

-Kaustubh

-- 
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/f38e02be-61e8-4694-aeeb-f0201d16a694%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Dashboard with Passenger - 500 Internal Server Error (Mysql::Error: Can't create/write to file Errcode: 13)

[Matheus Santos]

Hi folks, 

I am having the exact same problem. The Webrick works fine but the 
apache/passenger server does not. What would I need to have installed in 
ruby in order to ensure the connection between dashboard-passenger and the 
mysql that I don't need with the webrick? The /tmp (or do you mean the 
mysql.socket file?)  the  permission would have to be 777 right?

ps.: I also got the migration version (no_migration_check) error (probably 
because passenger can't read/write from/to mysql ) so when I set the 
env no_migration_check = 1 I got the 500 error...

Thanks!

On Monday, November 25, 2013 1:52:24 PM UTC-2, Felix.Frank wrote:
>
> Hi, 
>
> my guess would be that this error is handed through from MySQL itself. 
>
> Are there perhaps problems with the permissions on your /tmp? 
>
> It is indeed strange that Webrick behaves different from passenger for 
> this use case, though. Can you somehow make absolutely certain that ruby 
> is contacting the correct MySQL instance? 
>
> Cheers, 
> Felix 
>
> On 11/21/2013 05:40 PM, Jason Friedrich wrote: 
> > When I try to hit the site though, I am getting the message "Puppet 
> > Dashboard encountered an error. Something went wrong, and Puppet 
> > Dashboard was unable to render the requested page [...]" and a strange 
> > errror output in the production.log file (http://pastebin.com/aYYBRkEX). 
>
> > 
> > I do not understand why Puppet Dashboard tries to create a MYI file in 
> > /tmp. It should not create anything locally at all. It should use the 
> > configured MySQL server. 
>

-- 
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/cd862ddd-e8bf-4643-b59d-07f226e548c6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet-dashboard status report and bottleneck

[Stuart Cracraft]

 

All to nought. No change alas.

 

Confirmation of version:

  [root@ca-sna-pm01 puppet-dashboard]# gem list | grep rubygem

  rubygems-update (1.8.25)

  [root@ca-sna-pm01 puppet-dashboard]#

 

Retry of Schematization:

 

  [root@ca-sna-pm01 puppet-dashboard]# !1441

  rake RAILS_ENV=production db:migrate

  rake aborted!

  undefined method `source_index' for Gem:Module

 

  (See full trace by running task with --trace)

  [root@ca-sna-pm01 puppet-dashboard]#

 

The following would not be expected to work without the Schematization 
prerequisite above:

 

[root@ca-sna-pm01 puppet-dashboard]# sudo -u puppet-dashboard 
./script/server -e production

./script/../config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21:in 
`add_frozen_gem_path': undefined method `source_index\

' for Gem:Module (NoMethodError)

from ./script/../config/boot.rb:50:in `load_initializer'

from ./script/../config/boot.rb:41:in `run'

from ./script/../config/boot.rb:14:in `boot!'

from ./script/../config/boot.rb:113

from ./script/server:2:in `require'

from ./script/server:2

[root@ca-sna-pm01 puppet-dashboard]#

Stuart

On Tuesday, December 17, 2013 2:36:04 PM UTC-8, Matthaus Litteken wrote:

> Stuart, googling the rake error you were getting resulted in the following 
> hit: 
>
>
> http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror
>  
>
> Which indicated the version of rubygems is not compatible with the 
> rails application. 
>
> On Mon, Dec 16, 2013 at 10:36 PM, Stuart Cracraft 
> > 
> wrote: 
> > Thanks Ramin. 
> > 
> > A good tip. 
> > 
> > Thank-you. 
> > 
> > On Dec 16, 2013, at 1:49 PM, Ramin K > 
> wrote: 
> > 
> > No Ruby Mysql bindings aka the mysql gem. 
> > 
> > 
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies
>  
> > 
> > Ramin 
> > 
> > On 12/16/2013 12:37 PM, Stuart Cracraft wrote: 
> > 
> > And the installed gems and ruby version. 
> > 
> > [root@ca-sna-pm01 puppet-dashboard]# gem list 
> > 
> > *** LOCAL GEMS *** 
> > 
> > actionmailer (3.2.13) 
> > 
> > actionpack (3.2.13) 
> > 
> > activemodel (3.2.13) 
> > 
> > activerecord (3.2.13) 
> > 
> > activeresource (3.2.13) 
> > 
> > activesupport (3.2.13) 
> > 
> > archive-tar-minitar (0.5.2) 
> > 
> > arel (3.0.2) 
> > 
> > builder (3.0.4) 
> > 
> > bundler (1.3.5) 
> > 
> > cgi_multipart_eof_fix (2.5.0) 
> > 
> > columnize (0.3.6) 
> > 
> > daemons (1.1.9) 
> > 
> > erubis (2.7.0) 
> > 
> > fastthread (1.0.7) 
> > 
> > gem_plugin (0.2.3) 
> > 
> > hike (1.2.2) 
> > 
> > i18n (0.6.1) 
> > 
> > journey (1.0.4) 
> > 
> > json (1.8.0) 
> > 
> > mail (2.5.4) 
> > 
> > mime-types (1.23) 
> > 
> > mongrel (1.1.5) 
> > 
> > multi_json (1.7.4) 
> > 
> > polyglot (0.3.3) 
> > 
> > rack (1.4.5) 
> > 
> > rack-cache (1.2) 
> > 
> > rack-ssl (1.3.3) 
> > 
> > rack-test (0.6.2) 
> > 
> > rails (3.2.13) 
> > 
> > railties (3.2.13) 
> > 
> > rake (10.0.4) 
> > 
> > rdoc (3.12.2) 
> > 
> > rgen (0.6.2) 
> > 
> > ruby-json (1.1.2) 
> > 
> > ruby-shadow (2.2.0) 
> > 
> > ruby_core_source (0.1.5) 
> > 
> > rubygems-update (2.0.3) 
> > 
> > shadow (1.1) 
> > 
> > sprockets (2.2.2) 
> > 
> > thor (0.18.1) 
> > 
> > tilt (1.4.1) 
> > 
> > treetop (1.4.12) 
> > 
> > tzinfo (0.3.37) 
> > 
> > [root@ca-sna-pm01 puppet-dashboard]# ruby --version 
> > 
> > ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] 
> > 
> > [root@ca-sna-pm01 puppet-dashboard]# 
> > 
> > 
> > 
> > On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote: 
> > 
> >I followed: 
> > 
> >http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html 
> > 
> > 
> >and have reached the point after 
> > 
> >   puppet dashboard install/configuration 
> >   MySQL server and MySQL client installation/configuration/startup 
> > 
> >at 
> > 
> >   Preparing Schema 
> > 
> >and now receive the error: 
> > 
> >   rake RAILS_ENV=production db_migrate 
> >   rake aborted! 
> >   undefined method `source_index' for Gem:Module 
> > 
> >   See full trace by running task with --trace 
> > 
> >the above was run while connected to /usr/share/puppet-dashboard 
> >where there is a project Rakefile which the above uses. 
> > 
> >Any thoughts on the above and how to get past it? 
> > 
> >Thanks so much! 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > 
> > -- 
> > You received this message because y

Re: [Puppet Users] puppet-dashboard status report and bottleneck

[Matthaus Owens]

Stuart, googling the rake error you were getting resulted in the following hit:

http://stackoverflow.com/questions/15349869/undefined-method-source-index-for-gemmodule-nomethoderror

Which indicated the version of rubygems is not compatible with the
rails application.

On Mon, Dec 16, 2013 at 10:36 PM, Stuart Cracraft  wrote:
> Thanks Ramin.
>
> A good tip.
>
> Thank-you.
>
> On Dec 16, 2013, at 1:49 PM, Ramin K  wrote:
>
> No Ruby Mysql bindings aka the mysql gem.
>
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies
>
> Ramin
>
> On 12/16/2013 12:37 PM, Stuart Cracraft wrote:
>
> And the installed gems and ruby version.
>
> [root@ca-sna-pm01 puppet-dashboard]# gem list
>
> *** LOCAL GEMS ***
>
> actionmailer (3.2.13)
>
> actionpack (3.2.13)
>
> activemodel (3.2.13)
>
> activerecord (3.2.13)
>
> activeresource (3.2.13)
>
> activesupport (3.2.13)
>
> archive-tar-minitar (0.5.2)
>
> arel (3.0.2)
>
> builder (3.0.4)
>
> bundler (1.3.5)
>
> cgi_multipart_eof_fix (2.5.0)
>
> columnize (0.3.6)
>
> daemons (1.1.9)
>
> erubis (2.7.0)
>
> fastthread (1.0.7)
>
> gem_plugin (0.2.3)
>
> hike (1.2.2)
>
> i18n (0.6.1)
>
> journey (1.0.4)
>
> json (1.8.0)
>
> mail (2.5.4)
>
> mime-types (1.23)
>
> mongrel (1.1.5)
>
> multi_json (1.7.4)
>
> polyglot (0.3.3)
>
> rack (1.4.5)
>
> rack-cache (1.2)
>
> rack-ssl (1.3.3)
>
> rack-test (0.6.2)
>
> rails (3.2.13)
>
> railties (3.2.13)
>
> rake (10.0.4)
>
> rdoc (3.12.2)
>
> rgen (0.6.2)
>
> ruby-json (1.1.2)
>
> ruby-shadow (2.2.0)
>
> ruby_core_source (0.1.5)
>
> rubygems-update (2.0.3)
>
> shadow (1.1)
>
> sprockets (2.2.2)
>
> thor (0.18.1)
>
> tilt (1.4.1)
>
> treetop (1.4.12)
>
> tzinfo (0.3.37)
>
> [root@ca-sna-pm01 puppet-dashboard]# ruby --version
>
> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>
> [root@ca-sna-pm01 puppet-dashboard]#
>
>
>
> On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote:
>
>I followed:
>
>http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>
>
>and have reached the point after
>
>   puppet dashboard install/configuration
>   MySQL server and MySQL client installation/configuration/startup
>
>at
>
>   Preparing Schema
>
>and now receive the error:
>
>   rake RAILS_ENV=production db_migrate
>   rake aborted!
>   undefined method `source_index' for Gem:Module
>
>   See full trace by running task with --trace
>
>the above was run while connected to /usr/share/puppet-dashboard
>where there is a project Rakefile which the above uses.
>
>Any thoughts on the above and how to get past it?
>
>Thanks so much!
>
> --
> 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/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/jXit5cwjA9g/unsubscribe.
> To unsubscribe from this group and all its topics, 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/52AF7562.4050209%40badapple.net.
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/7129942C-D5D2-4CAE-8456-B8AEBB27C76C%40me.com.
>
> For more options, visit https://groups.google.com/groups/opt_out.



-- 
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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%3DwAdCpvta%3DQu0Y87G5M-9GZcrMYZjcnVQK9FxwUWYqMq4Tw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet-dashboard status report and bottleneck

[Stuart Cracraft]

Thanks Ramin.

A good tip.

Thank-you.

On Dec 16, 2013, at 1:49 PM, Ramin K  wrote:

> No Ruby Mysql bindings aka the mysql gem.
> 
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-dependencies
> 
> Ramin
> 
> On 12/16/2013 12:37 PM, Stuart Cracraft wrote:
>> And the installed gems and ruby version.
>> 
>> [root@ca-sna-pm01 puppet-dashboard]# gem list
>> 
>> *** LOCAL GEMS ***
>> 
>> actionmailer (3.2.13)
>> 
>> actionpack (3.2.13)
>> 
>> activemodel (3.2.13)
>> 
>> activerecord (3.2.13)
>> 
>> activeresource (3.2.13)
>> 
>> activesupport (3.2.13)
>> 
>> archive-tar-minitar (0.5.2)
>> 
>> arel (3.0.2)
>> 
>> builder (3.0.4)
>> 
>> bundler (1.3.5)
>> 
>> cgi_multipart_eof_fix (2.5.0)
>> 
>> columnize (0.3.6)
>> 
>> daemons (1.1.9)
>> 
>> erubis (2.7.0)
>> 
>> fastthread (1.0.7)
>> 
>> gem_plugin (0.2.3)
>> 
>> hike (1.2.2)
>> 
>> i18n (0.6.1)
>> 
>> journey (1.0.4)
>> 
>> json (1.8.0)
>> 
>> mail (2.5.4)
>> 
>> mime-types (1.23)
>> 
>> mongrel (1.1.5)
>> 
>> multi_json (1.7.4)
>> 
>> polyglot (0.3.3)
>> 
>> rack (1.4.5)
>> 
>> rack-cache (1.2)
>> 
>> rack-ssl (1.3.3)
>> 
>> rack-test (0.6.2)
>> 
>> rails (3.2.13)
>> 
>> railties (3.2.13)
>> 
>> rake (10.0.4)
>> 
>> rdoc (3.12.2)
>> 
>> rgen (0.6.2)
>> 
>> ruby-json (1.1.2)
>> 
>> ruby-shadow (2.2.0)
>> 
>> ruby_core_source (0.1.5)
>> 
>> rubygems-update (2.0.3)
>> 
>> shadow (1.1)
>> 
>> sprockets (2.2.2)
>> 
>> thor (0.18.1)
>> 
>> tilt (1.4.1)
>> 
>> treetop (1.4.12)
>> 
>> tzinfo (0.3.37)
>> 
>> [root@ca-sna-pm01 puppet-dashboard]# ruby --version
>> 
>> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>> 
>> [root@ca-sna-pm01 puppet-dashboard]#
>> 
>> 
>> 
>> On Monday, December 16, 2013 11:46:04 AM UTC-8, Stuart Cracraft wrote:
>> 
>>I followed:
>> 
>>http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>>
>> 
>>and have reached the point after
>> 
>>   puppet dashboard install/configuration
>>   MySQL server and MySQL client installation/configuration/startup
>> 
>>at
>> 
>>   Preparing Schema
>> 
>>and now receive the error:
>> 
>>   rake RAILS_ENV=production db_migrate
>>   rake aborted!
>>   undefined method `source_index' for Gem:Module
>> 
>>   See full trace by running task with --trace
>> 
>>the above was run while connected to /usr/share/puppet-dashboard
>>where there is a project Rakefile which the above uses.
>> 
>>Any thoughts on the above and how to get past it?
>> 
>>Thanks so much!
>> 
>> --
>> 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/ee0f339d-79f4-4622-bd51-3a2872d5aa48%40googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Puppet Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/puppet-users/jXit5cwjA9g/unsubscribe.
> To unsubscribe from this group and all its topics, 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/52AF7562.4050209%40badapple.net.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7129942C-D5D2-4CAE-8456-B8AEBB27C76C%40me.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet-dashboard status report and bottleneck

[Stuart Cracraft]

I followed:

  http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html

and have reached the point after

  puppet dashboard install/configuration
  MySQL server and MySQL client installation/configuration/startup

at

  Preparing Schema

and now receive the error:

  rake RAILS_ENV=production db_migrate
  rake aborted!
  undefined method `source_index' for Gem:Module

  See full trace by running task with --trace

the above was run while connected to /usr/share/puppet-dashboard
where there is a project Rakefile which the above uses.

Any thoughts on the above and how to get past it?

Thanks so much!

-- 
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/af1c62c9-dd67-4818-a069-68690fa7308e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard: how to connect?

[Stuart Cracraft]

Hi - I run puppet 3.3.2 currently of Open Source Puppet.

I am looking for anyone who has run Puppet Dashboard.

How do I connect to the dashboard?

Stuart

-- 
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/270ebc67-7884-401b-8503-7823c6aa1624%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet dashboard & ssl database connection

[Juan Sierra Pons]

Hi,

I am configuring my puppet-dasbboard to connect to a ssl encrypted
mysql DB server

The mysql server is configured OK as using the mysql client with the
--ssl-ca works ok

mysql -u dashboard -p -h mysql.example.org --ssl-ca=/etc/mysql/ca.pem
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 103

But modifying the /etc/puppet-dashboard/database.yml and adding the
sslca line doesn't work:
host: mysql.example.org
sslca: /etc/mysql/ROOTCA-eltorete.com-cacert.pem

Any idea what am I missing?

Best regards

--
Juan Sierra Pons j...@elsotanillo.net
Linux User Registered: #257202
Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo
GPG key = 0xA110F4FE
Key Fingerprint = DF53 7415 0936 244E 9B00  6E66 E934 3406 A110 F4FE
--

-- 
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/CABS%3Dy9va61b4W4T15gvfXaKO-4b75TqS8B9v1e9PcRsxf2bqXA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet dashboard data internally inconsistent

[Sam Tresler]

https://www.dropbox.com/s/0vao04js5v7edga/Screenshot%20-%2011262013%20-%2011%3A31%3A35%20AM.png

In the attached screenshot you can see that the last report was 10:07. The 
graph definitely shows an 11:36 run, and the dashboard activity shows that 
the nod was updated at 11:05. 

Puppet dashboard is getting reports from over 300 nodes. CPU is maxed, but 
pending tasks are consistently 1-2, and the machine isn't overloaded. Came 
in this morning to 80ish Unreported Nodes. Most nodes are still reporting 
and not exhibiting this behavior. The nodes in showing as unreported all 
have similar traits as the screenshot - data is getting to the dashboard 
somehow, but dashboard is not registering it as a report. 

Any ideas what is going on here? 

-- 
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/1f87f425-7030-497a-9377-823adc9695a2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Dashboard with Passenger - 500 Internal Server Error (Mysql::Error: Can't create/write to file Errcode: 13)

[Felix Frank]

Hi,

my guess would be that this error is handed through from MySQL itself.

Are there perhaps problems with the permissions on your /tmp?

It is indeed strange that Webrick behaves different from passenger for
this use case, though. Can you somehow make absolutely certain that ruby
is contacting the correct MySQL instance?

Cheers,
Felix

On 11/21/2013 05:40 PM, Jason Friedrich wrote:
> When I try to hit the site though, I am getting the message "Puppet
> Dashboard encountered an error. Something went wrong, and Puppet
> Dashboard was unable to render the requested page [...]" and a strange
> errror output in the production.log file (http://pastebin.com/aYYBRkEX).
> 
> I do not understand why Puppet Dashboard tries to create a MYI file in
> /tmp. It should not create anything locally at all. It should use the
> configured MySQL server.

-- 
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/52937238.2020502%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard 1.2.1

[GregC]

Anyone know where I can find rake node commands for Dashboard 1.2.1?

 I know this is an older release of the dashboard but the only documents I 
can find are for 1.24 and higher.

I would like to be able to remove a node from Puppet Dashboard

The doc says the following but this does not work in dashboard 1.2.1, here 
is what I get when run, Any clarification would be appreciated.


*rake node:del name=hostname --trace*


(in /usr/share/puppet-dashboard)
DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
deprecated. Use lib/tasks instead. (called from 
/usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)
rake aborted!
Don't know how to build task 'node:del'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1727:in `[]'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2049:in `invoke_task'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2028:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2028:in `each'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2028:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2067:in 
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2022:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2067:in 
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1997:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
/usr/bin/rake:19:in `load'
/usr/bin/rake:19

-- 
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/3822ffe7-36a7-402c-86fe-483a99ed5801%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard with Passenger - 500 Internal Server Error (Mysql::Error: Can't create/write to file Errcode: 13)

[Jason Friedrich]

Distribution: Ubuntu 12.04.3
Ruby version: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Gem version: 1.8.15
Puppet version: 3.3.2-1puppetlabs1 (Puppetlabs apt repo)
Puppet Dashboard: 1.2.23-1puppetlabs1 (Puppetlabs apt repo)


I have successfully set up a puppet master, with two agents and the 
Puppet Dashboard following the instructions from the puppetlabs web 
site. When I use the internal, built-in web server, everything seems to 
work fine. Even though the init scripts in the Ubuntu packages seem to 
have a bug or two, it worked fine for me.


Now I wanted to move everything to the apache web server, as a test for 
a bigger environment later. The puppetmaster was easily set up, the 
puppetmaster-passenger deb works really great, like a charm.


With the install/config of the Puppet Dashboard in Apache2 I have more 
problems. I have edited the settings.yml file 
(http://pastebin.com/UUDKaJTi) and the database.yml 
(http://pastebin.com/mpznUhdQ) to configure the Dashboard and the MySQL 
database I use. I have copied the config.ru 
(http://pastebin.com/myZzrA9p) file to the /usr/share/puppet-dashboard 
directory and created the Apache configuration 
(http://pastebin.com/XDpSkvbk).


When I try to hit the site though, I am getting the message "Puppet 
Dashboard encountered an error. Something went wrong, and Puppet 
Dashboard was unable to render the requested page [...]" and a strange 
errror output in the production.log file (http://pastebin.com/aYYBRkEX).


I do not understand why Puppet Dashboard tries to create a MYI file in 
/tmp. It should not create anything locally at all. It should use the 
configured MySQL server.


When I execute

rake RAILS_ENV=production db:migration

in the Puppet Dashboard Directory, I get the same the same error. All 
these settings worked fine when I used the built-in Webrick, so I do not 
quite understand why this happens right now.


Hope that someone can help and put me on the right track.

Thanks,
-Jason

--
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/528E378A.9040700%40probytes.eu.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet dashboard config for node request

[kaustubh chaudhari]

Sorry if this is a duplicate request. Unable to see my previous post, hence 
resending!


I am trying to have a node request tab in puppet-dashboard in the open 
source version, In PE we have this tab to accept / reject node request.

Can we configure the same in open source puppet dashboard ?

Kaustubh 

-- 
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/194a18e4-68b8-4ec8-8fef-5f0a7b3b2f7c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard Question

[GregC]

I am trying to pull information down to my dashboard server one of my 
Puppet master. I can do the following and retrieve inventory information 
without any issue using API

curl -k -H "Accept: yaml" https://puppet:8140/production/facts/node

But when I try to retrive the same facts from Puppet Dashboard it says:

Inventory
Could not retrieve facts from inventory service: 404 "Not Found"

I am using Puppet Dashboard 1.2.1. All fact information is correct per 
documentation in auth.conf, is there something specific to Puppet Dashboard 
that is causing this to not work?

Would appreciate any insight,


-- 
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/0e1eb4b4-fe87-488a-b695-8860efd9a8c4%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard web interface

[Jason Antman]

Oh wow. I shouldn't comment before I have my coffee. Yes you have it
exactly right, if you call the parameter "env", it will show up as
"$::env". I've fixed the example below.

-jantman

On 11/13/2013 08:50 AM, Thomas RICOU wrote:
> Hi, I think you understood quite well my question even if  I was not
> so clear... ;)
>
> Anyway, according to what you say, let's say that my (ENC) group is
> named 'DEVEL' and the var named 'env' is set to 'devel'. I add the
> node 'foo.example.com' to the 'DEVEL' group. Shouldn't the var be
> named '::env' instead of '::foo' ? Because when I addthe node
> 'bar.example.com' to that same group, the variable will be '::env' or
> '::bar' ?
>
> Thx
> Tom
>
> Le mercredi 13 novembre 2013 13:29:44 UTC+1, Jason Antman a écrit :
>
> Tom,
>
> I'm not sure I totally understand your question; I've also never
> used an
> ENC (like dashboard) with default.pp, only with modules.
>
> If you set a parameter called "env" on a group in Dashboard, and then
> add node "foo.example.com " to that group,
> the parameter will available
> in puppet as a top-scope/global variable, i.e. $::env.
>
> Is that what you were asking?
>
> -jantman
>
> On 11/13/2013 06:54 AM, Thomas RICOU wrote:
> > Hi
> >
> > I'm kinda noobish to puppet and I can't find an answer to my
> question.
> > What can I can do with the dashboard groups ? In fact I'm
> interested
> > in setting a var "env" to a value in ['devel','valid','prod']. this
> > value should be set only once when I create a new virtual machine
> > using a puppet agent. The thing is that this machine will use a
> > "default" node configuration which needs to know the value of the
> > "env" var. For some reasons, I don' t want to create a node file
> per
> > machine setting this param so I searched for something very easy
> to do
> > so. I found the "Groups" I saw in the dashboard web interface
> and in
> > which I created that "env" var but I can't figure out how to get
> it's
> > value back in default.pp node file.
> >
> > Am I completely wrong using these Groups?
> >
> > Thanks
> >
> > Tom
> > --
> > 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...@googlegroups.com .
> > To view this discussion on the web visit
> >
> 
> https://groups.google.com/d/msgid/puppet-users/d267b355-fc88-4f23-b60e-dffcb7f12de1%40googlegroups.com
> 
> .
>
> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/ba237ea7-16d8-406c-b9de-27ef2728e1ec%40googlegroups.com.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5283D54B.3040907%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard web interface

[Thomas RICOU]

Well, I tried, and (even in default.pp) i can access the var with $::env.

Thanks anyway.

Le mercredi 13 novembre 2013 14:50:56 UTC+1, Thomas RICOU a écrit :
>
> Hi, I think you understood quite well my question even if  I was not so 
> clear... ;)
>
> Anyway, according to what you say, let's say that my (ENC) group is named 
> 'DEVEL' and the var named 'env' is set to 'devel'. I add the node '
> foo.example.com' to the 'DEVEL' group. Shouldn't the var be named '::env' 
> instead of '::foo' ? Because when I addthe node 'bar.example.com' to that 
> same group, the variable will be '::env' or '::bar' ?
>
> Thx
> Tom
>
> Le mercredi 13 novembre 2013 13:29:44 UTC+1, Jason Antman a écrit :
>>
>> Tom, 
>>
>> I'm not sure I totally understand your question; I've also never used an 
>> ENC (like dashboard) with default.pp, only with modules. 
>>
>> If you set a parameter called "env" on a group in Dashboard, and then 
>> add node "foo.example.com" to that group, the parameter will available 
>> in puppet as a top-scope/global variable, i.e. $::foo. 
>>
>> Is that what you were asking? 
>>
>> -jantman 
>>
>> On 11/13/2013 06:54 AM, Thomas RICOU wrote: 
>> > Hi 
>> > 
>> > I'm kinda noobish to puppet and I can't find an answer to my question. 
>> > What can I can do with the dashboard groups ? In fact I'm interested 
>> > in setting a var "env" to a value in ['devel','valid','prod']. this 
>> > value should be set only once when I create a new virtual machine 
>> > using a puppet agent. The thing is that this machine will use a 
>> > "default" node configuration which needs to know the value of the 
>> > "env" var. For some reasons, I don' t want to create a node file per 
>> > machine setting this param so I searched for something very easy to do 
>> > so. I found the "Groups" I saw in the dashboard web interface and in 
>> > which I created that "env" var but I can't figure out how to get it's 
>> > value back in default.pp node file. 
>> > 
>> > Am I completely wrong using these Groups? 
>> > 
>> > Thanks 
>> > 
>> > Tom 
>> > -- 
>> > 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...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/puppet-users/d267b355-fc88-4f23-b60e-dffcb7f12de1%40googlegroups.com.
>>  
>>
>> > 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0e39d7ea-a59d-47d8-aa08-edba39a76866%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard web interface

[Thomas RICOU]

Hi, I think you understood quite well my question even if  I was not so 
clear... ;)

Anyway, according to what you say, let's say that my (ENC) group is named 
'DEVEL' and the var named 'env' is set to 'devel'. I add the node 
'foo.example.com' to the 'DEVEL' group. Shouldn't the var be named '::env' 
instead of '::foo' ? Because when I addthe node 'bar.example.com' to that 
same group, the variable will be '::env' or '::bar' ?

Thx
Tom

Le mercredi 13 novembre 2013 13:29:44 UTC+1, Jason Antman a écrit :
>
> Tom, 
>
> I'm not sure I totally understand your question; I've also never used an 
> ENC (like dashboard) with default.pp, only with modules. 
>
> If you set a parameter called "env" on a group in Dashboard, and then 
> add node "foo.example.com" to that group, the parameter will available 
> in puppet as a top-scope/global variable, i.e. $::foo. 
>
> Is that what you were asking? 
>
> -jantman 
>
> On 11/13/2013 06:54 AM, Thomas RICOU wrote: 
> > Hi 
> > 
> > I'm kinda noobish to puppet and I can't find an answer to my question. 
> > What can I can do with the dashboard groups ? In fact I'm interested 
> > in setting a var "env" to a value in ['devel','valid','prod']. this 
> > value should be set only once when I create a new virtual machine 
> > using a puppet agent. The thing is that this machine will use a 
> > "default" node configuration which needs to know the value of the 
> > "env" var. For some reasons, I don' t want to create a node file per 
> > machine setting this param so I searched for something very easy to do 
> > so. I found the "Groups" I saw in the dashboard web interface and in 
> > which I created that "env" var but I can't figure out how to get it's 
> > value back in default.pp node file. 
> > 
> > Am I completely wrong using these Groups? 
> > 
> > Thanks 
> > 
> > Tom 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/d267b355-fc88-4f23-b60e-dffcb7f12de1%40googlegroups.com.
>  
>
> > 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/ba237ea7-16d8-406c-b9de-27ef2728e1ec%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard web interface

[Jason Antman]

Tom,

I'm not sure I totally understand your question; I've also never used an
ENC (like dashboard) with default.pp, only with modules.

If you set a parameter called "env" on a group in Dashboard, and then
add node "foo.example.com" to that group, the parameter will available
in puppet as a top-scope/global variable, i.e. $::foo.

Is that what you were asking?

-jantman

On 11/13/2013 06:54 AM, Thomas RICOU wrote:
> Hi
>
> I'm kinda noobish to puppet and I can't find an answer to my question.
> What can I can do with the dashboard groups ? In fact I'm interested
> in setting a var "env" to a value in ['devel','valid','prod']. this
> value should be set only once when I create a new virtual machine
> using a puppet agent. The thing is that this machine will use a
> "default" node configuration which needs to know the value of the
> "env" var. For some reasons, I don' t want to create a node file per
> machine setting this param so I searched for something very easy to do
> so. I found the "Groups" I saw in the dashboard web interface and in
> which I created that "env" var but I can't figure out how to get it's
> value back in default.pp node file.
>
> Am I completely wrong using these Groups?
>
> Thanks
>
> Tom
> -- 
> 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/d267b355-fc88-4f23-b60e-dffcb7f12de1%40googlegroups.com.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/528370B8.2090103%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet dashboard web interface

[Thomas RICOU]

Hi

I'm kinda noobish to puppet and I can't find an answer to my question. What 
can I can do with the dashboard groups ? In fact I'm interested in setting 
a var "env" to a value in ['devel','valid','prod']. this value should be 
set only once when I create a new virtual machine using a puppet agent. The 
thing is that this machine will use a "default" node configuration which 
needs to know the value of the "env" var. For some reasons, I don' t want 
to create a node file per machine setting this param so I searched for 
something very easy to do so. I found the "Groups" I saw in the dashboard 
web interface and in which I created that "env" var but I can't figure out 
how to get it's value back in default.pp node file.

Am I completely wrong using these Groups?

Thanks

Tom

-- 
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/d267b355-fc88-4f23-b60e-dffcb7f12de1%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48

[lkorcutt]

I'm running into this with the current forge modules from puppetlabs for 
apache (0.9.0 )and puppet-dashboard (0.0.4). Do you know when an update 
will be published on the forge?

Thanks

On Sunday, September 8, 2013 12:19:35 PM UTC-6, blkperl wrote:
>
> The bug is fixed in the master branch on Github. I'll see about  getting a 
> new release on the forge.
>
> Cheers,
> William
>
>
> On Wed, Sep 4, 2013 at 5:31 PM, Cory Stoker 
> > wrote:
>
>> Look at the apache::vhost definition.  It looks to me that "template"
>> is no longer a parameter to the defined type.  Since this looks like
>> puppetlabs-dashboard I would check out the puppetlabs-apache module to
>> find the apache::vhost defined type in
>> puppetlabs-apache/manifest/vhost.pp.  If the parameter is not declared
>> in the type then you will need to remove that line and figure out what
>> you do need to declare in passenger.pp for the apache::vhost resource.
>>  It looks to me like $template was a parameter in older versions of
>> that module (0.4.0) but is now gone in the current version.
>>
>> HTH
>>
>> On Wed, Sep 4, 2013 at 8:08 AM, Mr. Vitriol 
>> > 
>> wrote:
>> > Hi,
>> > I am new to the job and forum. I installed puppet and puppetmaster and 
>> set
>> > up my first dependencies acording to a manual that we have here in our
>> > company. Everything works fine and I can set up new nodes with several
>> > modules to choose from. Unfortunatley the Dashboard gives me errors 
>> instead
>> > of starting correctley.
>> >
>> > Here the message:
>> >
>> > Error: Could not retrieve catalog from remote server: Error 400 on 
>> SERVER:
>> > Invalid parameter template at
>> > /etc/puppet/modules/dashboard/manifests/passenger.pp:48 on node
>> > puppet-master.defaultdomain
>> > Warning: Not using cache on failed catalog
>> > Error: Could not retrieve catalog; skipping run
>> >
>> > The relevant passage from the passenger is:
>> >
>> > # Class: dashboard::passenger
>> > #
>> > # This class configures parameters for the puppet-dashboard module.
>> > #
>> > # Parameters:
>> > #   [*dashboard_site*]
>> > # - The ServerName setting for Apache
>> > #
>> > #   [*dashboard_port*]
>> > # - The port on which puppet-dashboard should run
>> > #
>> > #   [*dashboard_config*]
>> > # - The Dashboard configuration file
>> > #
>> > #   [*dashboard_root*]
>> > # - The path to the Puppet Dashboard library
>> > #
>> > # Actions:
>> > #
>> > # Requires:
>> > #
>> > # Sample Usage:
>> > #
>> > class dashboard::passenger (
>> >   $dashboard_site,
>> >   $dashboard_port,
>> >   $dashboard_config,
>> >   $dashboard_root
>> > ) inherits dashboard {
>> >
>> >   require ::passenger
>> >   include apache
>> >
>> >   file { '/etc/init.d/puppet-dashboard':
>> > ensure => absent,
>> >   }
>> >
>> >   file { 'dashboard_config':
>> > ensure => absent,
>> > path   => $dashboard_config,
>> >   }
>> >
>> >   apache::vhost { $dashboard_site:
>> > port => $dashboard_port,
>> > priority => '50',
>> > docroot  => "${dashboard_root}/public",
>> > template => 'dashboard/passenger-vhost.erb',
>> >   }
>> > }
>> >
>> > That is the default version, since I didn't add anything.
>> >
>> > I hope someone can help me with this, google wasn't able to.
>> >
>> > 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...@googlegroups.com .
>> > To post to this group, send email to 
>> > puppet...@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...@googlegroups.com .
>> To post to this group, send email to puppet...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Thanks,
> William
>  

-- 
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/364fc105-1b88-41a0-91da-84c7bb0edc22%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet dashboard blank stylesheet

[Fine, Thomas]

Hi,

I'm trying to switch my working puppet-dashboard installation over from the
test server that it comes with to an Apache/Passenger setup.  Puppet seems
to be humming along just fine under this setup, but dashboard is unhappy.
 The web interface comes up with no style. I've taken a look with Safari's
developer windows at what it thinks is going on and I'm seeing an all.cis
that is coming up empty.  And yet the transfer logs show a sizable all.css
being transferred, and if I grab all.css directly I end up with content.

I do see that there's a bug (8121) on something like this, but as far as I
can tell, my version of puppet-dashboard (xxx) is greater than the version
where that bug is fixed.

It seems likely that something has gone miss in the whole
Apache-Passenger-Rails relationship, but I don't know enough about this to
figure out how to debug it.

Any ideas?

The server is Centos6
Apache is 2.2.15
Puppet is 3.2.4
Puppet-dashboard is 1.2.23
Ruby is 1.8.7
Passenger is 4.0.19

Thanks in advance,

  tom

-- 
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 Dashboard Radiator view thru iframe

[Matt Shields]

Is it possible to create an iframe in an html page and display the Radiator
view in the Puppet Dashboard?  For some reason all my other NOC iframe's
are displaying with the exception of the Radiator view

Matt

-- 
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-dashboard cert::create_key_pair and cert::request fails

[Robert Schaffar-Taurok]

Hi!

I am already successfully using puppet with puppet-dashboard in my 
environment and would like to extend this to display the facts in 
puppet-dashboard.
I understand that I need a puppetdb for that. Which I installed and I 
already get successfull log messages there that facts are stored. So until 
now everything seems to work.

Now I want to connect dashboard to puppetmaster and from the documentation 
I read that I need to do the following:

$ sudo -u puppet-dashboard rake cert:create_key_pair $ sudo -u 
puppet-dashboard rake cert:request

Well, I used the puppetlabs apt repository to install, so the users are 
different. But what I do is:

cd /usr/share/puppet-dashboard
su www-data -c "rake cert:create_key_pair --trace"
su www-data -c "rake cert:request --trace"

The first thing is that with create_key_pair I get a "Key(s) already 
exist." error message.
Because for some reason the method is called twice. I ignore this, as 
afterwards I successfully find a public and private key in the 
/usr/share/puppet-dashboard/certs directory. But nothing else. If there 
should be more there at this point, please tell me so. Just the public and 
private pem.

At issuing the cert:request command, I get the following error:

"SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: 
certificate verify failed"
and I don't find any request on the puppetmaster. (puppet cert list)

My setup is that, puppetmaster, puppetdb and puppet-dashboard are all 
running on the same host.

What I already tried:
- Copying certs from the /var/lib/puppet/ssl directory and skip the create 
and sign steps. But this doesn't work. Could easily be that I copied wrong 
files. The puppet-dashboard issues the same error message on the node view 
btw. (With or without keys in the puppet-dashboard/certs directory. The 
only time I get another error there is when I give the files in the certs 
directory a wrong permission. So it looks like it is looking at the 
expected location)
- Debugging a little bit. But couldn't find out more. And I don't get a 
better error message from the ssl code.
- Playing around for a day now. So I'm giving up. I need help :)

Installed puppet packages:

ii  puppet  3.3.1-1puppetlabs1all   
   Centralized configuration management - agent startup and compatibility 
scripts
ii  puppet-common   3.3.1-1puppetlabs1all   
   Centralized configuration management
ii  puppet-dashboard1.2.23-1puppetlabs1   all   
   Dashboard for Puppet
ii  puppetdb1.5.0-1puppetlabs1all   
   PuppetDB Centralized Storage.
ii  puppetdb-terminus   1.5.0-1puppetlabs1all   
   Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
ii  puppetlabs-release  1.0-7 all   
   "Package to install Puppet Labs gpg key and apt repo"
ii  puppetmaster3.3.1-1puppetlabs1all   
   Centralized configuration management - master startup and compatibility 
scripts
ii  puppetmaster-common 3.3.1-1puppetlabs1all   
   Puppet master common scripts

Debian Version: wheezy

Thanks in advance for any help,
Robert

-- 
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 dashboard stuck pending jobs - MySql Error: Incorrect string value

[Julien Nephtali]

Hi have add issues with stuck pending jobs on my puppet dashboard.

Here is the error message from my delayed_job.log file in 
/usr/share/puppet-dashboard/log directory.

Report.create_from_yaml_file failed with ActiveRecord::StatementInvalid: 
Mysql::Error: Incorrect string value: '\x96 $bas...' for column 'details' 
at row 1: INSERT INTO `delayed_job_failures`

As anyone encountered this error before ?


-- 
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] puppet dashboard with \n\n\n

[Matt Zagrabelny]

On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons  wrote:
>
> El 03/10/2013 14:00, "Matt Zagrabelny"  escribió:
>
>
>>
>> Greetings,
>>
>> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18.
>>
>> I am seeing many \n strings all over the place when looking at
>> reports. Specifically the \n's are in the Metrics, Log, Events links.
>>
>> My nodes are showing up okay, and it seems just to be a problem with
>> the reports. For instance, a Metrics page starts with:
>>
>> \n
>> \n
>> Metrics
>> \n
>> \n
>> Events
>>
>> \n\n\n\n\n\n\n\n\n
>>
>> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not
>> yield any hints.
>>
>> Thanks!
>>
>> -mz
>>
>> --
>> 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.
> Hi
>
> I had the same problem and the problem was in the ruby version
>
> Which one are you using?

realpath =ruby
/usr/bin/ruby1.9.1


> Check the dashboard webpage to find out wich one is the right one.

Looks like 1.8 is what is needed.

Looks like that worked!

Thanks!

-mz

-- 
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] puppet dashboard with \n\n\n

[Juan Sierra Pons]

El 03/10/2013 14:00, "Matt Zagrabelny"  escribió:
>
> Greetings,
>
> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18.
>
> I am seeing many \n strings all over the place when looking at
> reports. Specifically the \n's are in the Metrics, Log, Events links.
>
> My nodes are showing up okay, and it seems just to be a problem with
> the reports. For instance, a Metrics page starts with:
>
> \n
> \n
> Metrics
> \n
> \n
> Events
>
> \n\n\n\n\n\n\n\n\n
>
> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not
> yield any hints.
>
> Thanks!
>
> -mz
>
> --
> 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.
Hi

I had the same problem and the problem was in the ruby version

Which one are you using?

Check the dashboard webpage to find out wich one is the right one.

Regards

-- 
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 dashboard with \n\n\n

[Matt Zagrabelny]

Greetings,

I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18.

I am seeing many \n strings all over the place when looking at
reports. Specifically the \n's are in the Metrics, Log, Events links.

My nodes are showing up okay, and it seems just to be a problem with
the reports. For instance, a Metrics page starts with:

\n
\n
Metrics
\n
\n
Events

\n\n\n\n\n\n\n\n\n

Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not
yield any hints.

Thanks!

-mz

-- 
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] Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48

[William Van Hevelingen]

The bug is fixed in the master branch on Github. I'll see about  getting a
new release on the forge.

Cheers,
William


On Wed, Sep 4, 2013 at 5:31 PM, Cory Stoker  wrote:

> Look at the apache::vhost definition.  It looks to me that "template"
> is no longer a parameter to the defined type.  Since this looks like
> puppetlabs-dashboard I would check out the puppetlabs-apache module to
> find the apache::vhost defined type in
> puppetlabs-apache/manifest/vhost.pp.  If the parameter is not declared
> in the type then you will need to remove that line and figure out what
> you do need to declare in passenger.pp for the apache::vhost resource.
>  It looks to me like $template was a parameter in older versions of
> that module (0.4.0) but is now gone in the current version.
>
> HTH
>
> On Wed, Sep 4, 2013 at 8:08 AM, Mr. Vitriol 
> wrote:
> > Hi,
> > I am new to the job and forum. I installed puppet and puppetmaster and
> set
> > up my first dependencies acording to a manual that we have here in our
> > company. Everything works fine and I can set up new nodes with several
> > modules to choose from. Unfortunatley the Dashboard gives me errors
> instead
> > of starting correctley.
> >
> > Here the message:
> >
> > Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER:
> > Invalid parameter template at
> > /etc/puppet/modules/dashboard/manifests/passenger.pp:48 on node
> > puppet-master.defaultdomain
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> >
> > The relevant passage from the passenger is:
> >
> > # Class: dashboard::passenger
> > #
> > # This class configures parameters for the puppet-dashboard module.
> > #
> > # Parameters:
> > #   [*dashboard_site*]
> > # - The ServerName setting for Apache
> > #
> > #   [*dashboard_port*]
> > # - The port on which puppet-dashboard should run
> > #
> > #   [*dashboard_config*]
> > # - The Dashboard configuration file
> > #
> > #   [*dashboard_root*]
> > # - The path to the Puppet Dashboard library
> > #
> > # Actions:
> > #
> > # Requires:
> > #
> > # Sample Usage:
> > #
> > class dashboard::passenger (
> >   $dashboard_site,
> >   $dashboard_port,
> >   $dashboard_config,
> >   $dashboard_root
> > ) inherits dashboard {
> >
> >   require ::passenger
> >   include apache
> >
> >   file { '/etc/init.d/puppet-dashboard':
> > ensure => absent,
> >   }
> >
> >   file { 'dashboard_config':
> > ensure => absent,
> > path   => $dashboard_config,
> >   }
> >
> >   apache::vhost { $dashboard_site:
> > port => $dashboard_port,
> > priority => '50',
> > docroot  => "${dashboard_root}/public",
> > template => 'dashboard/passenger-vhost.erb',
> >   }
> > }
> >
> > That is the default version, since I didn't add anything.
> >
> > I hope someone can help me with this, google wasn't able to.
> >
> > 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.
>
> --
> 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.
>



-- 
Thanks,
William

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

[Ankit Mittal]

Dear All,

Please help to find the latest version of puppet Dashboard in which i can 
use postgre database.

-- 
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] puppet dashboard

[Peter Bukowinski]

Postgres will be supported in Dashboard 2.0, but it has not been released yet. 
When it is released, you will find it here:
https://github.com/sodabrew/puppet-dashboard

While you're waiting, you can watch the talk that Dashboard's new lead 
developer gave at PuppetConf last month:
http://www.youtube.com/watch?v=xcc131s_Rtk

--
Peter

On Sep 5, 2013, at 10:08 AM, Ankit Mittal  wrote:

> Dear All,
> 
> Please help to find the latest version of puppet Dashboard in which i can use 
> postgre database.

-- 
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] Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48

[Cory Stoker]

Look at the apache::vhost definition.  It looks to me that "template"
is no longer a parameter to the defined type.  Since this looks like
puppetlabs-dashboard I would check out the puppetlabs-apache module to
find the apache::vhost defined type in
puppetlabs-apache/manifest/vhost.pp.  If the parameter is not declared
in the type then you will need to remove that line and figure out what
you do need to declare in passenger.pp for the apache::vhost resource.
 It looks to me like $template was a parameter in older versions of
that module (0.4.0) but is now gone in the current version.

HTH

On Wed, Sep 4, 2013 at 8:08 AM, Mr. Vitriol  wrote:
> Hi,
> I am new to the job and forum. I installed puppet and puppetmaster and set
> up my first dependencies acording to a manual that we have here in our
> company. Everything works fine and I can set up new nodes with several
> modules to choose from. Unfortunatley the Dashboard gives me errors instead
> of starting correctley.
>
> Here the message:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Invalid parameter template at
> /etc/puppet/modules/dashboard/manifests/passenger.pp:48 on node
> puppet-master.defaultdomain
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
> The relevant passage from the passenger is:
>
> # Class: dashboard::passenger
> #
> # This class configures parameters for the puppet-dashboard module.
> #
> # Parameters:
> #   [*dashboard_site*]
> # - The ServerName setting for Apache
> #
> #   [*dashboard_port*]
> # - The port on which puppet-dashboard should run
> #
> #   [*dashboard_config*]
> # - The Dashboard configuration file
> #
> #   [*dashboard_root*]
> # - The path to the Puppet Dashboard library
> #
> # Actions:
> #
> # Requires:
> #
> # Sample Usage:
> #
> class dashboard::passenger (
>   $dashboard_site,
>   $dashboard_port,
>   $dashboard_config,
>   $dashboard_root
> ) inherits dashboard {
>
>   require ::passenger
>   include apache
>
>   file { '/etc/init.d/puppet-dashboard':
> ensure => absent,
>   }
>
>   file { 'dashboard_config':
> ensure => absent,
> path   => $dashboard_config,
>   }
>
>   apache::vhost { $dashboard_site:
> port => $dashboard_port,
> priority => '50',
> docroot  => "${dashboard_root}/public",
> template => 'dashboard/passenger-vhost.erb',
>   }
> }
>
> That is the default version, since I didn't add anything.
>
> I hope someone can help me with this, google wasn't able to.
>
> 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.

-- 
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 Dashboard Error 400 Invalid Parameter at passenger pp:48

[Mr. Vitriol]

Hi,
I am new to the job and forum. I installed puppet and puppetmaster and set 
up my first dependencies acording to a manual that we have here in our 
company. Everything works fine and I can set up new nodes with several 
modules to choose from. Unfortunatley the Dashboard 
gives me errors instead 
of starting correctley. 

Here the message:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Invalid parameter template at 
/etc/puppet/modules/dashboard/manifests/passenger.pp:48 on node 
puppet-master.defaultdomain
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

The relevant passage from the passenger is:

# Class: dashboard::passenger
#
# This class configures parameters for the puppet-dashboard module.
#
# Parameters:
#   [*dashboard_site*]
# - The ServerName setting for Apache
#
#   [*dashboard_port*]
# - The port on which puppet-dashboard should run
#
#   [*dashboard_config*]
# - The Dashboard configuration file
#
#   [*dashboard_root*]
# - The path to the Puppet Dashboard library
#
# Actions:
#
# Requires:
#
# Sample Usage:
#
class dashboard::passenger (
  $dashboard_site,
  $dashboard_port,
  $dashboard_config,
  $dashboard_root
) inherits dashboard {

  require ::passenger
  include apache

  file { '/etc/init.d/puppet-dashboard':
ensure => absent,
  }

  file { 'dashboard_config':
ensure => absent,
path   => $dashboard_config,
  }

  apache::vhost { $dashboard_site:
port => $dashboard_port,
priority => '50',
docroot  => "${dashboard_root}/public",
template => 'dashboard/passenger-vhost.erb',
  }
}

That is the default version, since I didn't add anything.

I hope someone can help me with this, google wasn't able to.

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.

Re: [Puppet Users] puppet dashboard database options

[Peter Bukowinski]

Postgres is an option in Puppet Dashboard 2.0, which is due to be released 
*very soon* (according to the session I attended at Puppet Conf last week).

https://github.com/sodabrew/puppet-dashboard

--
Peter


On Aug 28, 2013, at 9:15 AM, Ankit Mittal  wrote:

> Dear All,
> 
> Please help to find other database option in puppet dashboard , other that 
> MySql.
> 
> -- 
> 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] puppet dashboard database options

[Ankit Mittal]

Dear All,

Please help to find other database option in puppet dashboard , other that 
MySql.

-- 
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] puppet dashboard failed tasks every night

[ureal frank]

On Tuesday, August 27, 2013, Felipe Salum wrote:

> I checked that, nothing that could impact this. But I'm probably missing
> something since it is every night no exception.
>
>
>
i've debugged some problems with strace -p 'pidof ruby' and lsof -p 'pidof
ruby' when applying the catalog. (timeout.rb segdault because some huge
file was not pushed in a nice interval) you can do the same and see the
logs in the morning


>
>
> On Tue, Aug 27, 2013 at 10:15 AM, Peter Bukowinski 
> 
> > wrote:
>
>> Do you have any daily cron jobs that occur overnight?
>>
>> --
>> Peter
>>
>> On Aug 27, 2013, at 1:08 PM, Felipe Salum 
>> >
>> wrote:
>>
>> Hi guys.
>>
>> I'm trying to find the root cause of my puppet dashboard report failed
>> tasks that happen every night. It works without any error all day long but
>> when I connect in the morning to check it has around 3000 failed tasks from
>> the night before.
>>
>> Any advice what could be impacting puppet dashboard reports only during
>> the night ?
>>
>> Regards,
>> Felipe
>>
>> --
>> 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 > 'cvml', 'puppet-users+unsubscr...@googlegroups.com');>.
>> To post to this group, send email to 
>> puppet-users@googlegroups.com> '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 a topic in the
>> Google Groups "Puppet Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/puppet-users/uH7XQqY1GAM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> puppet-users+unsubscr...@googlegroups.com > 'puppet-users%2bunsubscr...@googlegroups.com');>.
>> To post to this group, send email to 
>> puppet-users@googlegroups.com> '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  'cvml', 'puppet-users%2bunsubscr...@googlegroups.com');>.
> To post to this group, send email to 
> puppet-users@googlegroups.com '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] puppet dashboard failed tasks every night

[Felipe Salum]

I checked that, nothing that could impact this. But I'm probably missing
something since it is every night no exception.


On Tue, Aug 27, 2013 at 10:15 AM, Peter Bukowinski  wrote:

> Do you have any daily cron jobs that occur overnight?
>
> --
> Peter
>
> On Aug 27, 2013, at 1:08 PM, Felipe Salum  wrote:
>
> Hi guys.
>
> I'm trying to find the root cause of my puppet dashboard report failed
> tasks that happen every night. It works without any error all day long but
> when I connect in the morning to check it has around 3000 failed tasks from
> the night before.
>
> Any advice what could be impacting puppet dashboard reports only during
> the night ?
>
> Regards,
> Felipe
>
> --
> 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 a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/uH7XQqY1GAM/unsubscribe.
> To unsubscribe from this group and all its topics, 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] puppet dashboard failed tasks every night

[Peter Bukowinski]

Do you have any daily cron jobs that occur overnight?

--
Peter

On Aug 27, 2013, at 1:08 PM, Felipe Salum  wrote:

> Hi guys.
> 
> I'm trying to find the root cause of my puppet dashboard report failed tasks 
> that happen every night. It works without any error all day long but when I 
> connect in the morning to check it has around 3000 failed tasks from the 
> night before.
> 
> Any advice what could be impacting puppet dashboard reports only during the 
> night ?
> 
> Regards,
> Felipe
> 
> -- 
> 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] puppet dashboard failed tasks every night

[Felipe Salum]

Hi guys.

I'm trying to find the root cause of my puppet dashboard report failed 
tasks that happen every night. It works without any error all day long but 
when I connect in the morning to check it has around 3000 failed tasks from 
the night before.

Any advice what could be impacting puppet dashboard reports only during the 
night ?

Regards,
Felipe

-- 
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 dashboard - having cached catalog runs show up as warnings

[oogs]

Hi,

I have noticed that when a typo is introduced or a module is plain 
broken, puppet will run using a cached catalog. This is logged as an 
error on the local client, however, it is not logged as an error on 
Puppet Dashboard. How can I change this behavior, so that using the 
cached catalog will result in a warning/error being displayed on Puppet 
Dashboard? Foreman does this.



I've already looked through the documentation for Puppet Dashboard 
1.2.23 (which is what we're running) and it doesn't make mention of 
this. (See http://docs.puppetlabs.com/dashboard/manual/1.2/index.html ).


Googling this brings up an old bug that is similar - 
http://projects.puppetlabs.com/issues/5104 - and roadmapped for 1.1.0.


-Chris

--
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 dashboard certificate request fails

[espe]

Hi,
if I send the certificate request from puppet dashboard to the puppet 
master, I get the error

SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: 
certificate verify failed

The master log gives me this message:

[2013-08-02 22:28:22] ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 
errno=0 state=SSLv3 read client certificate A: tlsv1 alert unknown ca

/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/network/http/webrick.rb:34:in 
`accept'

/usr/lib64/ruby/vendor_ruby/1.9.1/puppet/network/http/webrick.rb:34:in 
`block (3 levels) in listen'
/usr/lib64/ruby/1.9.1/webrick/server.rb:191:in `call'
/usr/lib64/ruby/1.9.1/webrick/server.rb:191:in `block in 
start_thread'

The puppet setup at all works fine. A have a lot of nodes connecting 
without problems to the master. The puppet dashboard runs on the same host 
like the puppet master. The dashboards collects reports successfully, too.

It's openSuSE 12.2 with puppet 3.2.2, puppet-dashboard 1.2.23, ruby 
1.9.3p392 and rake 0.9.2.2.

Can anybody help?

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] puppet-dashboard can't read files in /var/lib/puppet/reports

[Joe VanAndel]

On CentOS 6.4, with puppet-3.2.3-1 and puppet-dashboard-1.2.23-1, installed 
from the puppetlabs repo,  I found that puppet-dashboard couldn't read the 
reports in
 /var/lib/puppet/reports (permissions drwxr-x--- puppet puppet,)  so the 
dashboard was always out of date.

My solution was to add the puppet-dashboard user to the puppet entry in 
/etc/group

-- 
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 Dashboard View Production Reports

[GregC]

I have an issue where I have one Puppet Dashboard in Development.

I am not allowed to install a dashboard in my Production environment, but I 
would like to :
* Pull reports. I currently can do this through an elaborate rsync through 
some host and then import the reports into Dashboard.
* Also grab facter information for produce inventory reports.
* Grab filebucket info so I can display changes of files, as I do in 
Development.

Has anyone had any success with an approach theat will accomplish these 
three goals? Would be interested to know how others may be dealing with 
this sort of issue, appreciate any feedback, 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] puppet-dashboard in PE3.0

[jdt]

Hello,
 
I read the PE3.0 announcement and it states the the dashboard in there uses 
PostgreSQL as backend. Will this version be released as open-source too?
Or are there other options available to use PostgresQL with 
puppet-dashboard?

Best Regards,
Jo

-- 
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] Puppet-dashboard work well but can't see any node

[Konrad Scherer]

On 13-06-17 04:04 AM, Rajat Patel wrote:

Hi Guys,

We have Cent OS 6.4 server which is puppet master server, its take all
mix environment(fedora/redhat/centos/windows).

Right now we have add 2 node one from ubuntu 12.10 and fedora 18.


If the dashboard is using ruby 1.8.x, it cannot process reports coming 
from puppet using ruby 1.9.x. I know F18 is ruby 1.9 and CentOS 6.4 is 
ruby 1.8, so that may be the problem.


http://projects.puppetlabs.com/issues/10422

Do you see the error messages in Dashboard?

--
Konrad Scherer, Sr. Engineer, Linux Products Group, Wind River
direct 613-963-1342   fax 613-592-2283

--
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 dashboard on FreeBSD 9

[Ivailo Tanusheff]

Hi,

I am trying to install puppet-dashboard on FreeBSD 9, but with no success.
The link on their site: 
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html make me 
no good and is almost useless.
Can someone provide some knowledge or how to do this? Or I have to give up 
on that?

Regasrds,
Ivailo Tanusheff

-- 
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-dashboard work well but can't see any node

[Rajat Patel]

Hi Guys,

We have Cent OS 6.4 server which is puppet master server, its take all mix 
environment(fedora/redhat/centos/windows).

Right now we have add 2 node one from ubuntu 12.10 and fedora 18.

We can deploy all policy which we want to.

To show POC to management We need config puppet-dashboard which web pages 
is coming but can see any node add to the page.

We have try adding manually which is not working out.

Kindly let us know what could be issues. 

[root@master sysconfig]# /etc/init.d/puppet-dashboard start
Starting Puppet Dashboard: config.gem: Unpacked gem rspec-rails-1.3.4 in 
vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix 
this.
config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem rack-1.1.6 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked gem json_pure-1.7.7 in vendor/gems has no 
specification file. Run 'rake gems:refresh_specs' to fix this.
=> Booting WEBrick
=> Rails 2.3.17 application starting on http://0.0.0.0:3000
   [  OK  ]

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

[Puppet Users] puppet-dashboard problem, report from node fails

[zgrega]

Hello,

I am having a problem with reports from a puppet node. After report is sent 
the following error occurs on my puppet master:

*localhost puppet-master[31237]: Report processor failed: Connection timed 
out - connect(2)*

i really don't know what is a problem.

I have the following configuration on puppetmaster (Puppet v3.2.1):

[master]
reports = store, http
reporturl = http://X:3000/reports/upload

on agent (Puppet v2.7.11)

[agent]
report=true

Dashboard GUI is running.

On agent --debug does not show anything:

notice: Finished catalog run in 93.11 seconds
debug: Executing '/etc/puppet/etckeeper-commit-post'
debug: Value of 'preferred_serialization_format' (pson) is invalid for 
report, using default (b64_zlib_yaml)
debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml

Master started with debug and verbose also:

Debug: Processing report from ucsadm.ucstech.eu with processor 
Puppet::Reports::Store
Debug: Processing report from ucsadm.ucstech.eu with processor 
Puppet::Reports::Http
Error: Report processor failed: Connection timed out - connect(2)

How can I turn more debug info?

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard Issues

[Jithin Xavier]

Hi, 

I am using Puppet enterprise free 10 node version, getting one error while 
loading this page in "/baseline/compliance" 

"
Puppet Dashboard encountered an error. 

Something went wrong, and Puppet Dashboard was unable to render the 
requested page. Please contact your site’s help desk or systems 
administrator; if that happens to be you, please check Dashboard’s logs for 
more information.
"

getting this error only here..is it because of license?

Regards,
Jithin

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard errror

[Jithin Xavier]

Hi All,

For some reason my puppet dashborad is not starting and new node requests 
are not displaying in dashboard. I am getting following error while 
restarting Puppet dashboard.

root@PuppetMaster:/etc/puppetlabs/puppet/modules# 
/etc/init.d/pe-puppet-dashboard-workers start
 * Starting PE Puppet Dashboard 
Workers 

ERROR: there is already one or more instance(s) of the program running
ERROR: there is already one or more instance(s) of the program running
 * PE Puppet Dashboard Worker (pid ) is not running

 
[fail]
root@PuppetMaster:/etc/puppetlabs/puppet/modules#

I'm using Free enterprise version Puppet, /var/log/syslog 

 "Apr 16 15:13:04 PuppetMaster puppet-master[25026]: You have 5 active and 
no inactive nodes.
Apr 16 15:13:04 PuppetMaster puppet-master[25026]: You are currently 
licensed for 10 active nodes.
Apr 16 15:13:04 PuppetMaster puppet-master[25026]:
Apr 16 15:13:04 PuppetMaster puppet-master[25026]: This Puppet Enterprise 
distribution is licensed to:
Apr 16 15:13:04 PuppetMaster puppet-master[25026]: N/A#012#012You 
are using a complimentary ten node license provided free by Puppet Labs.
Apr 16 15:13:04 PuppetMaster puppet-master[25026]:
"

Please advise me to solve this issues.

Thanks,
Jithin

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard 1.2.23 issue deleting node

[Stefan Heijmans]

Hello,

we run Puppet Dashboard 1.2.23 in our sandbox and get an error deleting a 
node.
- first time we press the delete button nothing happens 
- second time we press the delete button we get the following error;

ActiveRecord::StatementInvalid in NodesController#destroy

Mysql::Error: Lock wait timeout exceeded; try restarting transaction: 
DELETE FROM `node_group_memberships` WHERE `id` = 53

RAILS_ROOT: /usr/share/puppet-dashboard
Application Trace | Framework Trace | Full Trace

Request

Parameters:

{"authenticity_token"=>"2LTYvT15OF9RXNjMXiDdVEGiXyCebbL3DNFgaamHMdk=",
 "id"=>"32",
 "_method"=>"delete"}

Show session dump
Response

Headers:

{"Cache-Control"=>"no-cache",
 "Content-Type"=>""}
After downgrading to 1.2.22, we can delete the node again.
Anyone else experience this?
 

Stefan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet dashboard enc default group

[vioilly]

Hi,

Is there such a thing in puppet dashboard as a default group that new nodes 
automatically get adding to, similar to the site.pp default classification?

-oli

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet dashboard stopped updating

[Gregory Damiani]

I was in the process of setting up puppet environments.  I pulled code from 
my main modules and manifests directories into the prod environment folder, 
deployed a newer branch of that code to a 'stg' environment folder, updated 
puppet.conf on the master, and reconfigured puppet.conf on my agents to use 
the new environments.  All looked fine until I checked puppet dashboard a 
while later and noticed all my hosts were coming up as Unresponsive.  I 
confirmed on the agents that they can still compile catalogs and create 
changes.  But no new reports are coming into the puppet master.

I checked the logs and see the following error:

Report processor failed: undefined method `+' for nil:NilClass

I'm using a trial version of puppet enterprise 2.6

Any help is 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard changed reports view error

[DjE]

Hello Puppet Users !

We encounter a problem with the dashboard on this URI : /reports/changed
The /reports works fine with ~13 reports (up to 3 months and 
auto-cleaning with rake reports:prune job)


I make a reports:prune:orphaned, juste in case, but without any success. 
The most recent change on the server was the puppetmaster upgrade from 
3.0.2 to 3.1.0.


Here is the dashboard error log :

>>>

Processing ReportsController#changed (for 10.0.8.58 at 2013-03-06 
18:04:27) [GET]

  Parameters: {"action"=>"changed", "controller"=>"reports"}
Rendering template within layouts/application
Rendering reports/index

ActionView::TemplateError (node_url failed to generate from 
{:controller=>"nodes", :action=>"show"} - you may have ambiguous routes, 
or you may need to supply additional parameters for this route.  
content_url has the following required parameters: ["nodes", :id] - are 
they all satisfied?) on line #35 of 
app/views/reports/_reports_table.html.haml:

32:   %td= link_to h(report.time), report
33:   - unless node
34: %td= link_to_if report.node, h(report.host), 
node_path(report.node)

35:   %td= report.total_resources.to_i
36:   %td= report.failed_resources.to_i
37:   %td= report.changed_resources.to_i
38:   %td= report.unchanged_resources.to_i

(eval):17:in `node_path'
app/views/reports/_reports_table.html.haml:35:in 
`_run_haml_app47views47reports47_reports_table46html46haml_locals_node_object_reports_reports_table'

app/views/reports/_reports_table.html.haml:31:in `each'
app/views/reports/_reports_table.html.haml:31:in 
`_run_haml_app47views47reports47_reports_table46html46haml_locals_node_object_reports_reports_table'
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:11:in 
`render'

haml (3.1.2) [v] lib/haml/helpers.rb:90:in `non_haml'
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:11:in 
`render'
app/views/reports/index.html.haml:22:in 
`_run_haml_app47views47reports47index46html46haml'
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:13:in 
`render'
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:13:in 
`render'

app/controllers/reports_controller.rb:25:in `changed'
sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:in `call'
passenger (3.0.19) 
lib/phusion_passenger/rack/request_handler.rb:96:in `process_request'
passenger (3.0.19) 
lib/phusion_passenger/abstract_request_handler.rb:516:in 
`accept_and_process_next_request'
passenger (3.0.19) 
lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop'
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:321:in 
`start_request_handler'
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `send'
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:275:in 
`handle_spawn_application'

passenger (3.0.19) lib/phusion_passenger/utils.rb:470:in `safe_fork'
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:270:in 
`handle_spawn_application'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`__send__'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`server_main_loop'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:206:in 
`start_synchronously'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:180:in 
`start'
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:149:in `start'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:219:in 
`spawn_rails_application'
passenger (3.0.19) 
lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:214:in 
`spawn_rails_application'
passenger (3.0.19) 
lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize'
passenger (3.0.19) 
lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:213:in 
`spawn_rails_application'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:132:in 
`spawn_application'
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:275:in 
`handle_spawn_application'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`__send__'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`server_main_loop'
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:206:in 
`start_synchronously'

passenger (3.0.19) helper-scripts/passenger-spawn-server:99

Rendering /usr/share/puppet-dashboard/public/500.html (500 Internal 
Server Error)


>>>

Ins

[Puppet Users] Puppet Dashboard changed reports view error

[DjE]

Hello Puppet Users ! 

We encounter a problem with the dashboard on this URI : /reports/changed 
The /reports works fine with ~13 reports (up to 3 months and 
auto-cleaning with rake reports:prune job) 

I make a reports:prune:orphaned, juste in case, but without any success. 
The most recent change on the server was the puppetmaster upgrade from 
3.0.2 to 3.1.0. 

Here is the dashboard error log : 

>>> >>>
>>>  


Processing ReportsController#changed (for 10.0.8.58 at 2013-03-06 18:04:27) 
[GET] 
  Parameters: {"action"=>"changed", "controller"=>"reports"} 
Rendering template within layouts/application 
Rendering reports/index 

ActionView::TemplateError (node_url failed to generate from 
{:controller=>"nodes", :action=>"show"} - you may have ambiguous routes, or 
you may need to supply additional parameters for this route.  content_url 
has the following required parameters: ["nodes", :id] - are they all 
satisfied?) on line #35 of app/views/reports/_reports_table.html.haml: 
32:   %td= link_to h(report.time), report 
33:   - unless node 
34: %td= link_to_if report.node, h(report.host), 
node_path(report.node) 
35:   %td= report.total_resources.to_i 
36:   %td= report.failed_resources.to_i 
37:   %td= report.changed_resources.to_i 
38:   %td= report.unchanged_resources.to_i 

(eval):17:in `node_path' 
app/views/reports/_reports_table.html.haml:35:in 
`_run_haml_app47views47reports47_reports_table46html46haml_locals_node_object_reports_reports_table'
 

app/views/reports/_reports_table.html.haml:31:in `each' 
app/views/reports/_reports_table.html.haml:31:in 
`_run_haml_app47views47reports47_reports_table46html46haml_locals_node_object_reports_reports_table'
 

haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:11:in 
`render' 
haml (3.1.2) [v] lib/haml/helpers.rb:90:in `non_haml' 
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:11:in 
`render' 
app/views/reports/index.html.haml:22:in 
`_run_haml_app47views47reports47index46html46haml' 
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:13:in 
`render' 
haml (3.1.2) [v] rails/./lib/haml/helpers/action_view_mods.rb:13:in 
`render' 
app/controllers/reports_controller.rb:25:in `changed' 
sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:in `call' 
passenger (3.0.19) lib/phusion_passenger/rack/request_handler.rb:96:in 
`process_request' 
passenger (3.0.19) 
lib/phusion_passenger/abstract_request_handler.rb:516:in 
`accept_and_process_next_request' 
passenger (3.0.19) 
lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop' 
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:321:in 
`start_request_handler' 
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `send' 
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:275:in 
`handle_spawn_application' 
passenger (3.0.19) lib/phusion_passenger/utils.rb:470:in `safe_fork' 
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:270:in 
`handle_spawn_application' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`__send__' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`server_main_loop' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:206:in 
`start_synchronously' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:180:in 
`start' 
passenger (3.0.19) 
lib/phusion_passenger/classic_rails/application_spawner.rb:149:in `start' 
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:219:in 
`spawn_rails_application' 
passenger (3.0.19) 
lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' 
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:214:in 
`spawn_rails_application' 
passenger (3.0.19) 
lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize' 
passenger (3.0.19) 
lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' 
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:213:in 
`spawn_rails_application' 
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:132:in 
`spawn_application' 
passenger (3.0.19) lib/phusion_passenger/spawn_manager.rb:275:in 
`handle_spawn_application' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`__send__' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:357:in 
`server_main_loop' 
passenger (3.0.19) lib/phusion_passenger/abstract_server.rb:206:in 
`start_synchronously' 
passen

Re: [Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Ti Leggett]

The issue is that on RHEL/CentOS 6, the mod_passenger RPM requires the 
rubygems-rack RPM which is at 1.2.5. The Puppet Dashboard RPM requires 
explicitly rack version 1.1.0 - from 
vendor/rails/actionpack/lib/action_controller.rb:

gem 'rack', '~> 1.1.0'
require 'rack'
require 'action_controller/cgi_ext'

If you comment out:

#gem 'rack', '~> 1.1.0'

Things work fine. So why is dashboard explicitly requiring this version? I'm 
not sure my 'fix' is the proper way to do things, but it at least makes things 
work again.

On Feb 26, 2013, at 12:16 PM, Ramin K  wrote:

> ~> 1.1.0 matches 1.1.x
> 
> Dashboard 1.2.22 is responding to these CVEs from http://rack.github.com/ and 
> 1.1.6 is the one that has the fix.
> 
> Ramin
> 

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Ramin K]

~> 1.1.0 matches 1.1.x

Dashboard 1.2.22 is responding to these CVEs from 
http://rack.github.com/ and 1.1.6 is the one that has the fix.


Ramin

On 2/26/2013 9:55 AM, Tom Blich wrote:

Well, based on the error, wouldn't I need to install rack 1.1.0? I
don't understand ruby all that well yet.

My confusion is why 1.2.21 is working just fine, but 1.2.22 is not.


On Tuesday, February 26, 2013 9:47:17 AM UTC-8, Ramin K wrote:

I'm guessing you're installing gems since everything looks very up to
date. Try the following.

sudo gem install rack --version 1.1.6

Then restart Apache. If you still have problems you can try removing
all
versions of Rack that are not 1.1.6, assuming that Puppet and Puppet
dashboard are the only Rack applications on this machine. I'd test this
in a maintenance window just in case.

Ramin

On 2/26/2013 9:39 AM, Tom Blich wrote:
 > Do you know where I might be able to change where it's looking
for the
 > specific rack version for 1.1.0?
 >
 > Thanks,
 > Tom
 >
 >
 > On Friday, February 22, 2013 5:29:59 PM UTC-8, Matt wrote:
 >
 > It looks like its trying to use a specific rack gem version
but you do
 > not have that version installed or you have two versions
installed and
 > its picking up the latest. It could be that you also have
another
 > passenger application where the versions conflict?
 >
 > (can't activate rack (~> 1.1.0, runtime) for [], already
activated
 > rack-1.5.2 for []) (process 8729, thread
#):
 >
 > On Fri, Feb 22, 2013 at 7:17 PM, Tom Blich  > wrote:
 >  > Had puppet-dashboard-1.2.21 running via instructions
provided here:
 >  >
 >  > http://docs.puppetlabs.com/dashboard/passenger.html

 > >
 >  >
 >  > Upgraded to puppet-dashboard-1.2.22 and now get the
following error:
 >  >
 >  >   [ pid=8729 thr=70328297972140 file=utils.rb:176
time=2013-02-22
 >  > 19:12:17.188 ]: *** Exception RuntimeError in
 >  > PhusionPassenger::Rack::ApplicationSpawner (can't activate
rack
 > (~> 1.1.0,
 >  > runtime) for [], already activated rack-1.5.2 for [])
(process
 > 8729, thread
 >  > #):
 >  > from
./config/../vendor/rails/railties/lib/initializer.rb:271:in
 >  > `require_frameworks'
 >  > from
./config/../vendor/rails/railties/lib/initializer.rb:134:in
 > `process'
 >  > from
./config/../vendor/rails/railties/lib/initializer.rb:113:in
 > `send'
 >  > from
./config/../vendor/rails/railties/lib/initializer.rb:113:in
 > `run'
 >  > from ./config/environment.rb:14
 >  > from
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
 >  > `gem_original_require'
 >  > from
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
 > `require'
 >  > from config.ru:4  
 >  > from
 > /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in
 >  > `instance_eval'
 >  > from
 > /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in
 >  > `initialize'
 >  > from config.ru:1:in `new'
 >  > from config.ru:1  
 >  > [Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM,
shutting down
 >  > [Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not
 > configured
 >  > [hint: SSLSessionCache]
 >  > [Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled
 > (wrapper:
 >  > /usr/sbin/suexec)
 >  > [Fri Feb 22 19:13:37 2013] [warn] module php5_module is
already
 > loaded,
 >  > skipping
 >  > [Fri Feb 22 19:13:37 2013] [notice] Digest: generating
secret for
 > digest
 >  > authentication ...
 >  > [Fri Feb 22 19:13:37 2013] [notice] Digest: done
 >  > [Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix)
DAV/2
 >  > Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15
 > OpenSSL/1.0.0-fips
 >  > configured -- resuming normal operations
 >  >
 >  > Not sure how to fix it.
 >  >
 >  > Thanks,
 >  > Tom
 >  >
 >  > --
 >  > 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...@googlegroups.com .
 >  > T

Re: [Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Tom Blich]

Well, based on the error, wouldn't I need to install rack 1.1.0? I 
don't understand ruby all that well yet.   

My confusion is why 1.2.21 is working just fine, but 1.2.22 is not.


On Tuesday, February 26, 2013 9:47:17 AM UTC-8, Ramin K wrote:
>
> I'm guessing you're installing gems since everything looks very up to 
> date. Try the following. 
>
> sudo gem install rack --version 1.1.6 
>
> Then restart Apache. If you still have problems you can try removing all 
> versions of Rack that are not 1.1.6, assuming that Puppet and Puppet 
> dashboard are the only Rack applications on this machine. I'd test this 
> in a maintenance window just in case. 
>
> Ramin 
>
> On 2/26/2013 9:39 AM, Tom Blich wrote: 
> > Do you know where I might be able to change where it's looking for the 
> > specific rack version for 1.1.0? 
> > 
> > Thanks, 
> > Tom 
> > 
> > 
> > On Friday, February 22, 2013 5:29:59 PM UTC-8, Matt wrote: 
> > 
> > It looks like its trying to use a specific rack gem version but you 
> do 
> > not have that version installed or you have two versions installed 
> and 
> > its picking up the latest. It could be that you also have another 
> > passenger application where the versions conflict? 
> > 
> > (can't activate rack (~> 1.1.0, runtime) for [], already activated 
> > rack-1.5.2 for []) (process 8729, thread #): 
> > 
> > On Fri, Feb 22, 2013 at 7:17 PM, Tom Blich  > > wrote: 
> >  > Had puppet-dashboard-1.2.21 running via instructions provided 
> here: 
> >  > 
> >  > http://docs.puppetlabs.com/dashboard/passenger.html 
> >  
> >  > 
> >  > Upgraded to puppet-dashboard-1.2.22 and now get the following 
> error: 
> >  > 
> >  >   [ pid=8729 thr=70328297972140 file=utils.rb:176 time=2013-02-22 
> >  > 19:12:17.188 ]: *** Exception RuntimeError in 
> >  > PhusionPassenger::Rack::ApplicationSpawner (can't activate rack 
> > (~> 1.1.0, 
> >  > runtime) for [], already activated rack-1.5.2 for []) (process 
> > 8729, thread 
> >  > #): 
> >  > from ./config/../vendor/rails/railties/lib/initializer.rb:271:in 
> >  > `require_frameworks' 
> >  > from ./config/../vendor/rails/railties/lib/initializer.rb:134:in 
> > `process' 
> >  > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in 
> > `send' 
> >  > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in 
> > `run' 
> >  > from ./config/environment.rb:14 
> >  > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
> >  > `gem_original_require' 
> >  > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
> > `require' 
> >  > from config.ru:4  
> >  > from 
> > /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
> >  > `instance_eval' 
> >  > from 
> > /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
> >  > `initialize' 
> >  > from config.ru:1:in `new' 
> >  > from config.ru:1  
> >  > [Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM, shutting down 
> >  > [Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not 
> > configured 
> >  > [hint: SSLSessionCache] 
> >  > [Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled 
> > (wrapper: 
> >  > /usr/sbin/suexec) 
> >  > [Fri Feb 22 19:13:37 2013] [warn] module php5_module is already 
> > loaded, 
> >  > skipping 
> >  > [Fri Feb 22 19:13:37 2013] [notice] Digest: generating secret for 
> > digest 
> >  > authentication ... 
> >  > [Fri Feb 22 19:13:37 2013] [notice] Digest: done 
> >  > [Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix) DAV/2 
> >  > Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15 
> > OpenSSL/1.0.0-fips 
> >  > configured -- resuming normal operations 
> >  > 
> >  > Not sure how to fix it. 
> >  > 
> >  > Thanks, 
> >  > Tom 
> >  > 
> >  > -- 
> >  > 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...@googlegroups.com . 
> >  > To post to this group, send email to puppet...@googlegroups.com 
> > . 
> >  > Visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en 
> > . 
> >  > 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 pupp

Re: [Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Ramin K]

I'm guessing you're installing gems since everything looks very up to 
date. Try the following.


sudo gem install rack --version 1.1.6

Then restart Apache. If you still have problems you can try removing all 
versions of Rack that are not 1.1.6, assuming that Puppet and Puppet 
dashboard are the only Rack applications on this machine. I'd test this 
in a maintenance window just in case.


Ramin

On 2/26/2013 9:39 AM, Tom Blich wrote:

Do you know where I might be able to change where it's looking for the
specific rack version for 1.1.0?

Thanks,
Tom


On Friday, February 22, 2013 5:29:59 PM UTC-8, Matt wrote:

It looks like its trying to use a specific rack gem version but you do
not have that version installed or you have two versions installed and
its picking up the latest. It could be that you also have another
passenger application where the versions conflict?

(can't activate rack (~> 1.1.0, runtime) for [], already activated
rack-1.5.2 for []) (process 8729, thread #):

On Fri, Feb 22, 2013 at 7:17 PM, Tom Blich > wrote:
 > Had puppet-dashboard-1.2.21 running via instructions provided here:
 >
 > http://docs.puppetlabs.com/dashboard/passenger.html

 >
 > Upgraded to puppet-dashboard-1.2.22 and now get the following error:
 >
 >   [ pid=8729 thr=70328297972140 file=utils.rb:176 time=2013-02-22
 > 19:12:17.188 ]: *** Exception RuntimeError in
 > PhusionPassenger::Rack::ApplicationSpawner (can't activate rack
(~> 1.1.0,
 > runtime) for [], already activated rack-1.5.2 for []) (process
8729, thread
 > #):
 > from ./config/../vendor/rails/railties/lib/initializer.rb:271:in
 > `require_frameworks'
 > from ./config/../vendor/rails/railties/lib/initializer.rb:134:in
`process'
 > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in
`send'
 > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in
`run'
 > from ./config/environment.rb:14
 > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
 > `gem_original_require'
 > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
 > from config.ru:4 
 > from
/usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in
 > `instance_eval'
 > from
/usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in
 > `initialize'
 > from config.ru:1:in `new'
 > from config.ru:1 
 > [Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM, shutting down
 > [Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not
configured
 > [hint: SSLSessionCache]
 > [Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled
(wrapper:
 > /usr/sbin/suexec)
 > [Fri Feb 22 19:13:37 2013] [warn] module php5_module is already
loaded,
 > skipping
 > [Fri Feb 22 19:13:37 2013] [notice] Digest: generating secret for
digest
 > authentication ...
 > [Fri Feb 22 19:13:37 2013] [notice] Digest: done
 > [Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix) DAV/2
 > Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15
OpenSSL/1.0.0-fips
 > configured -- resuming normal operations
 >
 > Not sure how to fix it.
 >
 > Thanks,
 > Tom
 >
 > --
 > 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...@googlegroups.com .
 > To post to this group, send email to puppet...@googlegroups.com
.
 > Visit this group at
http://groups.google.com/group/puppet-users?hl=en
.
 > 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?hl=en.
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Tom Blich]

Do you know where I might be able to change where it's looking for the 
specific rack version for 1.1.0?

Thanks,
Tom


On Friday, February 22, 2013 5:29:59 PM UTC-8, Matt wrote:
>
> It looks like its trying to use a specific rack gem version but you do 
> not have that version installed or you have two versions installed and 
> its picking up the latest. It could be that you also have another 
> passenger application where the versions conflict? 
>
> (can't activate rack (~> 1.1.0, runtime) for [], already activated 
> rack-1.5.2 for []) (process 8729, thread #): 
>
> On Fri, Feb 22, 2013 at 7:17 PM, Tom Blich > 
> wrote: 
> > Had puppet-dashboard-1.2.21 running via instructions provided here: 
> > 
> > http://docs.puppetlabs.com/dashboard/passenger.html 
> > 
> > Upgraded to puppet-dashboard-1.2.22 and now get the following error: 
> > 
> >   [ pid=8729 thr=70328297972140 file=utils.rb:176 time=2013-02-22 
> > 19:12:17.188 ]: *** Exception RuntimeError in 
> > PhusionPassenger::Rack::ApplicationSpawner (can't activate rack (~> 
> 1.1.0, 
> > runtime) for [], already activated rack-1.5.2 for []) (process 8729, 
> thread 
> > #): 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:271:in 
> > `require_frameworks' 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:134:in 
> `process' 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `send' 
> > from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `run' 
> > from ./config/environment.rb:14 
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
> > `gem_original_require' 
> > from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
> `require' 
> > from config.ru:4 
> > from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
> > `instance_eval' 
> > from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
> > `initialize' 
> > from config.ru:1:in `new' 
> > from config.ru:1 
> > [Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM, shutting down 
> > [Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not configured 
> > [hint: SSLSessionCache] 
> > [Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled (wrapper: 
> > /usr/sbin/suexec) 
> > [Fri Feb 22 19:13:37 2013] [warn] module php5_module is already loaded, 
> > skipping 
> > [Fri Feb 22 19:13:37 2013] [notice] Digest: generating secret for digest 
> > authentication ... 
> > [Fri Feb 22 19:13:37 2013] [notice] Digest: done 
> > [Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix) DAV/2 
> > Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15 OpenSSL/1.0.0-fips 
> > configured -- resuming normal operations 
> > 
> > Not sure how to fix it. 
> > 
> > Thanks, 
> > Tom 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To post to this group, send email to 
> > puppet...@googlegroups.com. 
>
> > Visit this group at http://groups.google.com/group/puppet-users?hl=en. 
> > 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Matthew Black]

It looks like its trying to use a specific rack gem version but you do
not have that version installed or you have two versions installed and
its picking up the latest. It could be that you also have another
passenger application where the versions conflict?

(can't activate rack (~> 1.1.0, runtime) for [], already activated
rack-1.5.2 for []) (process 8729, thread #):

On Fri, Feb 22, 2013 at 7:17 PM, Tom Blich  wrote:
> Had puppet-dashboard-1.2.21 running via instructions provided here:
>
> http://docs.puppetlabs.com/dashboard/passenger.html
>
> Upgraded to puppet-dashboard-1.2.22 and now get the following error:
>
>   [ pid=8729 thr=70328297972140 file=utils.rb:176 time=2013-02-22
> 19:12:17.188 ]: *** Exception RuntimeError in
> PhusionPassenger::Rack::ApplicationSpawner (can't activate rack (~> 1.1.0,
> runtime) for [], already activated rack-1.5.2 for []) (process 8729, thread
> #):
> from ./config/../vendor/rails/railties/lib/initializer.rb:271:in
> `require_frameworks'
> from ./config/../vendor/rails/railties/lib/initializer.rb:134:in `process'
> from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
> from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
> from ./config/environment.rb:14
> from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
> from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
> from config.ru:4
> from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in
> `instance_eval'
> from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in
> `initialize'
> from config.ru:1:in `new'
> from config.ru:1
> [Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM, shutting down
> [Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not configured
> [hint: SSLSessionCache]
> [Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled (wrapper:
> /usr/sbin/suexec)
> [Fri Feb 22 19:13:37 2013] [warn] module php5_module is already loaded,
> skipping
> [Fri Feb 22 19:13:37 2013] [notice] Digest: generating secret for digest
> authentication ...
> [Fri Feb 22 19:13:37 2013] [notice] Digest: done
> [Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix) DAV/2
> Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15 OpenSSL/1.0.0-fips
> configured -- resuming normal operations
>
> Not sure how to fix it.
>
> Thanks,
> Tom
>
> --
> 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?hl=en.
> 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet-dashboard-1.2.22 - unable to get it running under Apache/Passenger

[Tom Blich]

Had puppet-dashboard-1.2.21 running via instructions provided here:

http://docs.puppetlabs.com/dashboard/passenger.html

Upgraded to puppet-dashboard-1.2.22 and now get the following error: 

  [ pid=8729 thr=70328297972140 file=utils.rb:176 time=2013-02-22 
19:12:17.188 ]: *** Exception RuntimeError in 
PhusionPassenger::Rack::ApplicationSpawner (can't activate rack (~> 1.1.0, 
runtime) for [], already activated rack-1.5.2 for []) (process 8729, thread 
#):
from ./config/../vendor/rails/railties/lib/initializer.rb:271:in 
`require_frameworks'
from ./config/../vendor/rails/railties/lib/initializer.rb:134:in `process'
from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
from ./config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
from ./config/environment.rb:14
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
`gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from config.ru:4
from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
`instance_eval'
from /usr/lib/ruby/gems/1.8/gems/rack-1.5.2/lib/rack/builder.rb:55:in 
`initialize'
from config.ru:1:in `new'
from config.ru:1
[Fri Feb 22 19:12:46 2013] [notice] caught SIGTERM, shutting down
[Fri Feb 22 19:13:37 2013] [warn] Init: Session Cache is not configured 
[hint: SSLSessionCache]
[Fri Feb 22 19:13:37 2013] [notice] suEXEC mechanism enabled (wrapper: 
/usr/sbin/suexec)
[Fri Feb 22 19:13:37 2013] [warn] module php5_module is already loaded, 
skipping
[Fri Feb 22 19:13:37 2013] [notice] Digest: generating secret for digest 
authentication ...
[Fri Feb 22 19:13:37 2013] [notice] Digest: done
[Fri Feb 22 19:13:37 2013] [notice] Apache/2.2.15 (Unix) DAV/2 
Phusion_Passenger/3.0.19 PHP/5.3.20 mod_ssl/2.2.15 OpenSSL/1.0.0-fips 
configured -- resuming normal operations

Not sure how to fix it. 

Thanks,
Tom

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet-dashboard(open source)

[Mamta Garg]

Hi ,

I am working with puppet open source.I have setup puppet dashboard.
But its is not showing any agent node there.Anyone guide me for the same?

-- 
Thanks and Regards,
Mamta Garg

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet dashboard(open source)

[Mamta Garg]

I am setting up puppet opensource ,I am not able to lauch puppet dashboard.
Can anyone please tell me if puppet opensource dashbord setting is same as
in puppet dashboard or i need to do some different setting for this?

-- 
Thanks and Regards,
Mamta Garg

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard stuck pending jobs

[Felipe Salum]

Are you having the problem after running 'puppet agent --test' a few times 
or it just happens without any manual run ?

I was having the same problem some days ago, in my case because I was 
running 'puppet agent --test', more specifically the --show_diff that is 
used in --test was automatically generating a lot of output and causing the 
puppet dashboard workers to fail and increase the processing queue.

Look at /usr/share/puppet-dashboard/log/delayed_job.log (or whatever your 
dashboard location is) and check what error it is giving.

You can clean the queue manually without reinstalling everything:

service puppet-dashboard-workers stop
cd /usr/share/puppet-dashboard
rm -f spool/*
rake jobs:clear RAILS_ENV=production
service puppet-dashboard-workers start

Regards,
Felipe

On Saturday, February 9, 2013 7:11:04 PM UTC-8, Jagga Soorma wrote:
>
> Anyone out there run into this issue before or have any idea about how to 
> troubleshoot such a problem?  Any help would be appreciated.  I can't keep 
> rebuilding puppet dashboard every time this happens.
>
> Thanks
>
> On Friday, February 8, 2013 2:37:55 PM UTC-8, Jagga Soorma wrote:
>>
>> Yes, the workers are definitely running and I have tried restarting 
>> puppet-dashboard-workers a few times as well as rebooting the vm completely 
>> without any luck.  Something seems to be stuck somewhere but I can't figure 
>> out what.  This has happened a few times now and I have just been 
>> recreating from scratch to get it functional again.  Are there any logs for 
>> the workers that might tell us why these pending jobs are stuck or not 
>> finishing?
>>
>> Thanks.
>>
>> On Fri, Feb 8, 2013 at 2:27 PM, Jo Rhett 
>> 
>> > wrote:
>>
>>> Make sure that your dashboard workers are running. If you are using 
>>> CentOS then "service puppet-dashboard-workers status" will tell you.
>>>
>>> On Feb 8, 2013, at 1:53 PM, Jagga Soorma wrote:
>>>
>>> I am a new puppet user and wanted some type of monitoring for puppet so 
>>> deployed puppet-dashboard.  It has been working very well for a few days 
>>> not, but all of a sudden I start getting pending tasks and they never 
>>> finish even after restarting all processes.  They keep accumulating and 
>>> never seem to finish even though the clients are running fine.  I have the 
>>> puppet-dashboard running on a different server than my puppetmaster.  Is 
>>> there any way to troubleshoot what seems to be stuck and how to I get it 
>>> going without having to destroy the dashboard mysql db and recreating it 
>>> again?  That is the only way I have got it working again but that is not 
>>> the correct way of doing this :)  Any help would be appreciated.
>>>
>>> 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...@googlegroups.com .
>>> To post to this group, send email to puppet...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>>
>>>  -- 
>>> Jo Rhett
>>> Net Consonance : net philanthropy to improve open source and internet 
>>> projects.
>>>
>>>
>>>  
>>>  -- 
>>> 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...@googlegroups.com .
>>> To post to this group, send email to puppet...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.