[Puppet Users] execution expired with a puppetmaster with more then enough resources

2014-11-01 Thread Philipp Dallig
Hi,
Nodes with a filled catalog runs from time to time in: Could not retrieve 
catalog from remote server: execution expired
In my opinion i have a strong puppetmaster.
Some Facts:
max memory: 4 GB RAM (in average more then 2 GB free)
load average: 0,14
4 vCPU
visualization with lxc
OS: CentOS7
HostOS: CentOS 7
Puppetmaster Version: 3.7
Puppet Agents Version: 3.4+
Passenger-Version: 4.0.50
PuppetDB in the same Container

I have Foreman as an ENC, Foreman runs on the same Host in an other LXC 
Container.

Postgres 9.1 for Foreman und PuppetDB is on an other Host.

At the moment i have no more ideas, how i can solve this problem.

Maybe a passenger-memory-stats report help for a solution



-- Apache processes --
PIDPPID  VMSize Private  Name
--
1571   1 126.6 MB   4.1 MB   /usr/sbin/httpd -f 
/www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start
15954  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
/www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start
15955  1571  2006.7 MB  6.9 MB   /usr/sbin/httpd -f 
/www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start
15957  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
/www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start
15959  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
/www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start
15966  1571  2006.7 MB  6.8 MB   /usr/sbin/httpd -f 
/www/conf/httpd/puppetmaster.mycompany.com/httpd.conf -k start
### Processes: 6
### Total private dirty RSS: 38.18 MB


 Nginx processes 

### Processes: 0
### Total private dirty RSS: 0.00 MB


- Passenger processes -
PIDVMSizePrivate  Name
---
15936  212.2 MB  0.3 MB   PassengerWatchdog
15939  879.7 MB  1.0 MB   PassengerHelperAgent
15945  215.4 MB  0.9 MB   PassengerLoggingAgent
16119  465.8 MB  79.8 MB  Passenger RackApp: 
/www/sites/puppetmaster.mycompany.com/puppetmasterd
16126  465.9 MB  78.4 MB  Passenger RackApp: 
/www/sites/puppetmaster.mycompany.com/puppetmasterd
16135  466.0 MB  82.9 MB  Passenger RackApp: 
/www/sites/puppetmaster.mycompany.com/puppetmasterd
16144  530.9 MB  96.9 MB  Passenger RackApp: 
/www/sites/puppetmaster.mycompany.com/puppetmasterd
### Processes: 7
### Total private dirty RSS: 340.24 MB



If someone need more informations, let me know.


-- 
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/9748f970-59fd-4621-8944-84bae189072d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Exported resources from multiple sources?

2014-11-01 Thread Nick Cammorato
You'd have to mine the database and reconstruct the exported resource
as a resource, but it would be doable.  I was assuming strict
adherance to what an exported resource is wasn't really what Atom was
after.

--Nick

On Fri, Oct 31, 2014 at 9:28 AM, jcbollinger  wrote:
>
>
> On Thursday, October 30, 2014 12:00:21 PM UTC-5, Nick Cammorato wrote:
>>
>> I don't see why you couldn't write a hiera backend to do exactly this.
>> The current puppetdb hiera backend wouldn't be too hard to modify to
>> do it I don't think.
>>
>
> You couldn't write an Hiera back end to do this particular thing because
> Hiera is not involved in collecting exported resources.  You could write a
> DB-based Hiera backend that bridges networks, but it wouldn't be useful for
> exported resources.
>
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/dfb3ff9a-0f2b-421a-900e-e9c27cb88efa%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/CAKJ8aweAeTOu%2BCwF0GHy9abJ5zRfDhFniKGNRSDTLqYtuizhrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Managing folder trees - best practice?

2014-11-01 Thread JonY
Situation: systems come from imaging  with /var/tree full of (a hierarchy 
of) stuff that needs to be removed and replaced. I have a 'file/force => 
true/recurse => true' resource setup to accomplish this.. short and to the 
point...works great..replaces the folder hierarchy with a new one. 

Along comes an eager dev who says "I want to split this tree into two types 
- the difference between these being ~5% of the files." 

My choices for managing this tree seem to boil down to:

1. Berate the dev. Not v satisfying - like yelling at a puppy.
2. Maintain two (nearly identical - but not quite) file trees. It's all in 
git so maybe this isn't so bad. Looks messy though. Means having to sync 
nested trees and keep them straight.
3. Change the tree structure of what's being copied in and don't recurse. 
Name every sub folder in the 'file' resource according to which node get 
what. Neater than #2 but lots of extra work.
4. Create a 'merge' solution so I keep the current folder structure and 
only merge in the changes for the impacted nodes.

#1 - lots of unhappiness
#2 - seems prone to error
#3 - extra work. probably what will happen though.
#4 - seems like the most obvious but (AFAIK) it's not supported by puppet.

Is there something better? Another choice I've neglected?

-- 
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/46b4827d-7492-4441-b009-beb7612e5142%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.