3

私の Mac にはいくつかの並列 Vm があり、それらの間の単純な接続をパペット マスターとパペット クライアントとしてセットアップしようとしています。

  1. パペットマスター (CentOs 6.2 上)
  2. Puppet クライアント (Ubuntu 12.1 サーバー上)

次のコマンドを使用してクライアントに接続しようとすると。

puppet agent --server 192.168.1.103 --waitforcert 60 --test --verbose

次の出力に接続しようとします

warning: peer certificate won't be verified in this SSL session
info: Caching certificate for ca
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
info: Creating a new SSL certificate request for puppet1.localdomain
info: Certificate Request fingerprint (md5) : 2E:C6:D2:C2:........
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
notice: Did not receive certificate

サーバー側では、次の出力をリッスンするデバッグ パペット マスターがあります。

notice: Starting Puppet master version 2.7.14
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: access[^/catalog/([^/]+)$]: allowing 'method' find
info: access[^/catalog/([^/]+)$]: allowing $1 access
info: access[^/node/([^/]+)$]: allowing 'method' find
info: access[^/node/([^/]+)$]: allowing $1 access
info: access[/certificate_revocation_list/ca]: allowing 'method' find
info: access[/certificate_revocation_list/ca]: allowing * access
info: access[/report]: allowing 'method' save
info: access[/report]: allowing * access
info: access[/file]: allowing * access
info: access[/certificate/ca]: adding authentication any
info: access[/certificate/ca]: allowing 'method' find
info: access[/certificate/ca]: allowing * access
info: access[/certificate/]: adding authentication any
info: access[/certificate/]: allowing 'method' find
info: access[/certificate/]: allowing * access
info: access[/certificate_request]: adding authentication any
info: access[/certificate_request]: allowing 'method' find
info: access[/certificate_request]: allowing 'method' save
info: access[/certificate_request]: allowing * access
info: access[/]: adding authentication any
info: Inserting default '/status' (auth true) ACL because none were found in '/etc/puppet/auth.conf'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate_request for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
notice: puppet1.localdomain has a waiting certificate request
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'

ホスト解決と単純な IP アドレスだけを使用せずに、単純なパペット構成を設定することは可能ですか?

何か助けはありますか？

4

1 に答える 1

2

/ etc/hostsファイルに両方のVMのIPを追加するだけで問題が修正されました。それから人形は私のためにうまく働いています。

于 2012-05-27T02:27:23.623 に答える