search for: 8140

...away from WEBrick to apache/passenger, following the instruction here: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > and I can''t start httpd any more. It fails with this: Starting httpd: (98)Address already in use: make_sock: could not bind to > address [::]:8140 > (98)Address already in use: make_sock: could not bind to address > 0.0.0.0:8140 > no listening sockets available, shutting down > Unable to open logs > The problem comes from the virtual-host file for *puppetmaster, *in which it listening port 8140 and in fact 8140 is already in...

...vm1 is server & vm2 is client. In client I run, root@vm2# puppetd --server vm-devserver-18.dev.s.vonagenetworks.net -- waitforcert 60 --test and I see, /usr/lib/ruby/1.8/puppet/network/client/ca.rb:31:in `request_cert'': Certificate retrieval failed: Could not connect to vm1 on port 8140 (Puppet::Error) from /usr/sbin/puppetd:356 In server I run, root@vm1:/var/home/gsivaraj# puppetca --list And I get No certificates to sign As this is related to opening up the ports so, I did the following thing on server but of no use. Can you please help? 1) /etc/init.d/apparmor sto...

...mpletely ignored. However, if I leave it off, I get no caching at all because Puppet seems to make every single file request with a ? attached to it: > Jun 10 00:17:59.000000 puppetmaster-20372704.cloud.XYZ.com apache: puppetmaster-20372704.cloud.XYZ.com:443 204.236.165.198 - - - puppet.XYZ.com:8140 "GET /production/file_metadata/modules/zk/ssl/cacert.pem? HTTP/1.1" 200 330 "-" "-" 0/6260 > Jun 10 00:17:59.000000 puppetmaster-20372704.cloud.XYZ.com apache: puppetmaster-20372704.cloud.XYZ.com:443 204.236.165.198 - - - puppet.XYZ.com:8140 "GET /production/fi...

...h is composed by a puppetmaster running in my laptop (Macos Snow Leopard) and a puppet client running on a EC2 instance at Amazon. In order to allow the client to talk with the master I''m using an SSH Remote port forward, ie I login into from the laptop into the EC2 instance witha "-R 8140:localhost:8140" flag. This way when the clients connect into localhost:8140 this connection is forwarded back via SSH tunnel to my laptop. Now, whenever I test it with netcat or something similar, everything went fine, but when I run puppetd I got the error: "err: Could not request cert...

...my puppet master. When I try to run ''puppet agent --test'' on the client, I get err: Could not request certificate: Connection refused - connect(2) Exiting; failed to retrieve certificate and waitforcert is disabled I can''t telnet from the client to the server on port 8140. There are no firewalls between the 2 servers. I''ve turned off iptables and ip6tables on both servers. The times are sync''d. Both servers can ping each other by IP address and hostname. Doing a netstat -an on the puppet master server shows that it is not listening on port 814...

...nt requests a cert from a puppetmaster that is *not* the CA, I can see the request forwarded: (below) .4 is the agent .3 us the master proxying the request puppetca is the acting CA for all masters *Here is the what logs in access.log for the puppetmaster that is NOT the CA.* ubuntu-pupmaster1:8140 192.168.192.4 - - [26/Oct/2012:15:32:36 -0400] "GET /production/certificate/agent-hostname? HTTP/1.1" 200 2245 "-" "-" *Here is what logs in the master which IS the CA* puppetca:8140 192.168.192.3 - - [26/Oct/2012:15:32:33 -0400] "GET /" 400 588 "-&qu...

Hi, I am running puppet-server 0.25.5 on CentOS 5.4. I defined a moudle in /etc/puppet/fileserver.conf as below: [files] path /tmp/puppet allow * I also defined a resource in /etc/puppet/manifests/site.pp: file { "/etc/passwd": owner => "root", group => "bin", mode => 644, } file { "/tmp/0909.txt": source =>

Hello, I am installing puppet and keep getting this error [Puppet could not request certificate: No route to host -connect(2)] My DNS is resloving and i can ping the master from the agent. I have added this line to the iptables [iptables -I INPUT -s 192.168.1.20 -m tcp -p tcp --dport 8140 -j ACCEPT], where the IP is my agent. I have also added my master ip to /etc/puppet/puppet.conf Why am I still getting this error? ** -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving...

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 /var/lib/puppet/ puppetca generate puppet cert -g loadbalancer01 -- certdnsnames=puppetmaster:loadbalancer01 puppet cert -g primaryca --certdnsnames=p...

Take delivery of a great concession on your Meds-RX Name brands, Finest quality. Vast variety, including Difficult to find drugs 0 RX needed. Private with No waiting quarters or appointments required Shipped within 21 hours or under, discrete boxing Purchase in bulk and Save! Still additional http://uk.geocities.com/hanho_keeffes/?ms=05No prescription needed. Have you ze luggage? No; but

...te: Certificate retrieval failed: No route to host - connect(2) ------------ i tried the default ''bindaddress'' (0.0.0.0) and ''bindaddress = 127.0.0.1, no difference. i can successfully ping / telnet all other ports from the puppet- client to the puppet-master. only port 8140 gives this error (with both, telnet and puppetd) nestat on the server: tcp 0 0 127.0.0.1:8140 0.0.0.0:* LISTEN I''m completely lost here... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Goog...

...''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted: certificate verify failed If anyone could explain what''s happening with the certificates here, I''d really appreciate it. All the best, Adam Kosmin

...2.test.net. Here is mine: LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-3.0.18/ext/apache2/mod_passenger.so PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-3.0.18 PassengerRuby /usr/bin/ruby <Proxy balancer://puppet_ca> BalancerMember http://puppet-master1.test.net:8140 </Proxy> ProxyPassMatch ^(/.*?)/(certificate.*?)/(.*)$ balancer://puppet_ca/ ProxyPassReverse ^(/.*?)/(certificate.*?)/(.*)$ balancer://puppet_ca/ Listen 8140 <VirtualHost *:8140> SSLEngine on SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-L...

When I run openssl s_client -host puppet -port 8081 -CAfile /etc/puppet/ssl/certs/puppet.fqdn I get Verify return code: 21 (unable to verify the first certificate). If I run the same command, but use port 8140 to connect to puppet, I get a return code of 19 (which is correct). I believe that, if I fix this SSL problem then it would fix my main problem which is : Report processor failed: Failed to submit ''store report'' command for puppet1.allantgroup.com to PuppetDB at fqdn:8081: SS...

...3 [error] 25920#0: *23 open() "/etc/puppet/rack/public/production/certificate/sl63anadi.XXXXX.com" failed (2: No such file or directory), client: 10.209.47.26, server: , request: "GET /production/certificate/sl63anadi.XXXXX.com? HTTP/1.1", host: "bangvmpllda02.XXXXX.com:8140" 2012/12/05 18:33:33 [error] 25920#0: *24 open() "/etc/puppet/rack/public/production/certificate_request/sl63anadi.XXXXX.com" failed (2: No such file or directory), client: 10.209.47.26, server: , request: "GET /production/certificate_request/sl63anadi.XXXXX.com? HTTP/1.1&qu...

Hi All, Puppet-dashboard appears to be having some trouble. Under inventory, it says: "Could not retrieve facts from inventory service: Permission denied - certs/dashboard.private_key.pem" When I run: curl -k -H "Accept: yaml" https://puppet:8140/production/facts/host.domain I get the expected dump of facts. Versions: puppet-dashboard is 1.1.0 (using passenger) puppet-master is 2.7.1 Went with an extremely loose config on test: Puppet Master: auth.conf: path /facts method find, search auth any allow * puppet.conf: # Reporting reporturl =...

...r/bin/ruby1.8 # cat /etc/apache2/conf.d/puppetmasterd (works perfect) # you probably want to tune these settings PassengerHighPerformance on PassengerMaxPoolSize 12 PassengerPoolIdleTime 1500 # PassengerMaxRequests 1000 PassengerStatThrottleRate 120 RackAutoDetect Off RailsAutoDetect Off Listen 8140 <VirtualHost *:8140> SSLEngine on SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP SSLCertificateFile /var/lib/puppet/ssl/certs/sys-ubuntu.arl.qwestip.net.pem SSLCertificateKeyFile /var/lib/puppet/ssl/priva...

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

...g the lines of: Could not call puppetmaster.getconfig: #<Errno::ECONNRESET: Connection reset by peer> I believe the puppetmasterd does not completely die, so it is still in the process list. I''m wondering what a good way to monitor this would be. I see that I can telnet into port 8140, is there something simple I can send that would give me an indication that everything is okay or not? Any suggestions on monitoring this would be appreciated. Pete --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups &qu...

...407 Hewlett-Packard Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552 (HSPA modem) Bus 002 Device 003: ID 0408:20f5 Quanta Computer, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 r...