Hey John 
Did you get into bottom of this?

I am having similar issue, works fine with webrick...running with passenger 
will throw Error: Could not retrieve catalog from remote server: Error 400 
on SERVER: Could not find class errror.

Thanks
Suman

On Tuesday, 8 April 2014 07:29:24 UTC+10, John Pyeatt wrote:
>
> Tried to convert from webrick to passenger today. Failed.
>
> When I run
>
> puppet agent -tv
>
> I get two things that are troubling.
>
> 1)
> I get this message:
> Notice: with older puppet master. To remove this notice, please upgrade 
> your master(s) 
> Notice: to Puppet 3.3 or newer.
>
> Even though in my webrick days we are running puppet 3.4 on the 
> puppetmaster.
>
> 2)
> I also get these messages.
>
> Warning: Local environment: "dev" doesn't match server specified node 
> environment "production", switching agent to "production".
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Could not find class bastion for 10.0.11.83 on node 
>
> My /etc/puppet/puppet.conf is configured correctly because it was working 
> in the webbrick world. Additionally, I know it is getting some information 
> from my  puppet.conf file because it is correctly executing my ENC script 
> defined in external_nodes=
>
> It just doesn't seem to be recognizing my extra modulepath= and manifest= 
> values for my [dev] stanza. I've checked file/directory permissions and the 
> apache user www-data has read permissions to those directories.
>
> Any ideas???
> -- 
> John Pyeatt
> Singlewire Software, LLC
> www.singlewire.com
> ------------------
> 608.661.1184
> [email protected] <javascript:> 
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/383b2d3c-7f70-4197-b8bb-f77f7d27c730%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to