I''m sure it must already be a known bug, but I''ve been getting this message frequently on the clients: Could not retrieve catalog from remote server: Could not intern from pson: source did not contain any PSON! Happens erratically but it''s frequency seems to have increased with my upgrade from 2.6.3 to 2.6.4. Getting rather sick of it because I have to restart the client multiple times to get it to stop. Doug. -- 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.
Hi doug, I''ve been getting this as well , someone suggested searching the entire filesystem on the client for a directory called .puppet and delete any found. I haven''t tried this yet though On Mar 3, 2:36 pm, Douglas Garstang <doug.garst...@gmail.com> wrote:> I''m sure it must already be a known bug, but I''ve been getting this message > frequently on the clients: > > Could not retrieve catalog from remote server: Could not intern from pson: > source did not contain any PSON! > > Happens erratically but it''s frequency seems to have increased with my > upgrade from 2.6.3 to 2.6.4. Getting rather sick of it because I have to > restart the client multiple times to get it to stop. > > Doug.-- 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.
Sorry Jed I didn''t realise that you didn''t know about .puppet directories. A .puppet directory is created in your home directory if you accidentally run puppet as yourself and not as root. The problem that I had was that sometimes puppetd was correctly reading SSL settings from /var/lib/puppet/ssl and sometimes from ~/.puppet/ssl (I started puppet sudo''ed from my account). But I don''t think that this is Douglas'' problem as he is only getting his error occasionally whereas mine was happening once every three or four runs at the beginning and then increased in frequency. But still my experience might help a bit as I found that, at least in my case, no PSON meant actually meant no content at all was fetched from the puppetmaster. And the place to look to see if that is the case is the web server log on the master (in /var/log/puppet or whatever). I hope that this helps. On Mar 4, 4:55 am, Jed <jedbl...@gmail.com> wrote:> Hi doug, I''ve been getting this as well , someone suggested searching > the entire filesystem on the client for a directory called .puppet and > delete any found. I haven''t tried this yet though > > On Mar 3, 2:36 pm, Douglas Garstang <doug.garst...@gmail.com> wrote: > > > > > I''m sure it must already be a known bug, but I''ve been getting this message > > frequently on the clients: > > > Could not retrieve catalog from remote server: Could not intern from pson: > > source did not contain any PSON! > > > Happens erratically but it''s frequency seems to have increased with my > > upgrade from 2.6.3 to 2.6.4. Getting rather sick of it because I have to > > restart the client multiple times to get it to stop. > > > Doug.-- 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.
Bill Proud wrote:> Sorry Jed I didn''t realise that you didn''t know about .puppet > directories. A .puppet directory is created in your home directory if > you accidentally run puppet as yourself and not as root. The problem > that I had was that sometimes puppetd was correctly reading SSL > settings from /var/lib/puppet/ssl and sometimes from ~/.puppet/ssl (I > started puppet sudo''ed from my account). > > But I don''t think that this is Douglas'' problem as he is only getting > his error occasionally whereas mine was happening once every three or > four runs at the beginning and then increased in frequency. But still > my experience might help a bit as I found that, at least in my case, > no PSON meant actually meant no content at all was fetched from the > puppetmaster. And the place to look to see if that is the case is the > web server log on the master (in /var/log/puppet or whatever).Check the /var/log/puppet/masterhttp.log. Regards James Turnbull -- James Turnbull Puppet Labs 1-503-734-8571 -- 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.
On Fri, Mar 4, 2011 at 9:31 AM, James Turnbull <james@puppetlabs.com> wrote:> Bill Proud wrote: > > Sorry Jed I didn''t realise that you didn''t know about .puppet > > directories. A .puppet directory is created in your home directory if > > you accidentally run puppet as yourself and not as root. The problem > > that I had was that sometimes puppetd was correctly reading SSL > > settings from /var/lib/puppet/ssl and sometimes from ~/.puppet/ssl (I > > started puppet sudo''ed from my account). > > > > But I don''t think that this is Douglas'' problem as he is only getting > > his error occasionally whereas mine was happening once every three or > > four runs at the beginning and then increased in frequency. But still > > my experience might help a bit as I found that, at least in my case, > > no PSON meant actually meant no content at all was fetched from the > > puppetmaster. And the place to look to see if that is the case is the > > web server log on the master (in /var/log/puppet or whatever). > > Check the /var/log/puppet/masterhttp.log. > >Okidoki..... below is what appeared in the masterhttp.log file when this client tried to connect. [2011-03-06 06:46:34] ERROR OpenSSL::SSL::SSLError: SSL_write:: internal error /usr/lib/ruby/1.8/openssl/buffering.rb:178:in `syswrite'' /usr/lib/ruby/1.8/openssl/buffering.rb:178:in `do_write'' /usr/lib/ruby/1.8/openssl/buffering.rb:197:in `<<'' /usr/lib/ruby/1.8/webrick/httpresponse.rb:324:in `_write_data'' /usr/lib/ruby/1.8/webrick/httpresponse.rb:296:in `send_body_string'' /usr/lib/ruby/1.8/webrick/httpresponse.rb:187:in `send_body'' /usr/lib/ruby/1.8/webrick/httpresponse.rb:104:in `send_response'' /usr/lib/ruby/1.8/webrick/httpserver.rb:79:in `run'' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:45:in `listen'' /usr/lib/ruby/1.8/webrick/server.rb:173:in `call'' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start'' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start'' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each'' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start'' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in `listen'' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `initialize'' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `new'' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `listen'' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize'' /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `listen'' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:127:in `listen'' /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:142:in `start'' /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start'' /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:114:in `main'' /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:46:in `run_command'' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:287:in `run'' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:393:in `exit_on_fail'' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:287:in `run'' /usr/sbin/puppetmasterd:4[2011-03-06 06:46:34] qa-app02.fre.livegamer.com - - [06/Mar/2011:06:46:30 GMT] "GET /prod_current/catalog/ qa-app02.fre.livegamer.com?facts_format=b64_zlib_yaml& .... followed by a lot more stuff... Does that shine any light on the issue? Doug. -- 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.
SSL_write is the function that writes to an SSL connection. Evidently in this case there was an error - perhaps the connection was lost. Bill> Okidoki..... below is what appeared in the masterhttp.log file when this > client tried to connect. > > [2011-03-06 06:46:34] ERROR OpenSSL::SSL::SSLError: SSL_write:: internal > error /usr/lib/ruby/1.8/openssl/buffering.rb:178:in `syswrite''-- 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.
On Sun, Mar 6, 2011 at 2:48 AM, Bill Proud <billproud@yahoo.com> wrote:> SSL_write is the function that writes to an SSL connection. Evidently > in this case there was an error - perhaps the connection was lost. > >This error is occurring on multiple clients at regular intervals in a new data centre, sometimes on VM''s that are on the same physical hardware as the puppetmaster. That seems very unlikely. Doug. -- 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.
Trouble is that there isn''t a lot more information here. Is it always the same error? Actually you might have the same .puppet directory problem that I had but it would have to be in the home directory of whoever last started puppetmasterd (so not on the client). On Mar 6, 8:01 pm, Douglas Garstang <doug.garst...@gmail.com> wrote:> On Sun, Mar 6, 2011 at 2:48 AM, Bill Proud <billpr...@yahoo.com> wrote: > > SSL_write is the function that writes to an SSL connection. Evidently > > in this case there was an error - perhaps the connection was lost. > > This error is occurring on multiple clients at regular intervals in a new > data centre, sometimes on VM''s that are on the same physical hardware as the > puppetmaster. That seems very unlikely. > > Doug.-- 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.
Actually... we have two puppet masters on two different servers. Both are sourcing their /etc/puppet from the same working copy, and clients connecting to both puppet masters are displaying this PSON message. Also, it isn''t the .puppet directory problem. A ''find . -name .puppet'' on both puppetmasters returned no files. Given that it''s reproducable across two puppet masters, it would seem to indicate to me that it''s a bug with the puppet master (2.6.4), or Webrick (1.3.1), ruby (1.8.5). Doug. On Sun, Mar 6, 2011 at 11:11 AM, Bill Proud <billproud@yahoo.com> wrote:> Trouble is that there isn''t a lot more information here. Is it always > the same error? > > Actually you might have the same .puppet directory problem that I had > but it would have to be in the home directory of whoever last started > puppetmasterd (so not on the client). > > On Mar 6, 8:01 pm, Douglas Garstang <doug.garst...@gmail.com> wrote: > > On Sun, Mar 6, 2011 at 2:48 AM, Bill Proud <billpr...@yahoo.com> wrote: > > > SSL_write is the function that writes to an SSL connection. Evidently > > > in this case there was an error - perhaps the connection was lost. > > > > This error is occurring on multiple clients at regular intervals in a new > > data centre, sometimes on VM''s that are on the same physical hardware as > the > > puppetmaster. That seems very unlikely. > > > > Doug. > > -- > 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. > >-- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garstang@gmail.com Cell: +1-805-340-5627 -- 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.