Downgrade to 3.5.1 since last message and running without problems.
El jueves, 29 de mayo de 2014 14:22:51 UTC+2, Adrián López Tejedor escribió:
>
> I am having the same problem but I only have uppet-server-3.6.1, without
> passenger, dashboard, etc.
> It works correctly for 10' more or less, then start to give errors like:
>
> May 29 14:15:21 HOSTNAME puppet-master[30831]: no 'environments' in
> {:root_environment=>#<Puppet::Node::Environment:0x7f654f667018
> @config_version=nil, @manifest="/etc/puppet", @name=:"*root*",
> @modulepath=[], @watching=true>,
> :current_environment=>#<Puppet::Node::Environment:0x7f654f667018
> @config_version=nil, @manifest="/etc/puppet", @name=:"*root*",
> @modulepath=[], @watching=true>} at top of [[0, nil, nil]]
>
> El viernes, 9 de mayo de 2014 11:27:43 UTC+2, Luca Mazzaferro escribió:
>>
>> Hi again,
>> problem solved.
>> I re-installed also the puppet-dashboard following official information
>> here:
>>
>>
>> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#installing-from-git
>>
>> There is an error on the provided *dashboard-vhost.conf*:
>> there variable
>>
>> *RailsAutoDetect*
>>
>> is not supported since passenger 4.0.0
>>
>>
>> http://www.modrails.com/documentation/Users%20guide%20Apache.html#_railsautodetect_rackautodetect_and_wsgiautodetect
>>
>> I used instead
>> PassengerEnabled On
>>
>> Cheers and good luck.
>>
>> Luca
>>
>> Il giorno venerdì 9 maggio 2014 09:51:10 UTC+2, Luca Mazzaferro ha
>> scritto:
>>>
>>>
>>> Hi,
>>> thank you for this suggestion.
>>> Probably you are right, indeed; the problem should be there.
>>> Actually the Puppet-Passenger system is working again what I did on my
>>> SL6 is:
>>>
>>> Update the rack and passenger from the version passenger-4.0.41
>>> to passenger-4.0.42
>>> gem install rack passenger
>>> run again the passenger module installation command for apache2.
>>> passenger-install-apache2-module
>>>
>>> These two actions didn't solve the situation but when I copied again the
>>> config.ru
>>>
>>> cp /usr/share/puppet/ext/rack/config.ru/usr/share/puppet/rack/puppetmasterd/
>>>
>>> it starts to work again.
>>>
>>> What I guess is this: the Dashboard installation in some way rewrote the
>>> config.ru and create the problem.
>>> I will try to install it again making a bkp copy of config.ru before.
>>>
>>> Is it possible? Anyone experienced something like this?
>>> I'll keep you updated.
>>> Cheers.
>>>
>>>
>>> Il giorno giovedì 8 maggio 2014 20:45:21 UTC+2, [email protected] ha
>>> scritto:
>>>>
>>>> Check your config.ru and make sure it is correct and in the right
>>>> location. I had an old one from Foreman there and that was breaking the
>>>> system apparently.
>>>>
>>>
--
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/f69e4766-9344-4f79-ad64-619962da8092%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
