thanks to you and Ian for the replies. here's the scoop thus far... The network interfaces are indeed UP. I'm guessing someone simply failed to configure the startup files correctly to remove items that aren't used. (the server seems to have been running for 4 or more years since it's last installation).
It would appear that part of our problem is a DNS issue. We contacted our old sys admin, and that's the route he's taking. As for drive space, I think we're going to plan a weekend to clean up this box. I knew I could count on the list for help (thanks!!!!), but I don't know if we have this resolved yet, or what it will take to get it resolved. I DO know that DNS you sometimes have to wait a bit before you see the changes... So, I'm being patient. Just a further note to my involvement here - I have a past life as a network engineer, but have been doing development for a few years now. As a result of some recent staff shuffles, our sys admin is only available periodically, leaving us to fix most issues. And seeing as I have this past life, and a "strong" tech background (their words, not mine), guess who gets elected to handle most of the issues.... <grins> Unfortunately, my tech background is mostly windows based (I'm working on this issue.. LOL). Thanks again. -----Original Message----- From: Frank Ledderhof [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 06, 2003 3:01 PM To: [EMAIL PROTECTED] Subject: Re: (clug-talk) Need Help - downed server The easiest way to test your NICs is to bypass any other network equipment you have and connect two of your machines with a null aka crossover cable. Then transfer a few large files back and forth and verify them with MD5s (which you generated beforehand). Running your HDD over 90% capacity is sure to bog your system down due to extreme fragmentation and virtual memory problems. To list by file size, try "ls PATH -R -S -l" where PATH is the directory from which you want to start searching. (You could also use find, but no matter.) Also, if you don't have the HDD partitioned yet, do so sometime and place the data you're serving up on one of the other partitions. Then, when it gets full again, it won't affect your system so badly. This trick even works in Windoze - even "Program Files" lives on D: so that I can leave at least a Gig for M$ to put DLLs, drivers, etc on. Call it OT, but it just support my point. Good luck! :c) Shawn Grover wrote: >One of the server's I have inherited in the past week has suddenly decided >to stop serving it's web pages and/or has encountered a problem with a >network card. > >My guess thus far is that we either have run out of drive space, or our NICs >aren't comming up right when the system boots. > >So, first, I'm looking for an appropriate command to find the largest files >on the drive (I'll be checking google after I send this message, but our >primary site is down - kinda urgent to get this fixed). Any tips? > > >
