[26754] in Athena Bugs
Re: sunblade 150s crash with corrupt gconf
daemon@ATHENA.MIT.EDU (Robert Basch)
Tue Feb 28 16:37:57 2006
In-Reply-To: <200602281742.k1SHgZPw011240@m56-129-7.mit.edu>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EC1026C6-E1C3-4E70-B83D-98A25C4217F6@mit.edu>
Content-Transfer-Encoding: 7bit
From: Robert Basch <rbasch@mit.edu>
Date: Tue, 28 Feb 2006 16:37:14 -0500
To: jhawk@mit.edu
X-Spam-Score: 1.217
X-Spam-Level: * (1.217)
X-Spam-Flag: NO
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
On Feb 28, 2006, at 12:42 PM, jhawk@MIT.EDU wrote:
> Seen so far on m56-129-8 and m26-100-1. They hang after the afs cache
> scan and nothing happens. I moved aside /etc/gconf to /etc/
> gconf.broken
> and then they come back.
Hmm, I don't think anything in the boot sequence should be looking
at /etc/gconf. (We do recreate gconf schemas in /etc/rc2.d/S90athena-
ws,
but that should only look at /etc/athena/gconf). What does the broken
/etc/gconf look like? Do you know if the machine hangs again if you
move the broken /etc/gconf back into place?
>
> Quite painful to debug because the output of the startup scripts no
> longer goes to the console. Instead it seems to go...nowhere? What's
> the story with that? Is it a new bug, a deliberate behavior, or...?
With the advent of SMF in Solaris 10, this output is now logged to
files in /var/svc/log; the output from /etc/rc2.d scripts will be in
/var/svc/log/milestone-multi-user:default.log.
In this situation, it might be useful to try doing "boot -m verbose",
which prints messages as each service is started. "boot -m debug"
will print exhaustive debugging info from SMF.
Bob
