For When You Can't Have The Real Thing
[ start | index | login ]
start > Solaris > 10 > WARNING: init(1M) exited on fatal signal 9: restarting automatically

WARNING: init(1M) exited on fatal signal 9: restarting automatically

Created by dave. Last edited by dave, 4 years and 213 days ago. Viewed 8,154 times. #2
[diff] [history] [edit] [rdf]
labels
attachments
(2014-05-13)

Problem

Sun just fills its console with

WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: init(1M) exited on fatal signal 9: restarting automatically

If you can get into it, all commands fail with

% su - root
ld.so.1: su: fatal: libcmd.so.1: open failed: No such file or directory

What Happened

/var/lib was unprotected, and someone ran crle with a bad collection of options.

How I fixed It

boot cdrom -ws

# mount /dev/dsk/c1t0d0s0 /a # chroot /a /bin/sh # rm /var/ld/ld.config # crle -l /lib:/usr/lib # exit # umount /a # sync # sync # reboot

Beware that if your root partition isn't c1t0d0s0, you'll have to substitute accordingly.

(Source: Google had lots of hits, but >>this one had most things covered.)

no comments | post comment
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.

Useful:


snipsnap.org | Copyright 2000-2002 Matthias L. Jugel and Stephan J. Schmidt