From: michael.wilkinson@twcable.com
Date: Tue Jul 09 2002 - 01:49:29 EDT
Hi all-
Go an emergency... We have a server that took a power hit today and upon
reboot
could not fsck the root metadevice. We booted off the cd-rom, fsck'd it and
all was
happy - almost.
Once we gained access to the system it was discovered that it did not have a
def-
ault route! We have a valid /etc/defaultrouter and we can ping the gateway.
So, we
decided to run route and manually add the route. No good, we get this error:
# route add default x.x.x.x
route: socket: Protocol not supported
This machine has been active and running for years, but I can't remember the
last
time it was actually rebooted.
Anyway, anyone got any ideas? I tried running in.rdisc to see if it could
discover a
router... What would cause the above error?
Mike Wilkinson
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:34 EDT