[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] RaQ2 / MIPS machines hanging with IP 0.0.0.0 - a solution.
- Subject: [cobalt-users] RaQ2 / MIPS machines hanging with IP 0.0.0.0 - a solution.
- From: Martin Moeller <martin@xxxxxxx>
- Date: Wed Mar 20 19:46:02 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
I have done some additional testing since sending the fist message
(which never showed on the list). Here are the results:
I can add, that I have tested three versions of egrep, the one on a
reinstalled RaQ2 patched to the latest level, a self-compiled one and
one from a 'damaged' RaQ2. Only the last one fails in the interfaces=
line, the other two give the expected result without rewriting the
expression. Weird..
Original message follows:
=========================
Hello.
If you have had problems with the network interfaces not loading on RaQ2
or other machines, this little guide may get you going again.
I'm not sure it fixes the real issue, but it *does* get the interfaces
to load again, and still ignores .master's, backups, etc... :
Connect a serial terminal to the server at 9600 baud, 8N1.
(If you should get this problem on a RaQ3/RaQ4, use 115200 baud.)
Turn the server on.
Wait for the login prompt.
Log in as admin
su to root.
open /etc/rc.d/init.d/network in an editor (vi or pico).
Find these lines:
# find all the interfaces besides loopback.
# ignore aliases, alternative configurations, and editor backup files
interfaces=`ls ifcfg* | egrep -v 'ifcfg-lo$' | egrep
'ifcfg-[a-z0-9:]+$'`
in the interfases line, change the last egrep to this:
egrep 'ifcfg-[a-z][a-z0-9:]*$' (do still remember the backtick :)).
Save the file again.
Now, stop and start the network:
/etc/rc.d/init.d/network stop
/etc/rc.d/init.d/network start
You should now get your interfaces loading again (check with :
/sbin/ifconfig)
For the record, the original egrep really ought to work. I'm not sure
why it doesn't any more. This however does almost the same thing (unless
you have network interfaces beginning in numbers or colons, which I
doubt).
If you cannot log in via serial cable, then mount the harddisk in
another machine and edit the file there. That should do the trick.
If someone actually finds out *why* this happens, I'd sure like to know.
Regards,
--
Martin Moeller
Liga LinDist ApS.
Faelledvej 16D
DK-2200 Copenhagen N
Tel: +45 35 36 95 05
Fax: +45 35 36 92 05
http://www.liga.dk
mailto: martin@xxxxxxx