similar to: Could not request certificate: Error 405 on SERVER

Displaying 20 results from an estimated 1000 matches similar to: "Could not request certificate: Error 405 on SERVER"

2011 Jan 10
7
Could not request certificate: No route to host?
Hi, I''m getting this message "Could not request certificate: No route to host - connect(2)" when I''m trying to connect my pclient to pmaster. I checked my hostnames for both the pclient and the pmaster: [root@pclient etc]# hostname -f pclient.domain [root@pmaster etc]# hostname -f pmaster.domain I tried requesting for certificate: [root@pclient etc]# puppetd --server
2011 Jul 08
2
Puppetmaster setup with separate CA server configuration help
Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd
2013 Jul 23
3
Debugging Puppetmaster with Apache/Rack/Passenger
Hi, I''m currently trying to debug a performance issue I''m having. Therefore I would need "DEBUG" output. When using one puppetmaster process, this is fairly easy by starting it like this: > puppet master --no-daemonize --debug Now I need to see this debug output when running puppetmaster the way I ususally do - using Apache/Rack/Passenger. After looking
2014 Mar 13
2
[PATCH] nouveau: safen up nouveau_device list usage against concurrent access
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- nouveau/nouveau.c | 29 ++++++++++++++++++++++++++++- nouveau/private.h | 3 ++- 2 files changed, 30 insertions(+), 2 deletions(-) diff --git a/nouveau/nouveau.c b/nouveau/nouveau.c index ee7893b..72c31cf 100644 --- a/nouveau/nouveau.c +++ b/nouveau/nouveau.c @@ -85,6 +85,12 @@ nouveau_device_wrap(int fd, int close, struct
1997 Jul 29
1
Net use problem (fwd)
> Has anyone experienced this problem? > > Server: Solaris 2.5 system with a fresh install of Samba 1.9.16p11. > Clients: WinNT 4.0 and Win95 > > When we net use e: \\javaws1\pclient, Error: network name cannot be > found. > > However, we net use e: \\javaws1\userid, the connect is successful. > > After doing that... > When we net use f: \\javaws1\pclient,
2011 Feb 15
11
Puppetmasterd not receiving certificate request
Hi: I''m trying to configure Puppet on Ubuntu, and strangely I am never able to generate a certificate because my server never shows any pending certificate requests. Put differently, on the server I am running puppetmasterd and on the client I am able to connect to the server, but the client continues printing notice: Did not receive certificate warning: peer certificate
2012 Jul 18
4
cert issues, puppet agent applying configs, problems oh my!
So I''m new to puppet and I''m having a bear of a time just getting a test server going. I installed puppet and the puppet client via yum on CentOS on AWS, so that saved me some time. I followed a few various blog posts about getting everything set up and applying a file, etc. Now I am trying to install a module (puppetlabs/apache) and it''s failing miserably for me. I
2012 Feb 12
1
Using templates
Hi everyone, I''m learning Puppet and I want to configure ssh server with different port on different nodes. Puppet v2.7.1 I have created module ssh: content of modules/ssh/manifests/install.pp class ssh::install { package { "ssh": ensure => present, } } content of modules/ssh/manifests/service.pp class ssh::service { service { "ssh": ensure =>
2007 Jul 05
10
Wierd issue with node declaration
I have the following in my site.pp node "pclient.example.com" inherits default {} When I try to start puppetmaster it gives me the following error Starting puppetmaster: Syntax error at ''pclient.example.com'' at /etc/puppet/manifests/site.pp:24 When I change the node declaration to this node ''pclient.example.com'' inherits default {} puppetmaster
2009 Dec 03
1
Could not retrieve catalog
Hello all, I''m running puppet for the first ime. I''ve finished the install but I''m stuck at the certificate part. The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet client (0.24.8-4.el5) is running on CentOS 5.3. After the install, from the client side, I''ve run: puppetd --server puppetmaster.domain.com --waitforcert 60 --test On the
2010 Feb 19
11
Strange messages on 0.25.4.
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
2009 Aug 30
3
restart puppetmaster when files change
I create this class pmaster in order to restart puppetmaster daemon after /etc/puppet/puppet.conf file change. class pmaster { file { "/etc/puppet/puppet.conf": ensure => "file"; } service { "puppetmaster": ensure => "running", enable => "true", hasrestart => "true", subscribe => File [
2010 Jun 09
4
Could not retrieve catalog from remote server: certificate verify failed
Hi guys, I''m trying to setup my first puppet installation and I''m running into problems. I''ve got the puppetmaster running on a fresh install of Centos 5.4. The puppet client is also on another Centos 5.4 server. Once I''ve signed the client certificate on the puppetmaster, the client seems to break. See below for the debug output from the client. Any clue as
2010 Aug 19
7
External CA: Could not run: Could not retrieve certificate for puppetsrv and not running on a valid certificate authority
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
2011 Jul 22
9
Random error in the recovery catalog
Hello, I randomly errors like this: Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog from remote server: end of file reached Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (notice): Using cached catalog Fri Jul 22 09:01:41 +0000 2011 //SERVER.fqdn/Puppet (err): Could not retrieve catalog; skipping run Here are the versions: puppetmaster
2023 May 28
1
command [argument ...] in ssh(1): a footgun
On Sat, May 27, 2023 at 02:45:34AM +0200, Thorsten Glaser <t.glaser at tarent.de> wrote: > On Sat, 27 May 2023, raf wrote: > > >So, perhaps this could be added to the existing > >sentence/paragraph: > > > > "so any spaces in individual arguments must be > > Must they? No, a single space will do just fine. They do if you want the receiving shell
2013 Dec 06
13
Can't seem to get modulepath attribute recognized by puppetmasterd
Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet
2013 May 02
1
Beginner : First Agent/Master, Passenger Error
Hello, I''m new to Puppet, and I''m trying to configure my first Agent/Master node. It''s running under 3 VM''s (Ubuntu server 12.04), a master running with Passenger, and 2 Agents. (But I''m only configuring one at the moment) Well, I followed this<http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html>
2011 Apr 14
10
allow_duplicate_certs = true not working?
I saw this feature became available in 2.7.0rc1 and wanted to try it out. I entered ''allow_duplicate_certs = true'' on both my master and agent systems in the puppet.conf (not sure if its need in both, saw it in genconf for puppetd and puppetmasterd though ...). I also have autosign.conf configured to allow autosigning for our domain (*.domain.com). I had my agent register with
2012 Dec 06
2
pasenger does not start puppet master under nginx
On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status