What is "Could not intern from pson" error??

[Sans]

Dear all,
I'm getting this really annoying problem, where it's being failed intermittently. The errors I'm getting are like this:

err: Could not retrieve catalog from remote server: Could not intern from pson: unexpected token in object at '"li'!
err: Could not retrieve catalog from remote server: Could not intern from pson: unexpected token in object at '"file'!
err: Could not retrieve catalog from remote server: Could not intern from pson: expected value in object at '"p'!

If I keep trying over and over again (at least 4/5 times), at one point it successfully runs; so I don't think there is actually any fault in the code itself. does any one know why am I seeing this? Cheers!!

[Sans]

Hi there,
 
Does anyone have any idea at all what's I'm doing wrong? I just have suddenly started seeing this since yesterday morning. Any help will be appreciated. Cheers!!

[Denmat]

Hi,

Can you describe your setup a bit more for us? Versions, distros, apache/passenger, that kind of thing.

You could try running puppetmaster in the foreground and see if that helps you get closer to a solution. 

puppet master --no-daemonize --verbose (or --debug)

Then get a client to poll in. (command syntax above my vary depending on your version of puppet and will depend on your setup too).

THT

Den

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/cVeFux-I3XEJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

[Sans]

Hi Den,

My puppetmaster is a SL6 (Scientific Linux v6.2) and all my agents are SL5.4, running puppet-2.7.14 all around. I've seen people talking about apache/passenger stuff but I didn't do any thing extra, so I think. I'm still using WEBrick(??). It was perfectly fine, even the day before yesterday, until I moved my puppetmaster from SL5 to SL6 (with SELinux on). Is there any specific info you are after?

The error reporting is so inconsistent I don't get a clue at all - one agent is fine now and the next moment it throwing in the errors. Thanks for the advise on running puppetmaster in the foreground - trying that now. Cheers!!

To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.

[Bernd Adamowicz]

I cannot help with this problem. But I’m facing the same issue from the very first time I’m using Puppet. It happens only on my Puppet master boxes. I’m running Puppet 2.6.12 on RHEL 5.5. If I can provide more information to help solving this issue, just let me know.

 

Bernd

 

To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WJv61tuf8QQJ.

To post to this group, send email to puppet...@googlegroups.com

.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

For more options, visit this group at

http://groups.google.com/group/puppet-users?hl=en.

[Denmat]

Okay, so how many clients are trying to connect? Webrick doesn't scale well (hence people put it behind apache or nginx).

I see no specific reason that it should behave different under SL 5.x to 6.x. 

Test your clients one at a time and see if it works. If it does then you're coming up against limitations with webrick. If it fails on one or all post your logs for us from client and master.

puppet agent --test --verbose (--debug)

puppet master --no-daemonize --verbose --debug

Cheers,

Den

[Sans]

Thanks Bernd, for your input. At least we are not alone!
The errors are so lame it's hard to debug - run puppet on the same node a few times back to back and every time there was a different message:

[root@farm052 ~]# puppetd -t
info: Retrieving plugin
info: Loading facts in batch_system
info: Loading facts in num_core
[ .... ]
info: Loading facts in dpm_disk
err: Could not retrieve catalog from remote server: Could not intern from pson: unexpected token in array at '"Class[Cvmfs::Servi'!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
#
[root@farm052 ~]# puppetd -t
info: Retrieving plugin
info: Loading facts in batch_system
[ .... ]
info: Loading facts in dpm_disk
err: Could not retrieve catalog from remote server: Could not intern from pson: expected value in object at '"/etc'!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
#
[root@farm052 ~]# puppetd -t
info: Retrieving plugin
info: Loading facts in batch_system
[ .... ]
info: Loading facts in dpm_disk
err: Could not retrieve catalog from remote server: Could not intern from pson: expected value in object at '"C'!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
[root@farm052 ~]# puppetd -t
#
info: Retrieving plugin
info: Loading facts in batch_system
info: Loading facts in num_core
[ .... ]
info: Loading facts in dpm_disk
err: Could not retrieve catalog from remote server: Could not intern from pson: expected value in object at '"--- \n  puppetversi'!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
#
[root@farm052 ~]# puppetd -t
info: Retrieving plugin
info: Loading facts in batch_system
info: Loading facts in num_core
[ .... ]
info: Loading facts in dpm_disk
err: Could not retrieve catalog from remote server: Could not intern from pson: expected value in object at '"/etc/yum.repos'!
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

Completely cluless. Cheers!!

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.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WJv61tuf8QQJ.
To post to this group, send email to puppet...@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.

[Sans]

I've kinda 70 odd nodes but right now it's only three of them are talking to the master. As I mentioned earlier, Puppet was running just fine with all my nodes and setup for nearly a year until day before yesterday when I moved the master to the new SL6 node. This is the log from the puppet-server when it failed on the agent:

[2012-05-07 14:09:52] DEBUG accept: 111.111.111.252:39894
[2012-05-07 14:09:52] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
[2012-05-07 14:09:52] farm052.xxx.xxx.xxx.xx.uk - - [07/May/2012:14:09:52 BST] "GET /production/file_metadatas/plugins?ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage&recurse=true&checksum_type=md5& HTTP/1.1" 200 1823
[2012-05-07 14:09:52] - -> /production/file_metadatas/plugins?ignore=---+%0A++-+.svn%0A++-+CVS%0A++-+.git&links=manage&recurse=true&checksum_type=md5&
[2012-05-07 14:09:52] DEBUG close: 111.111.111.252:39894
[2012-05-07 14:09:56] DEBUG accept: 111.111.111.252:39895
[2012-05-07 14:09:56] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
[2012-05-07 14:09:58] ERROR OpenSSL::SSL::SSLError: SSL_write:: internal error
        /usr/lib/ruby/1.8/openssl/buffering.rb:179:in `syswrite'
        /usr/lib/ruby/1.8/openssl/buffering.rb:179:in `do_write'
        /usr/lib/ruby/1.8/openssl/buffering.rb:198: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/site_ruby/1.8/puppet/network/http/webrick.rb:38: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:126:in `listen'
        /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:141: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:202:in `main'
        /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:144:in `run_command'
        /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
        /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook'
        /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'        /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail'
        /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
        /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute'
        /usr/bin/puppet:4
[2012-05-07 14:09:58] farm052.xxx.xxx.xxx.xx.uk - - [07/May/2012:14:09:56 BST] "POST /production/catalog/farm052.xxx.xxx.
xxx.xx.uk HTTP/1.1" 200 0
[2012-05-07 14:09:58] - -> /production/catalog/farm052.xxx.xxx.xxx.xx.uk
[2012-05-07 14:09:58] DEBUG close: 111.111.111.252:39895
[2012-05-07 14:09:58] DEBUG accept: 111.111.111.252:39896
[2012-05-07 14:09:58] DEBUG Puppet::Network::HTTP::WEBrickREST is invoked.
[2012-05-07 14:09:58] farm052.xxx.xxx.xxx.xx.uk - - [07/May/2012:14:09:58 BST] "PUT /production/report/farm052.xxx.xxx.xxx.xx.uk HTTP/1.1" 200 14
[2012-05-07 14:09:58] - -> /production/report/farm052.xxx.xxx.xxx.xx.uk
[2012-05-07 14:09:58] DEBUG close: 111.111.111.252:39896
[2012-05-07 14:10:12] DEBUG close TCPSocket(0.0.0.0, 8140)
[2012-05-07 14:10:12] INFO  going to shutdown ...
[2012-05-07 14:10:12] INFO  WEBrick::HTTPServer#start done.

I see an "OpenSSL error" in the log. Cheers!!

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.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WJv61tuf8QQJ.
To post to this group, send email to puppet...@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.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.

To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.

[qutic development]

I had this strange error after the first in resolv.conf registered (internal) dns-server died. After a restart of the dns-server the error was gone.

[Sans]

Hi Jerry,

That actually reminds me about something related. I also moved the alias-name from the old server on to th new one and used that alias-name as certname and server in my configuration. Should it be a problem? Any one can comment? Cheers!!

[Sans]

Figured out that the using CNAME is not really the issue but I'm still getting the same error 3 out of 5 or so. If anyone know anything related to this, can you please help? Cheers!!

[Afroz Hussain]

Hi Sans,

Please run the below command once then start running puppet agent -t.. It will fix the issue.
puppet agent --onetime --no-daemonize -v --server "YOUR PUPPET MASTER NAME"

[JS]

Did you ever find a resolution to this?