From: Jolly Roger on
In article <hoftnr$mbs$1(a)news.eternal-september.org>,
Mike <mikee(a)mac.com> wrote:

> On 2010-03-25, Kevin McMurtrie <mcmurtrie(a)pixelmemory.us> wrote:
> > CarbonCore might be damaged. It's the bundle at:
> > /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.f
> > ramework
> >
> > Oddly, I've had CarbonCore self-destruct on my Mac Mini Server over and
> > over. Everything would go into launch/crash cycles and I'd have to
> > force a reboot on the command line. Hours later it would happen again.
> > I think I've tracked it down to a bug in thumbnail generation of MPEG 2
> > files.
>
> This same behavior is happening on two separate Snow Leopard (10.6.2)
> boxes. Carbon Core is destructing on both boxes at the same time?

What software have you installed on each machine that is in common?

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
From: Mike on
On 2010-03-26, Jolly Roger <jollyroger(a)pobox.com> wrote:
> In article <hoftnr$mbs$1(a)news.eternal-september.org>,
> Mike <mikee(a)mac.com> wrote:
>
>> On 2010-03-25, Kevin McMurtrie <mcmurtrie(a)pixelmemory.us> wrote:
>> > CarbonCore might be damaged. It's the bundle at:
>> > /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.f
>> > ramework
>> >
>> > Oddly, I've had CarbonCore self-destruct on my Mac Mini Server over and
>> > over. Everything would go into launch/crash cycles and I'd have to
>> > force a reboot on the command line. Hours later it would happen again.
>> > I think I've tracked it down to a bug in thumbnail generation of MPEG 2
>> > files.
>>
>> This same behavior is happening on two separate Snow Leopard (10.6.2)
>> boxes. Carbon Core is destructing on both boxes at the same time?
>
> What software have you installed on each machine that is in common?

On the iMac 27" I erased 10.6, installed 10.5, partitioned the drive in
half, then reinstalled 10.6 on the empty half. The Mac Mini is 10.6 and
I have installed nothing on this box. Both boxes are fully patched. The
10.5 partition on the iMac 27" works fine. The 10.6 partition on the
iMac 27" fails, and the Mac Mini fails the same way as the iMac 27".

Mike
From: Jolly Roger on
In article <hoik3v$icl$1(a)news.eternal-september.org>,
Mike <mikee(a)mac.com> wrote:

> On 2010-03-26, Jolly Roger <jollyroger(a)pobox.com> wrote:
> > In article <hoftnr$mbs$1(a)news.eternal-september.org>,
> > Mike <mikee(a)mac.com> wrote:
> >
> >> On 2010-03-25, Kevin McMurtrie <mcmurtrie(a)pixelmemory.us> wrote:
> >> > CarbonCore might be damaged. It's the bundle at:
> >> > /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.f
> >> > ramework
> >> >
> >> > Oddly, I've had CarbonCore self-destruct on my Mac Mini Server over and
> >> > over. Everything would go into launch/crash cycles and I'd have to
> >> > force a reboot on the command line. Hours later it would happen again.
> >> > I think I've tracked it down to a bug in thumbnail generation of MPEG 2
> >> > files.
> >>
> >> This same behavior is happening on two separate Snow Leopard (10.6.2)
> >> boxes. Carbon Core is destructing on both boxes at the same time?
> >
> > What software have you installed on each machine that is in common?
>
> On the iMac 27" I erased 10.6, installed 10.5, partitioned the drive in
> half, then reinstalled 10.6 on the empty half. The Mac Mini is 10.6 and
> I have installed nothing on this box. Both boxes are fully patched. The
> 10.5 partition on the iMac 27" works fine. The 10.6 partition on the
> iMac 27" fails, and the Mac Mini fails the same way as the iMac 27".

Hmm... Could it be you have a flaky or bad Mac OS X 10.6 install disc??

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
From: Mike on
On 2010-03-26, Jolly Roger <jollyroger(a)pobox.com> wrote:
> In article <hoik3v$icl$1(a)news.eternal-september.org>,
> Mike <mikee(a)mac.com> wrote:
>
>> On 2010-03-26, Jolly Roger <jollyroger(a)pobox.com> wrote:
>> > In article <hoftnr$mbs$1(a)news.eternal-september.org>,
>> > Mike <mikee(a)mac.com> wrote:
>> >
>> >> On 2010-03-25, Kevin McMurtrie <mcmurtrie(a)pixelmemory.us> wrote:
>> >> > CarbonCore might be damaged. It's the bundle at:
>> >> > /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.f
>> >> > ramework
>> >> >
>> >> > Oddly, I've had CarbonCore self-destruct on my Mac Mini Server over and
>> >> > over. Everything would go into launch/crash cycles and I'd have to
>> >> > force a reboot on the command line. Hours later it would happen again.
>> >> > I think I've tracked it down to a bug in thumbnail generation of MPEG 2
>> >> > files.
>> >>
>> >> This same behavior is happening on two separate Snow Leopard (10.6.2)
>> >> boxes. Carbon Core is destructing on both boxes at the same time?
>> >
>> > What software have you installed on each machine that is in common?
>>
>> On the iMac 27" I erased 10.6, installed 10.5, partitioned the drive in
>> half, then reinstalled 10.6 on the empty half. The Mac Mini is 10.6 and
>> I have installed nothing on this box. Both boxes are fully patched. The
>> 10.5 partition on the iMac 27" works fine. The 10.6 partition on the
>> iMac 27" fails, and the Mac Mini fails the same way as the iMac 27".
>
> Hmm... Could it be you have a flaky or bad Mac OS X 10.6 install disc??

I've used the installer disk on the iMac 27", but not on the mac
mini. I've not reinstalled the mac mini at all.

Mike
From: Mike on
On 2010-03-24, Mike <mikee(a)mac.com> wrote:
> Afternoon,
>
> I have a new mac mini with Snow Leopard (10.6.2), fully patched and
> configured. This box sees my local nets, nfs mounts, OpenLDAP, etc, and
> seems to work fine for local accounts (root). I can ssh(1) into this
> box using a domain account (samba NT4 PDC, v3.3.3) and this seems to
> work just fine. When I log onto the head of the mac mini using a domain
> account, that still works over ssh(1), I get logged in but very quickly
> (moments) nothing will start. Terminal crashes, safari will not launch,
> after terminal crashes it will not relaunch.
>
> I can't even log out.
>
> I must ssh(1) using the same account, sudo to root, then 'shutdown -r now'
> to get the box to start again.
>
> The ldap queries are working ok both when I ssh(1) in and do a 'ls -l
> /home' I see the right resolved user names coming from OpenLDAP. When I
> log into the console I see my home directory (/home/$USER) with the right
> files, etc. The NFS mounts (/home) come from a Fedora Core 5 linux box.
>
> I'm not trying to use the mac mini as a server. I'm trying to get it to
> work as an orderly component of my internal network.
>
> What is going on here and how do I fix the situation? I have this same
> problem with an iMac 27" running Snow Leopard (10.6.2), so I don't think
> this is hardware related.
>
> Mike

I thought I read the clue here, oh well. Somewhere still researching this
issue I read a question about a flaky NFS server. As my NFS server is on
a stock Fedora Core 5 box I decided to upgrade NFS (couldn't hurt). There
are not packages that I can find for NFS on Fedora Core 5 so I upgraded
from source from something like 1.0.8 to 1.0.9. It doesn't sound like
a lot. Snow Leopard, both 10.6.2 and 10.6.3, must be doing something
different or more restrictive than Leopard, 10.5. The home directories
now work without error.

The world is a happier place for me today.

Mike