Interestingly it appears to be the '--profile' that makes it work for me.
The rest are not needed.
On Tuesday, March 25, 2014 at 2:30:27 PM UTC-7, treydock wrote:
>
> I recently moved from manually configured Puppetmaster under passenger to
> fully managed using theforeman/puppet module. Now
Incredible. This made it work for me also.
joi, 12 iunie 2014, 16:47:55 UTC+3, treydock a scris:
>
> Sort of. The normal Puppet+Passenger configuration still crashes, but
> for some odd reason if I add the following to the Puppet config.ru
> (after the --confdir and --vardir lines) the crashes
+1 here.
We see this problem kind of problem on Puppet 3.4.3 and Scientific Linux
6.5.
Only the files causing the segfault are different from your case:
/usr/lib/ruby/site_ruby/1.8/puppet/util/autoload.rb:88: [BUG]
Segmentation fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
/usr/lib/
Sort of. The normal Puppet+Passenger configuration still crashes, but
for some odd reason if I add the following to the Puppet config.ru
(after the --confdir and --vardir lines) the crashes stop...
ARGV << "--debug"
ARGV << "--trace"
ARGV << "--profile"
ARGV << "--logdest" << "/var/log/puppet/pup
Hi Treydock,
Did you ever resolve this problem?
Thanks!
Op dinsdag 25 maart 2014 23:24:17 UTC+1 schreef treydock:
>
> As an update, I tried running 'puppet master --no-daemonize --debug' and
> am seeing a segmentation fault running outside of passenger/apache...
>
> /usr/lib/ruby/site_ruby/1.8/
As an update, I tried running 'puppet master --no-daemonize --debug' and am
seeing a segmentation fault running outside of passenger/apache...
/usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:555: [BUG] Segmentation
fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
/usr/lib/ruby/1
