Hello,
I'm migrating my test master server to 0.25.1.
It works fine at this time with the following elements:
- ruby enterprise edition
- puppet-server (from sources) 0.25.1
- passenger 2.2.7
- httpd 2.2.3
All on a 64bit RHEL5-like distro.
As I have more than one master server, I plan to use a proxy-balancer on
top of passenger in order to balance the load over the machines.
So I created a balancer configuration for apache, on port 8140, and
moved the passenger configuration to port 8141.
The proxy-balancer owns only one "worker", the passenger port:
<Proxy balancer://puppetmaster>
BalancerMember http://localhost:8141
</Proxy>
If I run my client on port 8141 (directly on passenger) it works fine.
If I run my client on port 8140 I get strange result:
# puppetd --test
info: Loading facts in (...)
(...the list of facts...)
Could not run: Puppet::Resource::Catalog does not respond to from_s; can
not intern instances from text/plain
info: Loading facts in (...)
(...the list of facts...)
Could not run: Puppet::Resource::Catalog does not respond to from_s; can
not intern instances from text/plain
info: Loading facts in (...)
(...the list of facts...)
Could not run: Puppet::Resource::Catalog does not respond to from_s; can
not intern instances from text/plain
#
It is printed 3 times per run.
Is it a known problem to use a proxy-balancer in front of passenger?
I can join the apache config files if needed, but the passenger one
works fine alone, and the complete proxy-balancer one is the same than I
used previously with mongrel, which works fine to handle load-balancing
over my 3 master servers (I mean, it have all the SSL stuff in it).
Thanks for any help.
--
Yannick
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
