FAQ
Hi I am encountering this problem now, can you help me, how to set "the
default value for module network".
Is it add a new [network] with path referencing the root of network module
in fileserver.conf?
On Thursday, March 29, 2012 6:27:23 PM UTC+8, A_SAAS wrote:

Hi everyone,

I found my error, the default value for my module network was not set for
the new OS (Centos) so my resource file was not correct.
Sorry for the convenient




On Wed, Mar 28, 2012 at 7:37 PM, Antidot SAS <antid...@gmail.com<javascript:>
wrote:
Hi everyone,

I have a puppet master/client infrastructure setup with apache. When on
the same datacenter I don't have any problem.

I am trying to use another datacenter, so I setup the fileserver.conf as
followed:
# Files in the /path/to/files directory will be served
# at puppet:///mount_point/.

[modules]
allow *.datacenter1
allow *.datacenter2

[plugins]
allow *.datacenter1
allow *.datacenter2


The fqdn of the server is:
[root@template]# facter fqdn
template.datacenter2

The client is registered on the server:
[root@puppetmaster]:/etc/puppet # puppet cert list --all | grep tem
+ template.datacenter2
(49:33:8A:66:D5:CA:B4:A8:F3:EE:8C:6D:0D:09:0E:FB)


But when I trying to run puppet here is the error:

[root@template puppet]# puppet agent -t --debug --trace
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/private_keys/template.datacenter2.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/public_keys/template.datacenter2.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/ssl/certs/template.datacenter.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring
File[/var/lib/puppet/ssl]
debug: Finishing transaction 23702911873500
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/ssl/certs/template.datacenter2.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/private_keys/template.datacenter2.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/public_keys/template.datacenter2.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring
File[/var/lib/puppet/ssl]
debug: Finishing transaction 23702910393880
debug: Using cached certificate for ca
debug: Using cached certificate for template.datacenter2
debug: Finishing transaction 23702909931920
info: Retrieving plugin
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: Using cached certificate for ca
debug: Using cached certificate for template.datacenter2
debug: Using cached certificate_revocation_list for ca
debug: Finishing transaction 23702909767560
info: Loading facts in puppet_vardir
info: Loading facts in meminbytes
info: Loading facts in facter_dot_d
info: Loading facts in root_home
info: Loading facts in puppet_vardir
info: Loading facts in meminbytes
info: Loading facts in facter_dot_d
info: Loading facts in root_home
debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml;
using pson
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:56:in `deserialize'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:120:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:189:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:237:in
`retrieve_new_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:476:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:475:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:236:in
`retrieve_new_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:86:in `retrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:112:in
`retrieve_and_apply_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:151:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:103:in `with_client'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:37:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `call'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:172:in `controlled_run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:35:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:336:in `onetime'
/usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:310:in
`run_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:410:in `hook'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:401:in `exit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute'
/usr/bin/puppet:4
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Is a directory - /etc/puppet/modules/network/templates/ at
/etc/puppet/modules/network/manifests/hosts.pp:10 on node
template.datacenter2
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
debug: Value of 'preferred_serialization_format' (pson) is invalid for
report, using default (marshal)
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
marshal


The 2 datacenter are connected by VPN and normally everything is open
from datacenter2 to datacenter1 but datacenter1 can't access datacenter2
except for 'established' traffic.

It seems to be a fileserver error but don't know how to debug this
feature. Any idea would be appreciate :D


Regards,
JM
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/z1RUzkw1VWkJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
categoriespuppet
postedNov 7, '12 at 6:16a
activeNov 7, '12 at 6:16a
posts1
users1
websitepuppetlabs.com

1 user in discussion

刘磊: 1 post

People

Translate

site design / logo © 2022 Grokbase