similar to: Puppet 3.2.0-0.1rc2.el6 SSL problem

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

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

Hi everyone, Please help, I have built a new server and installed puppet (2.6.17) running on RHEL 6.3. It seems that it is not listening on port 8139. iptables -L: Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt

I''m just getting started with puppet and there''s something I can''t get working. I have a client/agent setup at the moment. When running puppet agent for the first time, I get the following error: puppet agent --test dnsdomainname: Unknown host Error: Could not request certificate: Error 400 on SERVER: Permission denied - /etc/puppet/auth.conf My auth.conf looks

Hi all, I have experience using puppet, however I am new to setting puppet up as it was already done for me in past environments. I am running into an issue while trying to set puppet up for the first time on RHEL 6.4. I was hoping y''all might be able to help me! I get the following error from the puppet client''s /var/log/messages log: May 30 07:06:30 pclient

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

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

I am working on setting up a Puppet configuration where some of the data is stored on a DRBD volume. The modules and vardir are stored on the drbd volume. The puppet.conf files point to the drbd volume for vardir. I created a cert for a VIP puppet-master using the puppetca -- create command I had everything working on the primary drbd node, but when I fail over, everything starts up fine, but I

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

I''ve configured our DMZ apache webserver to proxy connections from our roaming users into our internal puppet master running under passenger/apache. Everything is pretty much working but because I am using SSL between the proxy server and the puppet master, the master treats the connection as authenticated as the proxy. My current work around is to allow access to all catalog and

Hello, I am running a puppet master version 2.7.5 on Centos 5.7 and a puppet agent version 2.7.5. I am simply trying to apply changes to files by defining a file resource in my manifest. When I execute my puppet agent to do the installation it complains it can not find the file meta data. Here is my manifest. class neospeech::config { file { "/usr/vwmrcpd/vwmrcpd/vwmrcpd":

Hello List, I have a problem with the CA on my Puppetmaster. This Puppetmaster is connected to different Networks with different sub domainnames. The Puppet clients connecting via different Interfaces. There is no routing between subnets. Only one subnet can connect successfully. This is because the subject in the Certificate is the name of this subnet. All other clients get: Could not

When I try to connect to * using a Cisco ATA 188 configured with a MGPC firmware (v3.1.1), I just keep getting this message every 30 seconds or so : May 10 10:08:21 NOTICE[7913]: chan_mgcp.c:1509 find_subchannel: Gateway '192.168.1.27' (and thus its endpoint '*') does not exist Using tcpdump, I have checked that the ATA188 (with IP 192.168.1.27 and port 2427) sends UDP packets to

Hi guys, we have a rebalance running on eight bricks since July and this is what the status looks like right now: ===Tue Oct 18 13:45:01 CST 2011 ==== rebalance step 1: layout fix in progress: fixed layout 223623 There are roughly 8T photos in the storage,so how long should this rebalance take? What does the number (in this case) 22362 represent? Our gluster infomation: Repository

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, opensuse 13.2 linux v3.16.7-7-desktop x86_64 rsync v3.1.1 I used rsync to copy /usr/ to another volume with these options: - --recursive --one-file-system --links --stats --itemize-changes - --quiet --delete --times After I had modified the system to use the new /usr volume, I realized I should have added: - --perms --owner --group

Does anybody has the expirience configuring Asterisk with Cisco ATA 186 MGCP firmware ? I have Cisco software v3.1.1 atamgcp (Build 040629A) Asterisk 1.0-RC1 On ATA i only put domain test. mgcp.conf looks like this [test] host = 192.168.195.55 context = default line => aaln/2 line => aaln/1 Asterisk CLI shows this: Jul 31 16:05:40 WARNING[135449600]: chan_mgcp.c:485

On Thu, 15 Jun 2017 13:23:44 +0000 just subscribed for rsync-qa from bugzilla via rsync <rsync at lists.samba.org> wrote: > https://bugzilla.samba.org/show_bug.cgi?id=12819 > > --- Comment #7 from Ben RUBSON <ben.rubson at gmail.com> --- > Note that my patch simply adds a sync() just after recv_files(), so > one sync() per connection, not per write operation. >

I noticed a behaviour which is kind of confusing. I have the puppetmasterd running. Now I want a new client to connect. I edit the site.pp and add the client. When the client is started I can see it with puppetca --list. So I sign the client. When it next tries to connect it shows: notice: Allowing ::ffff:192.168.x.y(::ffff:192.168.x.y) untrusted access to CA methods notice: Host

Hi, I have just started to get dovecot list messages which I had not been receiving until today. How can I opt out (again)? regards, Michal Szymanski On Fri, Nov 30, 2018 at 10:42:22AM +0100, Per Jessen wrote: > Aki Tuomi wrote: > >On 30.11.2018 10.03, Per Jessen wrote: > > > >>Hi AKi > >> > >>I guess my address was re-subscribed then? I was subscribed

Hi, on CentOS 6.3 (32-bit) current & default GnuTLS is version 2.8.5-4.el6_2.2 gnutls.i686 ( where can i get a src rpm for at-least trying it from a 2nd/different directory ? ) Can someone kindly point to an article that will help to effectively upgrade to GnuTLS v3.1.1 or later+stable version, on CentOS 6.3 (32-bit) ? Need the DANE supported GnuTLS, will be used for various GnuTLS depended