On Mon, Feb 14, 2011 at 10:12 PM, mark risher <[email protected]> wrote: > Thanks for the follow-up. Here is the puppetmasterd --genconf output: > http://pastebins.com/index.php?show=568; I have not made any changes > from the default, Ubuntu package installation, so the actual > puppet.conf file is just the pathnames. > > I've been running the server using the `/etc/init.d/puppetmasterd > start` command. There is very little log output in the masterhttp.log, > but here's what I see:
Shutdown the service and run puppet master with the following flags to get debug info: puppet master --no-daemonize -v > root@lab2:/var/log/puppet# more masterhttp.log > [2011-02-14 22:04:57] INFO WEBrick 1.3.1 > [2011-02-14 22:04:57] INFO ruby 1.8.7 (2010-01-10) [x86_64-linux] > [2011-02-14 22:04:57] INFO > Certificate: > Data: > Version: 3 (0x2) > Serial Number: 2 (0x2) > Signature Algorithm: sha1WithRSAEncryption > Issuer: CN=ca > Validity > Not Before: Feb 14 01:20:25 2011 GMT > Not After : Feb 13 01:20:25 2016 GMT > Subject: CN=lab2.domain.com > Subject Public Key Info: > Public Key Algorithm: rsaEncryption > RSA Public Key: (1024 bit) > Modulus (1024 bit): > 00:d5:f0:60:01:99:43:a8:d5:ce:0f:67:d1:d0:b2: > <snip> > Exponent: 65537 (0x10001) > X509v3 extensions: > Netscape Comment: > Puppet Ruby/OpenSSL Generated Certificate > X509v3 Basic Constraints: critical > CA:FALSE > X509v3 Subject Key Identifier: > E8:82:E2:46:38:25:B8:1C:9B:89:A7:FC:7D:96:22:12:BE: > 23:8E:9C > X509v3 Key Usage: > Digital Signature, Key Encipherment > X509v3 Extended Key Usage: > TLS Web Server Authentication, TLS Web Client > Authentication, E-mail Protection > X509v3 Subject Alternative Name: > DNS:puppet, DNS:lab2.domain.com, DNS:puppet.domain.com > Signature Algorithm: sha1WithRSAEncryption > 48:f5:6a:9a:c9:8d:69:7e:5a:e6:fa:38:c4:65:a4:5a:26:1e: > <snip> > [2011-02-14 22:04:57] INFO WEBrick::HTTPServer#start: pid=20959 > port=8140 > [2011-02-14 22:05:03] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:03 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:03] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:03] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:03 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:03] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:21] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:21 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:21] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:50] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:50 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:50] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:50] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:50 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:50] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:50] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:50 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:50] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:56] events.edgesentinel.com - - [14/Feb/ > 2011:22:05:56 PST] "GET /production/certificate/events1001.domain.com > HTTP/1.1" 404 51 > [2011-02-14 22:05:56] - -> /production/certificate/ > events1001.domain.com > [2011-02-14 22:05:57] INFO going to shutdown ... > [2011-02-14 22:05:57] INFO WEBrick::HTTPServer#start done. > root@lab2:/var/log/puppet# Seems like the agent is just waiting for a certificate and you don't have the CSR on the master. I'm not sure of a way to force the agent to submit the CSR again. Since I don't have the exact directory configuration, rather than asking you to copy the CSR to the server I'm going to recommend cleaning the agent's ssl directory so it will generate and submit the certificate request again. With the master in verbose mode you should see the following: (using demo.example.lan) info: Could not find certificate for 'demo.example.lan' info: Could not find certificate_request for 'demo.example.lan' notice: demo.example.lan has a waiting certificate request info: Could not find certificate for 'demo.example.lan' info: Could not find certificate for 'demo.example.lan' At this point you should have a certificate waiting to be signed. Thanks, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
