[96219] in RedHat Linux List
Re: top is not working
daemon@ATHENA.MIT.EDU (David S Edwards)
Sun Oct 25 15:09:46 1998
Date: Sun, 25 Oct 1998 12:09:14 -0800
To: redhat-list@redhat.com
From: "David S Edwards" <David@california.net>
In-Reply-To: <005001be0042$f40eba40$0200a8c0@eric>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Try doing a "rpm -Va" to see if any files have been changed from your
original installation. ls, ps and top are all likely targets for a hacker
to change, so they can mask their processes.
David
At 12:11 PM 10/25/98 -0600, you wrote:
>Well it seems like a hardware or network problem. Perhaps the problem is
>with the machine you use to ssh. Were there any symptoms of problems from
>users of this machine previous to yours? Are you sure? Does the "other"
>5.1 box (box #2) exhibit the same problems? Can you log into the machines
>locally after "cleaning" them and do they exhibit the same problems?
>
>- Eric
>
>-----Original Message-----
>From: Nikki Cook <sunny@mail.suntrix.com>
>To: redhat-list@redhat.com <redhat-list@redhat.com>
>Date: Saturday, October 24, 1998 1:02 PM
>Subject: top is not working
>
>
>Ok, now I'm comfortable enough with how things are done here to present you
>all with my problem in hopes that you can help me.
>
>This is on a 5.1 box (orig 2.0.34 kernel from the CD) that has been running
>flawlessly since July until about a week ago. I normally admin that
>machine via ssh. I also normally tail -f messages because this box is a
>shell user box.
>
>The first thing I saw was the tail screen go nuts, like a panic or race. I
>couldn't do anything with the box to get control, nothing responded, so I
>hit the power button.
>
>It rebooted just fine, forced the fsck without any glaring problems. All
>daemons loaded, all croned user processes started, and everything looked
>just ducky 'till I ran top to check on their procesess. I noticed that
>Top's CPU % was about half what it normally took. I checked file size/date
>against another 5.1 box on our network, no difference.
>
>The next time I tried to run top, it threw a "bad data in /var/run/utmp" at
>me, and made that xterm unusable.
>
>After reading and digging for info, I rm'd /var/run/utmp and /var/log/wtmp,
>touched those files, logged out and back in. Top still wouldn't run. Now
>this is really weird, Top wouldn't run on that other 5.1 box either. Yes,
>I was logged into it as well via ssh when all this started.
>
>Back to box #1... I rm'd and touched the files again, rebooted, changed to
>single user mode and ran fsck on each partition. It fixed stuff, then I
>ran it a second time on each partition and all partitions showed clean.
>
>Logged in. Top ran 3 times, then started throwing the same "bad data"
>complaint at me.
>
>I checked /dev/ttyp*, didn't see anything weird there.
>
>If I've left lots out that you need to know to help me or point me in a
>direction, my apologies. Yep, I'm one of those "newbies" that needs
>somebody to take me by my sweaty li'l palm and explicitly and succinctly
>tell me how to fix this. I just don't have the know-how to sort this out
>and fix it on my own.
>
>
>TIA,
>
>Nikki
>
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> SunTrix Com Internet Services
>Daytona Beach, Florida
> PPP and Shell Accounts (904) 258-5434
>WEB Design webdesign@mail.suntrix.com
>http://www.suntrix.com
>WEBBnet IRC Network
>irc.webbnet.org | irc.us.webbnet.org
> ftp://ftp.suntrix.com | mail.suntrix.com
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>--
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
>http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with
> "unsubscribe" as the Subject.
>
>
>
>
>--
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with
> "unsubscribe" as the Subject.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
