[RHCE] troubleshooting preperatoin

Jeremy Portzer rhce@trilug.org
22 Apr 2003 14:24:11 -0400


--=-dhmPrKLY6jbBug79A6xX
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-04-22 at 13:49, Scott Lundgren wrote:
>=20
> >Jtower and I both think that that would be a good exercise on the
> troubleshooting section of the
> >exam.
>=20
> On that note, has anyone seen/found good preperation for the troubleshoot=
ing
> quizes/scenarios? Coming from a programmer perspective than a sysadmin, t=
his
> is the aspect of the test that concerns me the most since I won't have th=
e
> work experience of walking up to a hung box and figuring out how to walk
> through and revive it.

Of course, nothing substitutes for real-world experience, and I think
one of the reasons for the troubleshooting section on the RHCE *is* to
test for real-world experience.  In this study group we might want to
try setting up some troubleshooting scenarios to practice. I'll think
some more about how we might do this.

One thing that you should be good at is using the kernel/bootloader
options.  For example, booting in single-user mode is "linux single"
from LILO, or typing "a" then adding the word "single" in GRUB .  To
boot in runlevel 3 (might be useful if the default runlevel is 5, yet
there are X problems), use the argument "3" (ie, "linux 3" from lilo).

Other useful options are "ide=3Dnodma" (in case of hardware lockups which
are often DMA problems), "nosysinfo" (on Red Hat Linux 9, turns off NPTL
and may un-hose your glibc).

The latter option, "nosysinfo" has been useful for people who mistakenly
installed an "i386" glibc update (which doesn't include NPTL) on top of
the previously existing i686 glibc.  When the kernel and other programs
were trying to use NPTL, but the upgraded glibc didn't support it, the
system was hosed.  nosysinfo fixes this (so you can boot up the system
and install the correct glibc).

Hope this helps,
Jeremy
=20
--=20
/=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\
| Jeremy Portzer       jeremyp@pobox.com       trilug.org/~jeremy     |
| GPG Fingerprint: 712D 77C7 AB2D 2130 989F  E135 6F9F F7BC CC1A 7B92 |
\=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/

--=-dhmPrKLY6jbBug79A6xX
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA+pYjLb5/3vMwae5IRAl8xAJ0VqHbs1BTA3fQSEMa7JNcQuZsB6wCeIVH5
LOKHHGqiy7sdqSPKdiFu5sE=
=XpUc
-----END PGP SIGNATURE-----

--=-dhmPrKLY6jbBug79A6xX--