Dan White
2012-Jun-26 18:43 UTC
[Puppet Users] Next Problem: Puppet 2.7 + Passenger won''t connect
OK. What did I booger up this time ? agent.myexample.org and puppetmaster.myexample.org are the same server. ---------------------------------------------------------------------------- # puppetd --no-daemonize --onetime --debug --noop debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Failed to load library ''ldap'' for feature ''ldap'' debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: Finishing transaction 23912129611220 debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: Finishing transaction 23912128448160 debug: Using cached certificate for ca debug: Using cached certificate for agent.myexample.org debug: Finishing transaction 23912127941800 debug: Loaded state in 0.02 seconds info: Retrieving plugin debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent.myexample.org debug: Using cached certificate_revocation_list for ca err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: Connection refused - connect(2) debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson err: /File[/var/lib/puppet/lib]: Could not evaluate: Connection refused - connect(2) Could not retrieve file metadata for puppet://puppetmaster.myexample.org/plugins: Connection refused - connect(2) debug: Finishing transaction 23912129691440 info: Loading facts in /etc/puppet/modules/old-firewall/lib/facter/iptables.rb info: Loading facts in /etc/puppet/modules/badperms/lib/facter/unlabeled_device_files.rb info: Loading facts in /etc/puppet/modules/firewall/lib/facter/broadcast.rb info: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables.rb info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb info: Loading facts in /var/lib/puppet/lib/facter/iptables.rb info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb info: Loading facts in /var/lib/puppet/lib/facter/unlabeled_device_files.rb info: Loading facts in /var/lib/puppet/lib/facter/broadcast.rb debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson err: Could not retrieve catalog from remote server: Connection refused - connect(2) info: Not using expired catalog for agent.myexample.org from cache; expired at Tue Jun 05 13:43:17 -0400 2012 notice: Using cached catalog err: Could not retrieve catalog; skipping run debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml err: Could not send report: Connection refused - connect(2) ------------------------------------------------------------------------------ “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Craig White
2012-Jun-26 20:08 UTC
Re: [Puppet Users] Next Problem: Puppet 2.7 + Passenger won''t connect
On Jun 26, 2012, at 11:43 AM, Dan White wrote:> OK. What did I booger up this time ? > > agent.myexample.org and puppetmaster.myexample.org are the same server. > > ---------------------------------------------------------------------------- > # puppetd --no-daemonize --onetime --debug --noop > > debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist > debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist > debug: Puppet::Type::User::ProviderPw: file pw does not exist > debug: Puppet::Type::User::ProviderLdap: true value when expecting false > debug: Failed to load library ''ldap'' for feature ''ldap'' > debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/private_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] > debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] > debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] > debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/public_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] > debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/certs/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] > debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] > debug: Finishing transaction 23912129611220 > debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/certs/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] > debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] > debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/public_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] > debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/ssl/private_keys/agent.myexample.org.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] > debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] > debug: Finishing transaction 23912128448160 > debug: Using cached certificate for ca > debug: Using cached certificate for agent.myexample.org > debug: Finishing transaction 23912127941800 > debug: Loaded state in 0.02 seconds > info: Retrieving plugin > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > debug: Using cached certificate for ca > debug: Using cached certificate for agent.myexample.org > debug: Using cached certificate_revocation_list for ca > err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: Connection refused - connect(2) > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson > err: /File[/var/lib/puppet/lib]: Could not evaluate: Connection refused - connect(2) Could not retrieve file metadata for puppet://puppetmaster.myexample.org/plugins: Connection refused - connect(2) > debug: Finishing transaction 23912129691440 > info: Loading facts in /etc/puppet/modules/old-firewall/lib/facter/iptables.rb > info: Loading facts in /etc/puppet/modules/badperms/lib/facter/unlabeled_device_files.rb > info: Loading facts in /etc/puppet/modules/firewall/lib/facter/broadcast.rb > info: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables.rb > info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb > info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb > info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb > info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb > info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb > info: Loading facts in /var/lib/puppet/lib/facter/iptables.rb > info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb > info: Loading facts in /var/lib/puppet/lib/facter/unlabeled_device_files.rb > info: Loading facts in /var/lib/puppet/lib/facter/broadcast.rb > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson > err: Could not retrieve catalog from remote server: Connection refused - connect(2) > info: Not using expired catalog for agent.myexample.org from cache; expired at Tue Jun 05 13:43:17 -0400 2012 > notice: Using cached catalog > err: Could not retrieve catalog; skipping run > debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) > debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml > err: Could not send report: Connection refused - connect(2)---- something wrong with your apache/passenger setup I think. what do you get from... ps aux|grep apache netstat -ntulp ? Craig -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Dan White
2012-Jun-26 20:20 UTC
Re: [Puppet Users] Next Problem: Puppet 2.7 + Passenger won''t connect
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) ----- Craig White <craig.white@ttiltd.com> wrote:> > On Jun 26, 2012, at 11:43 AM, Dan White wrote: > > > OK. What did I booger up this time ? > > > > agent.myexample.org and puppetmaster.myexample.org are the same server. > > > > ---------------------------------------------------------------------------- > > # puppetd --no-daemonize --onetime --debug --noop > > > > debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist-----SNIP----------> > err: Could not send report: Connection refused - connect(2) > ---- > something wrong with your apache/passenger setup I think. > > what do you get from... > ps aux|grep apache > netstat -ntulp > ? > > CraigThis is a RHEL5 box. The package/service is httpd # ps aux | grep httpd root 12698 0.0 0.0 61192 760 pts/0 S+ 16:14 0:00 grep httpd root 18111 0.0 0.0 191532 4720 ? Ss 14:13 0:00 /usr/sbin/httpd apache 18128 0.0 0.0 191664 2856 ? S 14:13 0:00 /usr/sbin/httpd apache 18129 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd apache 18130 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd apache 18131 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd apache 18132 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd apache 18133 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd apache 18134 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd apache 18135 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd # netstat -ntulp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN 4008/java tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN 2718/rsyslogd tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN 2738/snmpd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2756/sshd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2798/sendmail tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 12622/sshd tcp 0 0 :::514 :::* LISTEN 2718/rsyslogd tcp 0 0 :::9898 :::* LISTEN 4008/java tcp 0 0 :::80 :::* LISTEN 18111/httpd tcp 0 0 :::22 :::* LISTEN 2756/sshd tcp 0 0 ::1:6010 :::* LISTEN 12622/sshd tcp 0 0 :::443 :::* LISTEN 18111/httpd udp 0 0 0.0.0.0:514 0.0.0.0:* 2718/rsyslogd udp 0 0 0.0.0.0:514 0.0.0.0:* 2718/rsyslogd udp 0 0 127.0.0.1:25375 0.0.0.0:* 2738/snmpd udp 0 0 127.0.0.1:25376 0.0.0.0:* 3219/cmapeerd udp 0 0 0.0.0.0:161 0.0.0.0:* 2738/snmpd udp 0 0 127.0.0.1:25393 0.0.0.0:* 3469/cmanicd udp 0 0 :::514 :::* 2718/rsyslogd udp 0 0 :::514 :::* 2718/rsyslogd I am guessing there should be an 8140 in that netstat, right ? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Craig White
2012-Jun-26 21:07 UTC
Re: [Puppet Users] Next Problem: Puppet 2.7 + Passenger won''t connect
On Jun 26, 2012, at 1:20 PM, Dan White wrote:> > > “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > ----- Craig White <craig.white@ttiltd.com> wrote: >> >> On Jun 26, 2012, at 11:43 AM, Dan White wrote: >> >>> OK. What did I booger up this time ? >>> >>> agent.myexample.org and puppetmaster.myexample.org are the same server. >>> >>> ---------------------------------------------------------------------------- >>> # puppetd --no-daemonize --onetime --debug --noop >>> >>> debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist > -----SNIP---------- >>> err: Could not send report: Connection refused - connect(2) >> ---- >> something wrong with your apache/passenger setup I think. >> >> what do you get from... >> ps aux|grep apache >> netstat -ntulp >> ? >> >> Craig > > This is a RHEL5 box. The package/service is httpd > > # ps aux | grep httpd > root 12698 0.0 0.0 61192 760 pts/0 S+ 16:14 0:00 grep httpd > root 18111 0.0 0.0 191532 4720 ? Ss 14:13 0:00 /usr/sbin/httpd > apache 18128 0.0 0.0 191664 2856 ? S 14:13 0:00 /usr/sbin/httpd > apache 18129 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > apache 18130 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > apache 18131 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > apache 18132 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > apache 18133 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > apache 18134 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > apache 18135 0.0 0.0 191664 2852 ? S 14:13 0:00 /usr/sbin/httpd > > # netstat -ntulp > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN 4008/java > tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN 2718/rsyslogd > tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN 2738/snmpd > tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2756/sshd > tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2798/sendmail > tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 12622/sshd > tcp 0 0 :::514 :::* LISTEN 2718/rsyslogd > tcp 0 0 :::9898 :::* LISTEN 4008/java > tcp 0 0 :::80 :::* LISTEN 18111/httpd > tcp 0 0 :::22 :::* LISTEN 2756/sshd > tcp 0 0 ::1:6010 :::* LISTEN 12622/sshd > tcp 0 0 :::443 :::* LISTEN 18111/httpd > udp 0 0 0.0.0.0:514 0.0.0.0:* 2718/rsyslogd > udp 0 0 0.0.0.0:514 0.0.0.0:* 2718/rsyslogd > udp 0 0 127.0.0.1:25375 0.0.0.0:* 2738/snmpd > udp 0 0 127.0.0.1:25376 0.0.0.0:* 3219/cmapeerd > udp 0 0 0.0.0.0:161 0.0.0.0:* 2738/snmpd > udp 0 0 127.0.0.1:25393 0.0.0.0:* 3469/cmanicd > udp 0 0 :::514 :::* 2718/rsyslogd > udp 0 0 :::514 :::* 2718/rsyslogd > > I am guessing there should be an 8140 in that netstat, right ?---- yes, if you have passenger properly configured as a puppetmaster, it would be listening on port 8140 Craig -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Dan White
2012-Jun-27 01:59 UTC
Re: [Puppet Users] Next Problem: Puppet 2.7 + Passenger won''t connect
On Jun 26, 2012, at 5:07 PM, Craig White wrote:> On Jun 26, 2012, at 1:20 PM, Dan White wrote: >> I am guessing there should be an 8140 in that netstat, right ? > ---- > yes, if you have passenger properly configured as a puppetmaster, it would be listening on port 8140Part of the problem is that the instructions I was trying to follow at http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger and http://docs.puppetlabs.com/guides/passenger.html are a bit old and rusty. The old wiki says it is outdated, but the guides page has more detail about setting up puppet 0.2[45].x than any other version. Anyone got some cheese to go with this whine ? :) Well, I will roll up my sleeves, dive in and see if I can figure it out. And I will make a contribution to the documentation once I get it straight ! This is my promise. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Dan White
2012-Jun-27 14:04 UTC
Re: [Puppet Users] Next Problem: Puppet 2.7 + Passenger won''t connect
----- Dan White <ygor@comcast.net> wrote:> > On Jun 26, 2012, at 5:07 PM, Craig White wrote: > > On Jun 26, 2012, at 1:20 PM, Dan White wrote: > >> I am guessing there should be an 8140 in that netstat, right ? > > ---- > > yes, if you have passenger properly configured as a puppetmaster, it would be listening on port 8140 > > Part of the problem is that the instructions I was trying to follow at > > http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > and > http://docs.puppetlabs.com/guides/passenger.html > are a bit old and rusty. The old wiki says it is outdated, but the guides page has more detail about setting up puppet 0.2[45].x than any other version. > > Anyone got some cheese to go with this whine ? :) > > Well, I will roll up my sleeves, dive in and see if I can figure it out. > And I will make a contribution to the documentation once I get it straight ! This is my promise. > >I found the problem. Part mine, part Puppet''s /usr/share/puppet/ext/rack/manifest.pp out of the puppet-2.7.(12/17)-1.el5.noarch.rpm file { "/etc/apache2/conf.d/puppetmasterd": ensure => present, source => "puppet:///modules/rack/apache2.conf", mode => 0644, owner => root, group => root, require => [File["/etc/puppet/rack/config.ru"], File["/etc/puppet/rack/public"], Package["apache2"], Package["passenger"]], notify => Service["apache2"], } Couple of problems with this -- one I caught before and the other that caused me grief later. First problem: On Red Hat, the package/service is httpd instead of apache2 Second problem: /etc/apache2/conf.d/puppetmasterd was being ignored ''cause /etc/httpd/conf/httpd.conf says: # # Load config files from the config directory "/etc/httpd/conf.d". # Include conf.d/*.conf So I renamed /etc/apache2/conf.d/puppetmasterd to /etc/apache2/conf.d/puppetmaster.conf and now my Passenger-Driven Puppet Master is running ! “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Possibly Parallel Threads
- on puppet master server , puppet agent can't connect to itself
- retrieving module directory
- Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
- Puppet Agent VS User
- Puppet master can not find file_metadata for my puppet module