>
> It turns out that for me at least this problem was caused by using the
> directory /etc/puppet/rack/ as the document root.
> Creating the directory puppetmasterd and moving everything to down a level
> to /etc/puppet/rack/puppetmasterd (paths updated in apache config of
> course), everythin
On 10/26/2010 10:46 PM, Andrew Forgue wrote:
> On Oct 26, 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-
yes, that is the method I had in mind too :)
better be save then sorry
Thanks!
On Tue, Oct 26, 2010 at 4:50 PM, Patrick wrote:
> I love this package, but I had some conflicts with my existing puppetmaster
> configuration. This is what I did (probably very overkill) that fixed all
> the conflict
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 wrote:
> Hi,
>
> Excerpts from Taylor Leese's message of Tue Oct 26 16:31:04 -0400 2010:
>
>
>
> > @Ohad - I'm actually using
I love this package, but I had some conflicts with my existing puppetmaster
configuration. This is what I did (probably very overkill) that fixed all the
conflicts. I haven't had this trouble with new servers. I've only had this
problem with servers that had puppet+passenger configured manual
Mathias,
if the none passenger version was install, what do one need to do to switch
?
apt-get remove and then apt-get install or will a apt-get-install replace
the current none
passenger version?
Thanks
On Tue, Oct 26, 2010 at 1:38 PM, Mathias Gug wrote:
> Hi,
>
> Excerpts from Taylor Leese's
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 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 M
On Oct 26, 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 m
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 apac
@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 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
> > successfu
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
if you are on rhel5, you can use the following rpm -
http://theforeman.org/repo/el5/noarch/rubygem-passenger-2.2.2-1.noarch.rpm
Ohad
On Tue, Oct 26, 2010 at 10:00 PM, Taylor Leese wrote:
> Patrick,
>
> Any idea if people are using versions > 2.2.5 in the wild
> successfully? I tried to revert b
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,
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
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:
> Pat
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)
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-user
On Fri, Dec 26, 2008 at 10:23 AM, Jeff wrote:
> I was trying to follow the passenger howto and while passenger seems
> to be answering properly for the puppetmaster, the puppet clients all
> complain with this error:
>
> Could not describe /files/etc/portage/package.keywords: Wrong content-
> typ
18 matches
Mail list logo
