Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension
That did the trick. Thanks. On Wednesday, October 1, 2014 4:41:44 PM UTC-7, Ellison Marks wrote: If you're using ubuntu, It would probably just be sudo apt-get install postgresql-contrib You might need to restart postgres after that, not sure. On Wednesday, October 1, 2014 2:10:40 PM UTC-7, Taylor Leese wrote: Ken - I'm using Ubuntu 14 and I installed PuppetDB via https://forge.puppetlabs.com/puppetlabs/puppetdb. I also should have noted that I got this error while upgrading from PuppetDB 2.1 to 2.2. Postgres is version 9.3.5 if I remember correctly. Admittedly, I'm not very familiar with Postgres. Ellison - How would I go about installing this contrib package to see if that helps? - Taylor On Wednesday, October 1, 2014 10:39:07 AM UTC-7, Ellison Marks wrote: As a note, I installed from the postgres yum repositories, as the version in stock centos 6 was getting too old. I had to install the -contrib package to get that extension. On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote: I tried the same thing and got the error below. Any ideas? puppetdb=# create extension pg_trgm; ERROR: could not open extension control file /usr/share/postgresql/9.3/extension/pg_trgm.control: No such file or directory Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug in that package or pg_trgm is shipped separately? I can probably take a look here. What distro and distro release is this exactly? Is this the PG shipped with the distro or is it from PGDG upstream? ken. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1fb0fa89-06f9-4ab5-a06b-a82f23ffe1dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension
I tried the same thing and got the error below. Any ideas? puppetdb=# create extension pg_trgm; ERROR: could not open extension control file /usr/share/postgresql/9.3/extension/pg_trgm.control: No such file or directory - Taylor On Saturday, August 30, 2014 12:42:30 AM UTC-7, Paul Seymour wrote: Ignore me didn't add the extension to the PuppetDB database. Added it to the puppetdb DB and hey presto:- 2014-08-30 08:40:27,935 INFO [c.p.p.s.migrate] Creating additional index `fact_paths_path_trgm` Too early in the morning for this sh.. Cheers Paul -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/01038d48-d73b-4394-95e3-d2b75c925e3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension
Ken - I'm using Ubuntu 14 and I installed PuppetDB via https://forge.puppetlabs.com/puppetlabs/puppetdb. I also should have noted that I got this error while upgrading from PuppetDB 2.1 to 2.2. Postgres is version 9.3.5 if I remember correctly. Admittedly, I'm not very familiar with Postgres. Ellison - How would I go about installing this contrib package to see if that helps? - Taylor On Wednesday, October 1, 2014 10:39:07 AM UTC-7, Ellison Marks wrote: As a note, I installed from the postgres yum repositories, as the version in stock centos 6 was getting too old. I had to install the -contrib package to get that extension. On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote: I tried the same thing and got the error below. Any ideas? puppetdb=# create extension pg_trgm; ERROR: could not open extension control file /usr/share/postgresql/9.3/extension/pg_trgm.control: No such file or directory Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug in that package or pg_trgm is shipped separately? I can probably take a look here. What distro and distro release is this exactly? Is this the PG shipped with the distro or is it from PGDG upstream? ken. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7cfee753-494f-4df6-9696-95c15dc6b4bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: PuppetDB 2.2 and pg_trgm extension
Ken - Also, to be even more specific I'm using the following version of the puppetdb module: mod 'puppetlabs/puppetdb', :git = 'g...@github.com:puppetlabs/puppetlabs-puppetdb.git', :ref = 'ba3049796f89aec8fb2857cb04d7f6b4dd71c4dc' On Wednesday, October 1, 2014 2:10:40 PM UTC-7, Taylor Leese wrote: Ken - I'm using Ubuntu 14 and I installed PuppetDB via https://forge.puppetlabs.com/puppetlabs/puppetdb. I also should have noted that I got this error while upgrading from PuppetDB 2.1 to 2.2. Postgres is version 9.3.5 if I remember correctly. Admittedly, I'm not very familiar with Postgres. Ellison - How would I go about installing this contrib package to see if that helps? - Taylor On Wednesday, October 1, 2014 10:39:07 AM UTC-7, Ellison Marks wrote: As a note, I installed from the postgres yum repositories, as the version in stock centos 6 was getting too old. I had to install the -contrib package to get that extension. On Wednesday, October 1, 2014 7:11:17 AM UTC-7, Ken Barber wrote: I tried the same thing and got the error below. Any ideas? puppetdb=# create extension pg_trgm; ERROR: could not open extension control file /usr/share/postgresql/9.3/extension/pg_trgm.control: No such file or directory Seems odd, pg_trgm should be shipped with PostgreSQL. Maybe its a bug in that package or pg_trgm is shipped separately? I can probably take a look here. What distro and distro release is this exactly? Is this the PG shipped with the distro or is it from PGDG upstream? ken. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0379f579-de92-410f-83f6-33aa0e8fc37b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Unmet dependencies: puppetmaster 3.7.0-1puppetlabs1
Hello all, I noticed this error today which is related to unmet dependencies for Puppet 3.7.0-1puppetlabs1 on Ubuntu Trusty. It's worth noting this was working perfectly as recently as a few days ago and today with no code changes there are dependency problems. I've actually noticed this in the past with 3.6.2 as well and upgraded to 3.7.0 to fix it, but this should not be happening when I'm specifying a explicit Puppet version because I don't want to always have to upgrade to keep things sane. Anybody else experiencing this problem? Or any ideas? Maybe I am doing something wrong. *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: /Stage[main]/Puppetmaster::Install/Package[puppetmaster-passenger]/ensure: change from purged to 3.7.0-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: /Stage[main]/Puppetmaster::Install/Package[puppetmaster]/ensure: change from purged to 3.7.0-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1'
[Puppet Users] Re: Unmet dependencies: puppetmaster 3.7.0-1puppetlabs1
I think it's also worth noting that Puppet 3.7.1 was released today. See https://docs.puppetlabs.com/puppet/3.7/reference/release_notes.html#puppet-371. This doesn't seem like a coincidence. - Taylor On Tuesday, September 16, 2014 1:08:47 AM UTC-7, Taylor Leese wrote: Hello all, I noticed this error today which is related to unmet dependencies for Puppet 3.7.0-1puppetlabs1 on Ubuntu Trusty. It's worth noting this was working perfectly as recently as a few days ago and today with no code changes there are dependency problems. I've actually noticed this in the past with 3.6.2 as well and upgraded to 3.7.0 to fix it, but this should not be happening when I'm specifying a explicit Puppet version because I don't want to always have to upgrade to keep things sane. Anybody else experiencing this problem? Or any ideas? Maybe I am doing something wrong. *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: /Stage[main]/Puppetmaster::Install/Package[puppetmaster-passenger]/ensure: change from purged to 3.7.0-1puppetlabs1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster-passenger=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster-passenger : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1) but it is not going to be installed* *E: Unable to correct problems, you have held broken packages.* *Wrapped exception:* *Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install puppetmaster=3.7.0-1puppetlabs1' returned 100: Reading package lists...* *Building dependency tree...* *Reading state information...* *Some packages could not be installed. This may mean that you have* *requested an impossible situation or if you are using the unstable* *distribution that some required packages have not yet been created* *or been moved out of Incoming.* *The following information may help to resolve the situation:* *The following packages have unmet dependencies:* * puppetmaster : Depends: puppetmaster-common (= 3.7.0-1puppetlabs1
Re: [Puppet Users] ENC fails on first run - Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml
I don't believe so because it works fine on the second run. I actually switched to using Hiera as the classifier since this was problematic. On Sun, Jul 20, 2014 at 11:02 PM, David Schmitt da...@dasz.at wrote: You ENC seems to depend upon the host's facts in the default yaml cache location. Perhaps you have removed the yaml caching of facts? Regards, David On 2014-07-14 23:46, Taylor Leese wrote: I incorrectly redacted the host name in the error message. Here is the correct version: *== nexus: **Warning: Unable to fetch my node definition, but the agent run will continue:* *== nexus: **Warning: Error 400 on SERVER: Failed to find nexus.myhost.com http://nexus.myhost.com/ via exec: Execution of '/etc/puppet/bin/node_classifier nexus.myhost.com http://my.host.com/' returned 1: Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml* *== nexus: * On Mon, Jul 14, 2014 at 2:43 PM, Taylor Leese tlees...@gmail.com mailto:tlees...@gmail.com wrote: Hi all - I setup an ENC and classification works for the most part except on the first run. I've noticed that the yaml file in /var/lib/puppet/yaml/facts doesn't exist on the first run so I receive a warning during Vagrant provisioning similar to below. Note, when I run the Puppet agent a subsequent time there is no error. I am using Puppet 3.4.3 and Facter 1.7.5. I also found a similar issue referenced in the Foreman project here (https://projects.theforeman.org/issues/5925). Any idea what could be causing this or if this might be a bug? *== nexus: **Warning: Unable to fetch my node definition, but the agent run will continue:* *== nexus: **Warning: Error 400 on SERVER: Failed to find nexus.myhost.com http://nexus.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier my.host.com http://my.host.com' returned 1: Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml* *== nexus: * - Taylor -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ kbL4rwAsG1g/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com mailto:puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7d6f51e3- 62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/7d6f51e3- 62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com?utm_medium= emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com mailto:puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKwbMverR_hndKRZ%2BdRA% 2BvorW6ONKxCV6okwz0C%2BopzadS0GxA%40mail.gmail.com https://groups.google.com/d/msgid/puppet-users/CAKwbMverR_hndKRZ%2BdRA% 2BvorW6ONKxCV6okwz0C%2BopzadS0GxA%40mail.gmail.com? utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/puppet-users/kbL4rwAsG1g/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/puppet-users/53CCACE2.80203%40dasz.at. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKwbMvdY__ph%2BPuqwCHKZUr60AqgbJ01jxtYi0jy7JcgEg6A%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] ENC fails on first run - Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml
Hi all - I setup an ENC and classification works for the most part except on the first run. I've noticed that the yaml file in /var/lib/puppet/yaml/facts doesn't exist on the first run so I receive a warning during Vagrant provisioning similar to below. Note, when I run the Puppet agent a subsequent time there is no error. I am using Puppet 3.4.3 and Facter 1.7.5. I also found a similar issue referenced in the Foreman project here (https://projects.theforeman.org/issues/5925). Any idea what could be causing this or if this might be a bug? *== nexus: **Warning: Unable to fetch my node definition, but the agent run will continue:* *== nexus: **Warning: Error 400 on SERVER: Failed to find nexus.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier my.host.com' returned 1: Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml* *== nexus: * - Taylor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7d6f51e3-62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] ENC fails on first run - Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml
I incorrectly redacted the host name in the error message. Here is the correct version: *== nexus: **Warning: Unable to fetch my node definition, but the agent run will continue:* *== nexus: **Warning: Error 400 on SERVER: Failed to find nexus.myhost.com http://nexus.myhost.com/ via exec: Execution of '/etc/puppet/bin/node_classifier nexus.myhost.com http://my.host.com/' returned 1: Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml* *== nexus: * On Mon, Jul 14, 2014 at 2:43 PM, Taylor Leese tlees...@gmail.com wrote: Hi all - I setup an ENC and classification works for the most part except on the first run. I've noticed that the yaml file in /var/lib/puppet/yaml/facts doesn't exist on the first run so I receive a warning during Vagrant provisioning similar to below. Note, when I run the Puppet agent a subsequent time there is no error. I am using Puppet 3.4.3 and Facter 1.7.5. I also found a similar issue referenced in the Foreman project here ( https://projects.theforeman.org/issues/5925). Any idea what could be causing this or if this might be a bug? *== nexus: **Warning: Unable to fetch my node definition, but the agent run will continue:* *== nexus: **Warning: Error 400 on SERVER: Failed to find nexus.myhost.com http://nexus.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier my.host.com http://my.host.com' returned 1: Error reading YAML file: No such file or directory - /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml* *== nexus: * - Taylor -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/kbL4rwAsG1g/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7d6f51e3-62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/7d6f51e3-62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAKwbMverR_hndKRZ%2BdRA%2BvorW6ONKxCV6okwz0C%2BopzadS0GxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Failed to find [host] via exec
The work around I went with is to just avoid the require 'puppet' line in my external node classifier so I can avoid this issue completely. I just ignore the first line of the YAML file in /var/lib/puppet/yaml/facts/ and do YAML.load rather than YAML.load_file. - Taylor On Saturday, July 12, 2014 5:23:19 PM UTC-7, Taylor Leese wrote: It's also worth mentioning that even if I chown and chgrp /root/.facter/facts.d to puppet I still receive the same error. That also doesn't seem like it should be the solution. I found two Puppet issues that may be related, but it's not entirely clear if they are exactly the same. https://tickets.puppetlabs.com/browse/FACT-176 https://tickets.puppetlabs.com/browse/PUP-2367 - Taylor On Saturday, July 12, 2014 5:06:22 AM UTC-7, Taylor Leese wrote: Jose - Ah, the puppet master itself is running as the puppet user. *root@puppet:/etc/puppet# ps -ef | grep puppet* *root 1362 1 0 10:55 ?00:00:02 /usr/bin/ruby /usr/bin/puppet agent* *puppet 20719 1 0 11:31 ?00:00:00 Passenger RackApp: /usr/share/puppet/rack/puppetmasterd* I tried the following and got an error: *root@puppet:/etc/puppet# sudo -u puppet ./bin/node_classifier * */usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `open': Permission denied - /root/.facter/facts.d (Errno::EACCES)* I'm not sure if this is really indicative of the actual problem or not. - Taylor On Saturday, July 12, 2014 4:54:22 AM UTC-7, Jose Luis Ledesma wrote: The node classifier command is launched by the same user the runs puppet master, and normally it is the 'puppet' user. You should try running the node classifier command in the puppet master with the same user it runs. Regards El 12/07/2014 13:52, Taylor Leese tlee...@gmail.com escribió: I probably also should have mentioned I am using Ubuntu 14 and this is running locally via Vagrant and the Vagrant agent provisioner. I've tried running the puppet agent manually after the Vagrant provisioning fails and I receive the same error message. Jose - When you say the command what do you mean? The node classifier? My VM doesn't have a puppet user so I checked to see what user the agent was running under and it is root. root@nexus:/home/vagrant# ps -ef | grep puppet root 1480 1 0 11:01 ?00:00:01 /usr/bin/ruby /usr/bin/ *puppet* agent - Taylor On Saturday, July 12, 2014 4:41:16 AM UTC-7, Jose Luis Ledesma wrote: Have you tried to run the command with the same user the puppet master is running? (Usually puppet) Regards, El 12/07/2014 13:39, Taylor Leese tlee...@gmail.com escribió: Hi all, I'm trying to setup an external node classifier and I'm running into an error that I haven't been able to resolve. *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node puppet.myhost.com http://puppet.myhost.com: Failed to find puppet.myhost.com http://puppet.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier puppet.myhost.com http://puppet.myhost.com' returned 1: * This is the relevant part of my puppet.conf: *node_terminus = exec* *external_nodes = /etc/puppet/bin/node_classifier* The interesting thing is that if I run the classifier manually I get what appears (to me) to be correct output. I'm using Puppet 3.4.3. Any idea what I might be doing wrong? *root@puppet:/etc/puppet# ./bin/node_classifier puppet.myhost.com http://puppet.myhost.com* *--- * * classes: * *- apt* *- common* *- ntp* *- puppet* *- sudo* *- users* * parameters: * *puppetserver: puppet.myhost.com http://puppet.myhost.com* * environment: production* *root@puppet:/etc/puppet# * - Taylor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e% 40googlegroups.com https://groups.google.com/d/msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message
[Puppet Users] Failed to find [host] via exec
Hi all, I'm trying to setup an external node classifier and I'm running into an error that I haven't been able to resolve. *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node puppet.myhost.com: Failed to find puppet.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier puppet.myhost.com' returned 1: * This is the relevant part of my puppet.conf: *node_terminus = exec* *external_nodes = /etc/puppet/bin/node_classifier* The interesting thing is that if I run the classifier manually I get what appears (to me) to be correct output. I'm using Puppet 3.4.3. Any idea what I might be doing wrong? *root@puppet:/etc/puppet# ./bin/node_classifier puppet.myhost.com* *--- * * classes: * *- apt* *- common* *- ntp* *- puppet* *- sudo* *- users* * parameters: * *puppetserver: puppet.myhost.com* * environment: production* *root@puppet:/etc/puppet# * - Taylor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Failed to find [host] via exec
I probably also should have mentioned I am using Ubuntu 14 and this is running locally via Vagrant and the Vagrant agent provisioner. I've tried running the puppet agent manually after the Vagrant provisioning fails and I receive the same error message. Jose - When you say the command what do you mean? The node classifier? My VM doesn't have a puppet user so I checked to see what user the agent was running under and it is root. root@nexus:/home/vagrant# ps -ef | grep puppet root 1480 1 0 11:01 ?00:00:01 /usr/bin/ruby /usr/bin/ *puppet* agent - Taylor On Saturday, July 12, 2014 4:41:16 AM UTC-7, Jose Luis Ledesma wrote: Have you tried to run the command with the same user the puppet master is running? (Usually puppet) Regards, El 12/07/2014 13:39, Taylor Leese tlee...@gmail.com javascript: escribió: Hi all, I'm trying to setup an external node classifier and I'm running into an error that I haven't been able to resolve. *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node puppet.myhost.com http://puppet.myhost.com: Failed to find puppet.myhost.com http://puppet.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier puppet.myhost.com http://puppet.myhost.com' returned 1: * This is the relevant part of my puppet.conf: *node_terminus = exec* *external_nodes = /etc/puppet/bin/node_classifier* The interesting thing is that if I run the classifier manually I get what appears (to me) to be correct output. I'm using Puppet 3.4.3. Any idea what I might be doing wrong? *root@puppet:/etc/puppet# ./bin/node_classifier puppet.myhost.com http://puppet.myhost.com* *--- * * classes: * *- apt* *- common* *- ntp* *- puppet* *- sudo* *- users* * parameters: * *puppetserver: puppet.myhost.com http://puppet.myhost.com* * environment: production* *root@puppet:/etc/puppet# * - Taylor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Failed to find [host] via exec
Jose - Ah, the puppet master itself is running as the puppet user. *root@puppet:/etc/puppet# ps -ef | grep puppet* *root 1362 1 0 10:55 ?00:00:02 /usr/bin/ruby /usr/bin/puppet agent* *puppet 20719 1 0 11:31 ?00:00:00 Passenger RackApp: /usr/share/puppet/rack/puppetmasterd* I tried the following and got an error: *root@puppet:/etc/puppet# sudo -u puppet ./bin/node_classifier * */usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `open': Permission denied - /root/.facter/facts.d (Errno::EACCES)* I'm not sure if this is really indicative of the actual problem or not. - Taylor On Saturday, July 12, 2014 4:54:22 AM UTC-7, Jose Luis Ledesma wrote: The node classifier command is launched by the same user the runs puppet master, and normally it is the 'puppet' user. You should try running the node classifier command in the puppet master with the same user it runs. Regards El 12/07/2014 13:52, Taylor Leese tlee...@gmail.com javascript: escribió: I probably also should have mentioned I am using Ubuntu 14 and this is running locally via Vagrant and the Vagrant agent provisioner. I've tried running the puppet agent manually after the Vagrant provisioning fails and I receive the same error message. Jose - When you say the command what do you mean? The node classifier? My VM doesn't have a puppet user so I checked to see what user the agent was running under and it is root. root@nexus:/home/vagrant# ps -ef | grep puppet root 1480 1 0 11:01 ?00:00:01 /usr/bin/ruby /usr/bin/ *puppet* agent - Taylor On Saturday, July 12, 2014 4:41:16 AM UTC-7, Jose Luis Ledesma wrote: Have you tried to run the command with the same user the puppet master is running? (Usually puppet) Regards, El 12/07/2014 13:39, Taylor Leese tlee...@gmail.com escribió: Hi all, I'm trying to setup an external node classifier and I'm running into an error that I haven't been able to resolve. *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node puppet.myhost.com http://puppet.myhost.com: Failed to find puppet.myhost.com http://puppet.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier puppet.myhost.com http://puppet.myhost.com' returned 1: * This is the relevant part of my puppet.conf: *node_terminus = exec* *external_nodes = /etc/puppet/bin/node_classifier* The interesting thing is that if I run the classifier manually I get what appears (to me) to be correct output. I'm using Puppet 3.4.3. Any idea what I might be doing wrong? *root@puppet:/etc/puppet# ./bin/node_classifier puppet.myhost.com http://puppet.myhost.com* *--- * * classes: * *- apt* *- common* *- ntp* *- puppet* *- sudo* *- users* * parameters: * *puppetserver: puppet.myhost.com http://puppet.myhost.com* * environment: production* *root@puppet:/etc/puppet# * - Taylor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e% 40googlegroups.com https://groups.google.com/d/msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/ba0718b4-cd4c-48db-9697-3a6fdba3de2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Failed to find [host] via exec
It's also worth mentioning that even if I chown and chgrp /root/.facter/facts.d to puppet I still receive the same error. That also doesn't seem like it should be the solution. I found two Puppet issues that may be related, but it's not entirely clear if they are exactly the same. https://tickets.puppetlabs.com/browse/FACT-176 https://tickets.puppetlabs.com/browse/PUP-2367 - Taylor On Saturday, July 12, 2014 5:06:22 AM UTC-7, Taylor Leese wrote: Jose - Ah, the puppet master itself is running as the puppet user. *root@puppet:/etc/puppet# ps -ef | grep puppet* *root 1362 1 0 10:55 ?00:00:02 /usr/bin/ruby /usr/bin/puppet agent* *puppet 20719 1 0 11:31 ?00:00:00 Passenger RackApp: /usr/share/puppet/rack/puppetmasterd* I tried the following and got an error: *root@puppet:/etc/puppet# sudo -u puppet ./bin/node_classifier * */usr/lib/ruby/vendor_ruby/facter/util/directory_loader.rb:75:in `open': Permission denied - /root/.facter/facts.d (Errno::EACCES)* I'm not sure if this is really indicative of the actual problem or not. - Taylor On Saturday, July 12, 2014 4:54:22 AM UTC-7, Jose Luis Ledesma wrote: The node classifier command is launched by the same user the runs puppet master, and normally it is the 'puppet' user. You should try running the node classifier command in the puppet master with the same user it runs. Regards El 12/07/2014 13:52, Taylor Leese tlee...@gmail.com escribió: I probably also should have mentioned I am using Ubuntu 14 and this is running locally via Vagrant and the Vagrant agent provisioner. I've tried running the puppet agent manually after the Vagrant provisioning fails and I receive the same error message. Jose - When you say the command what do you mean? The node classifier? My VM doesn't have a puppet user so I checked to see what user the agent was running under and it is root. root@nexus:/home/vagrant# ps -ef | grep puppet root 1480 1 0 11:01 ?00:00:01 /usr/bin/ruby /usr/bin/ *puppet* agent - Taylor On Saturday, July 12, 2014 4:41:16 AM UTC-7, Jose Luis Ledesma wrote: Have you tried to run the command with the same user the puppet master is running? (Usually puppet) Regards, El 12/07/2014 13:39, Taylor Leese tlee...@gmail.com escribió: Hi all, I'm trying to setup an external node classifier and I'm running into an error that I haven't been able to resolve. *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node puppet.myhost.com http://puppet.myhost.com: Failed to find puppet.myhost.com http://puppet.myhost.com via exec: Execution of '/etc/puppet/bin/node_classifier puppet.myhost.com http://puppet.myhost.com' returned 1: * This is the relevant part of my puppet.conf: *node_terminus = exec* *external_nodes = /etc/puppet/bin/node_classifier* The interesting thing is that if I run the classifier manually I get what appears (to me) to be correct output. I'm using Puppet 3.4.3. Any idea what I might be doing wrong? *root@puppet:/etc/puppet# ./bin/node_classifier puppet.myhost.com http://puppet.myhost.com* *--- * * classes: * *- apt* *- common* *- ntp* *- puppet* *- sudo* *- users* * parameters: * *puppetserver: puppet.myhost.com http://puppet.myhost.com* * environment: production* *root@puppet:/etc/puppet# * - Taylor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e% 40googlegroups.com https://groups.google.com/d/msgid/puppet-users/d5056060-42ad-4807-8b47-7c9b204bc94e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/31cd8d4d-54bc-44dd-9ef6-73fc2409829d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cffd7bd8-f482-47a0-925b-398dbd26240d%40googlegroups.com. For more
[Puppet Users] Re: Passenger Problems
You guys hijacked my thread. :-) Any idea about my passenger problems? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passenger Problems
Patrick, I did run across that thread, but the GitHub site specifically says 2.2.5 is known to work (http://github.com/puppetlabs/puppet/tree/ master/ext/rack) which made me suspicious that it was my fault. At this point I guess there is no harm in trying 2.2.11 (or whatever the latest version is). Are people using passenger versions 2.2.5 with success? - Taylor On Oct 26, 10:52 am, Patrick kc7...@gmail.com wrote: On Oct 25, 2010, at 12:50 PM, Taylor Leese wrote: Hi all, I'm new to Puppet and I'm trying to setup a puppet master and a client on Amazon EC2 using Passenger. I've gone through the steps described here (http://docs.puppetlabs.com/guides/passenger.html) and here (http://github.com/puppetlabs/puppet/tree/master/ext/rack). However, I am still having some issues. My Environment: * Amazon EC2 * Puppet 2.6.1 * Passenger 2.2.5 Issue #1: From the puppet master node you can see below that passenger is running. However, when I run passenger-status it says that it's not running? Why? r...@ip-10-162-214-xxx:/var/log/apache2# ps -ef | grep passenger root 17327 17314 0 19:37 ? 00:00:00 /var/lib/gems/1.8/gems/ passenger-2.2.5/ext/apache2/ApplicationPoolServerExecutable 0 /var/lib/ gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server /usr/bin/ ruby1.8 /tmp/passenger.17294 root 17422 13196 0 19:38 pts/0 00:00:00 grep --color=auto passenger r...@ip-10-162-214-xxx:/var/log/apache2# passenger-status ERROR: Phusion Passenger doesn't seem to be running. r...@ip-10-162-214-xxx:/var/log/apache2# What distro are you using? A google search for that got me this message. Any chance it's applicable? Message at:http://markmail.org/message/wdue4jfvqdjponha Quoted below: On Sun, Mar 28, 2010 at 8:50 PM, zdennis zach...@gmail.com wrote: We had a production site which was running on Passenger 2.2.5 and ruby- enterprise-1.8.6-20080810. It's been running this combination for the past several months without issue. Today, the application went down with the error: uninitialized constant PhusionPassenger::Utils::PseudoIO::StringIO Upgrade to 2.2.11. This bug has been fixed months ago. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passenger Problems
Patrick, Any idea if people are using versions 2.2.5 in the wild successfully? I tried to revert back to 2.2.2 previously, but I received a number of compilation errors when running passenger-install- apache2-module so it seems like moving up may be my only option. - Taylor On Oct 26, 12:50 pm, Patrick kc7...@gmail.com wrote: The reason I though it might be the problem is because a lot of people are saying that they got that error after it worked for months. This says to me that their might have been a change to something else that makes 2.2.5 stop working. On Oct 26, 2010, at 10:59 AM, Taylor Leese wrote: Patrick, I did run across that thread, but the GitHub site specifically says 2.2.5 is known to work (http://github.com/puppetlabs/puppet/tree/ master/ext/rack) which made me suspicious that it was my fault. At this point I guess there is no harm in trying 2.2.11 (or whatever the latest version is). Are people using passenger versions 2.2.5 with success? - Taylor On Oct 26, 10:52 am, Patrick kc7...@gmail.com wrote: On Oct 25, 2010, at 12:50 PM, Taylor Leese wrote: Hi all, I'm new to Puppet and I'm trying to setup a puppet master and a client on Amazon EC2 using Passenger. I've gone through the steps described here (http://docs.puppetlabs.com/guides/passenger.html) and here (http://github.com/puppetlabs/puppet/tree/master/ext/rack). However, I am still having some issues. My Environment: * Amazon EC2 * Puppet 2.6.1 * Passenger 2.2.5 Issue #1: From the puppet master node you can see below that passenger is running. However, when I run passenger-status it says that it's not running? Why? r...@ip-10-162-214-xxx:/var/log/apache2# ps -ef | grep passenger root 17327 17314 0 19:37 ? 00:00:00 /var/lib/gems/1.8/gems/ passenger-2.2.5/ext/apache2/ApplicationPoolServerExecutable 0 /var/lib/ gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server /usr/bin/ ruby1.8 /tmp/passenger.17294 root 17422 13196 0 19:38 pts/0 00:00:00 grep --color=auto passenger r...@ip-10-162-214-xxx:/var/log/apache2# passenger-status ERROR: Phusion Passenger doesn't seem to be running. r...@ip-10-162-214-xxx:/var/log/apache2# What distro are you using? A google search for that got me this message. Any chance it's applicable? Message at:http://markmail.org/message/wdue4jfvqdjponha Quoted below: On Sun, Mar 28, 2010 at 8:50 PM, zdennis zach...@gmail.com wrote: We had a production site which was running on Passenger 2.2.5 and ruby- enterprise-1.8.6-20080810. It's been running this combination for the past several months without issue. Today, the application went down with the error: uninitialized constant PhusionPassenger::Utils::PseudoIO::StringIO Upgrade to 2.2.11. This bug has been fixed months ago. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passenger Problems
Patrick, Any idea if people are using versions 2.2.5 in the wild successfully? I tried to revert back to 2.2.2 previously, but I received a number of compilation errors when running passenger-install- apache2-module so it seems like moving up may be my only option. - Taylor On Oct 26, 12:50 pm, Patrick kc7...@gmail.com wrote: The reason I though it might be the problem is because a lot of people are saying that they got that error after it worked for months. This says to me that their might have been a change to something else that makes 2.2.5 stop working. On Oct 26, 2010, at 10:59 AM, Taylor Leese wrote: Patrick, I did run across that thread, but the GitHub site specifically says 2.2.5 is known to work (http://github.com/puppetlabs/puppet/tree/ master/ext/rack) which made me suspicious that it was my fault. At this point I guess there is no harm in trying 2.2.11 (or whatever the latest version is). Are people using passenger versions 2.2.5 with success? - Taylor On Oct 26, 10:52 am, Patrick kc7...@gmail.com wrote: On Oct 25, 2010, at 12:50 PM, Taylor Leese wrote: Hi all, I'm new to Puppet and I'm trying to setup a puppet master and a client on Amazon EC2 using Passenger. I've gone through the steps described here (http://docs.puppetlabs.com/guides/passenger.html) and here (http://github.com/puppetlabs/puppet/tree/master/ext/rack). However, I am still having some issues. My Environment: * Amazon EC2 * Puppet 2.6.1 * Passenger 2.2.5 Issue #1: From the puppet master node you can see below that passenger is running. However, when I run passenger-status it says that it's not running? Why? r...@ip-10-162-214-xxx:/var/log/apache2# ps -ef | grep passenger root 17327 17314 0 19:37 ? 00:00:00 /var/lib/gems/1.8/gems/ passenger-2.2.5/ext/apache2/ApplicationPoolServerExecutable 0 /var/lib/ gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server /usr/bin/ ruby1.8 /tmp/passenger.17294 root 17422 13196 0 19:38 pts/0 00:00:00 grep --color=auto passenger r...@ip-10-162-214-xxx:/var/log/apache2# passenger-status ERROR: Phusion Passenger doesn't seem to be running. r...@ip-10-162-214-xxx:/var/log/apache2# What distro are you using? A google search for that got me this message. Any chance it's applicable? Message at:http://markmail.org/message/wdue4jfvqdjponha Quoted below: On Sun, Mar 28, 2010 at 8:50 PM, zdennis zach...@gmail.com wrote: We had a production site which was running on Passenger 2.2.5 and ruby- enterprise-1.8.6-20080810. It's been running this combination for the past several months without issue. Today, the application went down with the error: uninitialized constant PhusionPassenger::Utils::PseudoIO::StringIO Upgrade to 2.2.11. This bug has been fixed months ago. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passenger Problems
@Patrick - Thanks. I will try a newer version of passenger later tonight. @Ohad - I'm actually using Ubuntu Maverick. On Oct 26, 1:11 pm, Patrick kc7...@gmail.com wrote: On Oct 26, 2010, at 1:00 PM, Taylor Leese wrote: Patrick, Any idea if people are using versions 2.2.5 in the wild successfully? I tried to revert back to 2.2.2 previously, but I received a number of compilation errors when running passenger-install- apache2-module so it seems like moving up may be my only option. If you want to do more research, it seems to be related to this:http://code.google.com/p/phusion-passenger/issues/detail?id=398 On Oct 26, 12:50 pm, Patrick kc7...@gmail.com wrote: The reason I though it might be the problem is because a lot of people are saying that they got that error after it worked for months. This says to me that their might have been a change to something else that makes 2.2.5 stop working. On Oct 26, 2010, at 10:59 AM, Taylor Leese wrote: Patrick, I did run across that thread, but the GitHub site specifically says 2.2.5 is known to work (http://github.com/puppetlabs/puppet/tree/ master/ext/rack) which made me suspicious that it was my fault. At this point I guess there is no harm in trying 2.2.11 (or whatever the latest version is). Are people using passenger versions 2.2.5 with success? - Taylor On Oct 26, 10:52 am, Patrick kc7...@gmail.com wrote: On Oct 25, 2010, at 12:50 PM, Taylor Leese wrote: Hi all, I'm new to Puppet and I'm trying to setup a puppet master and a client on Amazon EC2 using Passenger. I've gone through the steps described here (http://docs.puppetlabs.com/guides/passenger.html) and here (http://github.com/puppetlabs/puppet/tree/master/ext/rack). However, I am still having some issues. My Environment: * Amazon EC2 * Puppet 2.6.1 * Passenger 2.2.5 Issue #1: From the puppet master node you can see below that passenger is running. However, when I run passenger-status it says that it's not running? Why? r...@ip-10-162-214-xxx:/var/log/apache2# ps -ef | grep passenger root 17327 17314 0 19:37 ? 00:00:00 /var/lib/gems/1.8/gems/ passenger-2.2.5/ext/apache2/ApplicationPoolServerExecutable 0 /var/lib/ gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server /usr/bin/ ruby1.8 /tmp/passenger.17294 root 17422 13196 0 19:38 pts/0 00:00:00 grep --color=auto passenger r...@ip-10-162-214-xxx:/var/log/apache2# passenger-status ERROR: Phusion Passenger doesn't seem to be running. r...@ip-10-162-214-xxx:/var/log/apache2# What distro are you using? A google search for that got me this message. Any chance it's applicable? Message at:http://markmail.org/message/wdue4jfvqdjponha Quoted below: On Sun, Mar 28, 2010 at 8:50 PM, zdennis zach...@gmail.com wrote: We had a production site which was running on Passenger 2.2.5 and ruby- enterprise-1.8.6-20080810. It's been running this combination for the past several months without issue. Today, the application went down with the error: uninitialized constant PhusionPassenger::Utils::PseudoIO::StringIO Upgrade to 2.2.11. This bug has been fixed months ago. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passenger Problems
Mathias - Really? That's awesome. I didn't realize that existed. I will check it out. Thanks. On Oct 26, 1:38 pm, Mathias Gug math...@ubuntu.com wrote: Hi, Excerpts from Taylor Leese's message of Tue Oct 26 16:31:04 -0400 2010: @Ohad - I'm actually using Ubuntu Maverick. If you're using Ubuntu Maverick I'd highly recommend to use the puppetmaster-passenger package. It will automatically install and setup a puppet master running under apache2 and passenger. No further configuration is required. -- Mathias Gug Ubuntu Developer http://www.ubuntu.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Passenger Problems
Mathias - The package you mentioned (puppetmaster-passenger) worked perfectly for me on the first try. That saved me a ton of time. Thanks! On Oct 26, 1:38 pm, Mathias Gug math...@ubuntu.com wrote: Hi, Excerpts from Taylor Leese's message of Tue Oct 26 16:31:04 -0400 2010: @Ohad - I'm actually using Ubuntu Maverick. If you're using Ubuntu Maverick I'd highly recommend to use the puppetmaster-passenger package. It will automatically install and setup a puppet master running under apache2 and passenger. No further configuration is required. -- Mathias Gug Ubuntu Developer http://www.ubuntu.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Passenger Problems
Hi all, I'm new to Puppet and I'm trying to setup a puppet master and a client on Amazon EC2 using Passenger. I've gone through the steps described here (http://docs.puppetlabs.com/guides/passenger.html) and here (http://github.com/puppetlabs/puppet/tree/master/ext/rack). However, I am still having some issues. My Environment: * Amazon EC2 * Puppet 2.6.1 * Passenger 2.2.5 Issue #1: From the puppet master node you can see below that passenger is running. However, when I run passenger-status it says that it's not running? Why? r...@ip-10-162-214-xxx:/var/log/apache2# ps -ef | grep passenger root 17327 17314 0 19:37 ?00:00:00 /var/lib/gems/1.8/gems/ passenger-2.2.5/ext/apache2/ApplicationPoolServerExecutable 0 /var/lib/ gems/1.8/gems/passenger-2.2.5/bin/passenger-spawn-server /usr/bin/ ruby1.8 /tmp/passenger.17294 root 17422 13196 0 19:38 pts/000:00:00 grep --color=auto passenger r...@ip-10-162-214-xxx:/var/log/apache2# passenger-status ERROR: Phusion Passenger doesn't seem to be running. r...@ip-10-162-214-xxx:/var/log/apache2# Issue #2: From the puppet client I execute puppetd --waitforcert 60 --test and receive below: r...@ip-10-161-106-xxx:/etc/puppet# puppetd --waitforcert 60 --test notice: Ignoring --listen on onetime run err: Could not retrieve catalog from remote server: Error 500 on SERVER: However, this gives the 500 above and in the puppet master's apache2 error.log I see below. [Mon Oct 25 19:37:02 2010] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] [Mon Oct 25 19:37:02 2010] [notice] Apache/2.2.16 (Ubuntu) Phusion_Passenger/2.2.5 mod_ssl/2.2.16 OpenSSL/0.9.8o configured -- resuming normal operations *** Exception NameError in PhusionPassenger::Rack::ApplicationSpawner (uninitialized constant PhusionPassenger::Utils::PseudoIO::StringIO) (process 17328): from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/utils.rb:207:in `initialize' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/utils.rb:248:in `new' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/utils.rb:248:in `report_app_init_status' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/rack/application_spawner.rb:91:in `run' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/rack/application_spawner.rb:69:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/utils.rb:183:in `safe_fork' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/rack/application_spawner.rb:62:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/rack/application_spawner.rb:45:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/spawn_manager.rb:159:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/abstract_server.rb:352:in `__send__' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/abstract_server.rb:352:in `main_loop' from /var/lib/gems/1.8/gems/passenger-2.2.5/lib/ phusion_passenger/abstract_server.rb:196:in `start_synchronously' from /var/lib/gems/1.8/gems/passenger-2.2.5/bin/passenger- spawn-server:61 Any idea(s) how to fix these two issues and what I'm doing wrong? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
