Thanks. My first 2 attempts in deleting that route didn't succeed (syntax error perhaps) but i managed to solve it on the 3rd try. I was already stressed out so I wasn't able to apprise the list with my solution. Then when I arrived home (where I planned to post my "case solved" message), I got entangled with a long lost neighbor who asked me to join him for a few drinks. :-)
i wonder what could've caused or added that route? I am sure I didn't add it, and I'm the only one who has root privileges on this server, which never goes offline except for such loss of power. The reason I forced fsck was to eliminate file system errors from the list of possible culprits, because I AM sure I didn't add that route. The server was working fine before the power interruption (abrupt power cut-off). fooler mail wrote: > On Mon, Feb 9, 2009 at 5:11 PM, Jun Martin <jun.mar...@gmail.com> wrote: > >> Our server's acting weird, guys. Please help. >> >> The power went out and our generator bogged down. By the time I decided to >> power down the server, its UPS ran out of juice. >> >> When power was back up, the server booted successfully, except that there >> this error (2nd line) in the logs: >> ----------------------- >> Feb 9 15:12:43 ibm network: Bringing up loopback interface: succeeded >> >> Feb 9 15:12:45 ibm ifup: SIOCADDRT: File exists >> >> Feb 9 15:12:45 ibm network: Bringing up interface eth0: succeeded >> ---------------------- >> >> The weird thing about it, is that it only wants to "TALK" to the gateway and >> not to any other workstation! :-( >> >> I've already forced fsck on reboot, to no avail. >> > > > fsck is related to a filesystem and not to a network configuration... > > > >> Heres the output of >> #netstat -rn: >> >> Destination Gateway Genmask Flags Metric Ref Use >> Iface >> 192.168.1.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth0 >> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 >> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo >> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 >> >> Googling for "SIOCADDRT: File exists" gave me no solution to the problem. >> Speaking of, what *IS* the problem? >> > > SIOCADDRT means Socket IOCtl for ADDing a RouTe in the routing table.. > > in unix.. everything is a file... file exists means when adding a > route that was already existing.. it gives you a SIOCADDRT: File > exists error... > > the reason why your server cant talk to other workstations within its > network segment because of the first route entry in your routing > table... > > >> 192.168.1.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth0 >> > > the route entry above means that when the destination ip address is in > the range of 192.168.1.0/255.255.255.0 it sends to your gateway ip > address 192.168.1.1 instead directly to its network segment (see the > second entry of your routing table as that is the correct entry).. > > you must remove that as that was the caused of your problem... > > after removing that... this is what your routing table looks like... > > >> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 >> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo >> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 >> > > fooler. > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph > > _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
