Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #188762 > unrolled thread

Gnome desktop almost totally unresponsive in Jessie

Started by"James H. H. Lampert" <jamesl@touchtonecorp.com>
First post2017-11-08 19:50 +0100
Last post2017-11-08 23:30 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.debian.user


Contents

  Gnome desktop almost totally unresponsive in Jessie "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2017-11-08 19:50 +0100
    Re: Gnome desktop almost totally unresponsive in Jessie Roberto C. Sánchez <roberto@debian.org> - 2017-11-08 20:00 +0100
      Re: Gnome desktop almost totally unresponsive in Jessie "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2017-11-08 23:30 +0100

#188762 — Gnome desktop almost totally unresponsive in Jessie

From"James H. H. Lampert" <jamesl@touchtonecorp.com>
Date2017-11-08 19:50 +0100
SubjectGnome desktop almost totally unresponsive in Jessie
Message-ID<uJDAd-2kG-5@gated-at.bofh.it>
I've got a small problem. On our local Jessie box, the Tomcat and Apache 
web servers both seem responsive enough, and I likewise have no trouble 
getting and using an SSH session remotely (except that the "find" 
command is extremely slow).

But the Gnome desktop has become almost totally unresponsive.

I'd rather not restart the box. Any advice on how to deal with this 
without restarting the box?

--
JHHL

[toc] | [next] | [standalone]


#188763

FromRoberto C. Sánchez <roberto@debian.org>
Date2017-11-08 20:00 +0100
Message-ID<uJDJT-2o5-1@gated-at.bofh.it>
In reply to#188762
On Wed, Nov 08, 2017 at 10:40:22AM -0800, James H. H. Lampert wrote:
> I've got a small problem. On our local Jessie box, the Tomcat and Apache web
> servers both seem responsive enough, and I likewise have no trouble getting
> and using an SSH session remotely (except that the "find" command is
> extremely slow).
> 
> But the Gnome desktop has become almost totally unresponsive.
> 
> I'd rather not restart the box. Any advice on how to deal with this without
> restarting the box?
> 
The output of 'ps aux', 'iostat', and 'free -m' would help identify the
problem.  Also, 'cat /proc/mdstat' if you have a RAID setup.

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]


#188785

From"James H. H. Lampert" <jamesl@touchtonecorp.com>
Date2017-11-08 23:30 +0100
Message-ID<uJH17-4Q4-5@gated-at.bofh.it>
In reply to#188763
On 11/8/17, 10:55 AM, Roberto C. Sánchez wrote:
>> The output of 'ps aux', 'iostat', and 'free -m' would help identify the
> problem.  Also, 'cat /proc/mdstat' if you have a RAID setup.
. . .

After a mostly-off-List discussion with Mr. Sanchez, I gave up and did a 
"shutdown -r" on the system.

After a re-IPL, Gnome was back to gnormal, and everything else was back 
up as well.

It's not like it's an AS/400, or even a state-of-the-art Linux box, 
that's designed to run for years at a time without an IPL -- it's an old 
Dell PowerEdge 400SC.

And I'd forgotten: it DOES have RAID: a hardware RAID controller with 
two mirrored pairs on it.

No sign of damage to the mirrored pairs, but a full cold-start might be 
necessary to be sure of that, if not an actual controller-level diagnostic.

--
JHHL

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web