tag 385230 +unreproducible
tag 385230 +help
thanks
I've seen this in the wild once, but the machine had to be reinstalled and
it hasn't reappeared since on the same hardware/software/etc. David
Schmitt's comment of 10 September doesn't make much sense to me; perhaps it
was a mistyped bug number?
On Thu, Aug 31, 2006 at 05:37:24PM -0400, Brett Viren wrote:
> Okay, getting somewhere!
>
> I noticed that the "rdoc", "rdoc1.8" and "irb1.8" packages were
> installed on the broken system and were missing on the working system.
> Removing irb1.8 also removed the rdoc packages and got the broken
>
Okay, getting somewhere!
I noticed that the "rdoc", "rdoc1.8" and "irb1.8" packages were
installed on the broken system and were missing on the working system.
Removing irb1.8 also removed the rdoc packages and got the broken
system working again.
I then installed just irb1.8 on the previously wo
On Thu, Aug 31, 2006 at 02:09:31PM -0400, Brett Viren wrote:
> Matthew Palmer <[EMAIL PROTECTED]> writes:
> > Thanks anyway for the bug report, though; we might get lucky this time and
> > actually nail (one of) these bugs to the wall.
>
> One possible hint is on the system that works ruby is gett
Matthew Palmer <[EMAIL PROTECTED]> writes:
> You can rename /lib/tls to something else (I like /lib/tls.disabled) and the
> linker will then run everything against the regular libraries. Perhaps give
> that a go temporarily on the failing system and see if that corrects the
> problem (then obviou
Matthew Palmer <[EMAIL PROTECTED]> writes:
> Thanks anyway for the bug report, though; we might get lucky this time and
> actually nail (one of) these bugs to the wall.
More input:
I installed the puppet client package on another machine but talking
to the same server. I brought up-to-date all
On Tue, Aug 29, 2006 at 06:52:35PM -0400, Brett Viren wrote:
> I'm finding that running puppetd with a very simple (but possibly
> wrong) setup leads to random Ruby back traces and SegVs.
>
> Please let me know if I can provide additional info.
Good bug report. This kind of problem has been repor
Package: puppet
Version: 0.18.4-1
Severity: important
Hi,
I'm finding that running puppetd with a very simple (but possibly
wrong) setup leads to random Ruby back traces and SegVs. Here is the
setup:
The server ("home.phy.bnl.gov") is run like:
puppetmasterd --debug
The client ("lycastus.p
8 matches
Mail list logo
