search for: certificaterequest

...ds me of something, that I experienced in the past. Why would the server! complain "Unknown CA"? To test inspect the communication with wireshark and look if the client sends a cert; or: $ echo "a001 LOGOUT" | openssl s_client -msg -connect your.server:993 and grep for "CertificateRequest". Do you have a certificate configured in your mailclient Thunderbird but not in Evolution? HTH Peter Am 2017-09-26 um 00:08 schrieb Michael A. Peters: > Definitely client issue, connecting via evolution works just fine. > > So I suppose it is off the the thunderbird list. I like...

...cate verify failed warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Server: # puppetca -s bar03 notice: Signed certificate request for ca notice: Rebuilding inventory file bar03 notice: Signed certificate request for bar03 notice: Removing file Puppet::SSL::CertificateRequest bar03 at ''/var/ lib/puppet/ssl/ca/requests/bar03.pem'' I have configured the time between the client and server using ntp but with the some o similar problem. Can this problem be due to DNS issues?. -- You received this message because you are subscribed to the Google Groups &qu...

...etca -l "puppet-client.test.com" (AC:EA:5B:B7:C6:A5:94:CE:26:1A:49:9E:F3:B1:EF:B1) [root@puppet-server manifests]# [root@puppet-server manifests]# puppet cert sign --all notice: Signed certificate request for puppet-client.test.com notice: Removing file Puppet::SSL::CertificateRequest puppet-client.test.com at ''/var/lib/puppet/ssl/ca/requests/puppet-client.test.com.pem'' [root@puppet-server manifests]# Well going. 5.[root@puppet-client ssl]# puppet agent --test --verbose --server puppet-server.test.com info: Caching certificate for...

...ve configured puppet master and agent. 1. Executed this "*puppetca --sign ip-10-194-18-145.ec2.internal*" command in puppet master instance. It returns an output like * notice: Signed certificate request for ip-10-194-18-145.ec2.internal* * notice: Removing file Puppet::SSL::CertificateRequest ip-10-194-18-145.ec2.internal at ''/var/lib/puppet/ssl/ca/requests/ip-10-194-18-145.ec2.internal.pem''* * *Is there any issue with this error ? 2. Created one site.pp file in *puppet master /etc/puppet/manifests* folder with below content. node ''client'...

...y when EC is being nice, the node comes up and puppet logs in and installs the agent which then generates a certificate and has it auto signed. After which the puppet agent exits (why?), and nobody is really happy after that: Sep 30 12:16:51 app01 puppet-master[18203]: Removing file Puppet::SSL::CertificateRequest 21b5041a-db2a-f26f-c2e6-faf3676a5d2a at ''/etc/puppet/ssl/ca/requests/21b5041a-db2a-f26f-c2e6- faf3676a5d2a.pem'' Sep 30 12:17:01 app01 puppet-master[18203]: Could not find node ''21b5041a-db2a-f26f-c2e6-faf3676a5d2a''; cannot compile What am I missing? Of course t...

...d not find certificate for ''client.domain.com'' info: Could not find certificate_request for ''client.domain.com'' notice: client.domain.com has a waiting certificate request notice: Signed certificate request for client.domain.com notice: Removing file Puppet::SSL::CertificateRequest client.domain.com at ''/var/lib/puppet/ssl/ca/requests/ client.domain.com.pem'' But when I reboot the machine, if I try to run puppetd again manually, I''m getting a private key error: puppetd --server puppet.domain.com --test --waitforcert 15 err: Could not request ce...

...a -l* notice: Signed certificate request for ca notice: Rebuilding inventory file l1311022.our.domain.de (19:60:00:FE:95:D8:1B:D1:7A:0A:08:C1:1F:E1:94:4E) *l1215022:/var/lib/puppet/ssl # pca -s --all* notice: Signed certificate request for l1311022.our.domain.de notice: Removing file Puppet::SSL::CertificateRequest l1311022.our.domain.de at ''/var/lib/puppet/ssl/ca/requests/l1311022.our.domain.de.pem'' l1215022:/var/lib/puppet/ssl # (CLIENT) *root@l1311022:/var/lib/puppet/ssl$ puppet agent --test* warning: peer certificate won''t be verified in this SSL session info: Caching certifi...

...Anyway, now I go back to the server, and yes, there''s a request waiting... prov01 ~:# puppetca --list app03.pax.livegamer.com I sign it... prov01 ~:# puppetca --sign app03.pax.livegamer.com notice: Signed certificate request for app03.pax.livegamer.com notice: Removing file Puppet::SSL::CertificateRequest app03.pax.livegamer.com at ''/var/lib/puppet/ssl/ca/requests/app03.pax.livegamer.com.pem'' I then go back to the client and restart puppet: [root@app03 puppet]# service puppet restart Stopping puppet: [ OK ] Starting puppet:...

...erienced in the past. Why would > the server! complain "Unknown CA"? To test inspect the communication > with wireshark and look if the client sends a cert; or: > > $ echo "a001 LOGOUT" | openssl s_client -msg -connect your.server:993 > > and grep for "CertificateRequest". > > Do you have a certificate configured in your mailclient Thunderbird but > not in Evolution? > > HTH > Peter > > Am 2017-09-26 um 00:08 schrieb Michael A. Peters: >> Definitely client issue, connecting via evolution works just fine. >> >> So I...

...ut why this is happening. master logs show:- Could not find certificate for ''<FQDN>'' Could not find certificate_request for ''<FQDN>'' <FQDN> has a waiting certificate request Signed certificate request for <FQDN> Removing file Puppet::SSL::CertificateRequest <FQDN> at ''/etc/puppet/ssl/ca/requests/<FQDN>.pem'' I am really stumped now. Any ideas what it could be, anything else to check ? Thanks Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscrib...

I'm not running any A/V software, and the same version of dovecot on servers with CA signed certs (komodo) - the client connects to them just fine. On 09/25/2017 01:40 PM, Tony wrote: > It does look like a client issue. Do you also have some kind of AV > running? There are some AV software that can sometimes interfere with > mail sessions. See if you might be running into a similar

...cate won''t be verified in this SSL session warning: peer certificate won''t be verified in this SSL session Then on the master: [master]# puppet cert --list foobar [master]# puppet cert --sign foobar notice: Signed certificate request for foobar notice: Removing file Puppet::SSL::CertificateRequest foobar at ''/etc/ puppet/ssl/ca/requests/foobar.pem'' Then back on the client: info: Caching certificate for foobar err: Could not retrieve catalog from remote server: hostname not match with the server certificate warning: Not using cache on failed catalog err: Could not retrieve...

...ertificate error: Could not render to pson: getaddrinfo: Name or service not known I tried to manually sign certificate from master as below [root@ip-10-224-122-211 tmp]# puppet cert sign ip-10-196-90-236 notice: Signed certificate request for ip-10-196-90-236 notice: Removing file Puppet::SSL::CertificateRequest ip-10-196-90-236 at ''/etc/puppetlabs/puppet/ssl/ca/requests/ip-10-196-90-236.pem'' But when i am trying to test from agent, i am getting errors again. [root@ip-10-196-90-236 ~]# puppet agent -t info: Retrieving plugin err: /File[/var/opt/lib/pe-puppet/lib]: Failed to generate ad...

Hey all, after installing the 3.0.0 version of puppet (debian package from puppetlabs), doing the initial config, doing an initial start of master to generate the certs needed and then starting apache with passenger to control puppetmaster. I can do: puppet ca list --all and get a listing of the certs in the system (initially only the master). afterwards, on the client node, I run: puppet

...' info: Could not find certificate_request for ''2c96865c-deb0-a646-2d94- c4287f72650f'' notice: 2c96865c-deb0-a646-2d94-c4287f72650f has a waiting certificate request notice: Signed certificate request for 2c96865c-deb0-a646-2d94- c4287f72650f notice: Removing file Puppet::SSL::CertificateRequest 2c96865c-deb0- a646-2d94-c4287f72650f at ''/etc/puppet/ssl/ca/requests/2c96865c-deb0- a646-2d94-c4287f72650f.pem'' 2c96865c-deb0-a646-2d94-c4287f72650f root@ip-10-36-11-244:/etc/puppet/manifests# puppet node classify ec2-50-19-149-210.compute-1.amazonaws.com --mode agent --node- gro...

Hi Experts, I''m trying to generate my own certificates (all of them, including certs for CA, server and client) for puppet to use. and I''m getting "Could not run: Could not retrieve certificate for puppetsrv and not running on a valid certificate authority" Just wondering what the problem could be? What I did is: 1. generate a self signed CA cert, and save the

Hi all. I am testing 0.25.4 to upgrade from 0.23.2. In testing, I found two strange messages on 0.25.4 which I have never found on 0.24.3. So could you tell me what these messages mean and how to fix them. [Environment] Puppetmasterd -version : 0.25.4 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [Strange messages] 1.When Puppetd

I''m running in circles with this issue... I accidentally did a ''puppetca --clean --all'' and lost all certificates. I was able to get the puppetmaster running and re-created certificates for the client system, but I get the following error: warning: peer certificate won''t be verified in this SSL session info: Caching certificate for w0f.lagged.com info:

...rtificate found and waitforcert is disabled MASTER [root@puppet centos]# puppet cert list "fp2" (SHA1) 35:51:A0:12:CF:2E:F7:73:22:C3:5E:51:DC:03:AF:4C:FC:54:5C:10 [root@puppet centos]# puppet cert sign fp2 Notice: Signed certificate request for fp2 Notice: Removing file Puppet::SSL::CertificateRequest fp2 at ''/var/lib/puppet/ssl/ca/requests/fp2.pem'' AGENT [root@FP2 ~]$ puppet agent -t Info: Caching certificate for fp2 Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B...