Ferdorians,
This is my first message to this groups, I don't really know if this would be the best group for my question. I am experiencing this problem for some time now, I hope you can help.
The main problem is that my machine is causing CPU excessive usage when a SSH session is closed. It does not happen when openining, neither during the session, but when it is closed.
I have tried to collect some evidence, here they are:
- This is what I telled the machine for this test:
$ ps -e -o pcpu,cputime,pid,args > before $ ssh localhost thiagob@localhost's password: id: cannot find name for group ID 74594 $ ps -e -o pcpu,cputime,pid,args > during $ exit $ ps -e -o pcpu,cputime,pid,args > after
- Prior to the execution of the SSH client, everything is perfect with the processes running on the machine. I won't attach the process monitor report here because it is very long and doesn't add much information. There is almost no CPU activity prior to executing the client.
- After opening an SSH terminal, the CPU isn't busy. Here is the process status I got with the terminal opened:
$ grep ssh during 0.0 00:00:00 1898 /usr/sbin/sshd 0.0 00:00:00 2605 /usr/bin/ssh-agent startkde 0.4 00:00:00 4470 ssh localhost 0.0 00:00:00 4471 sshd: thiagob [priv] 0.0 00:00:00 4479 sshd: thiagob@pts/8 << This is the one that gets hungry
- After executing the `exit` command, the CPU become annoingly busy:
$ grep ssh after 0.0 00:00:00 1898 /usr/sbin/sshd 0.0 00:00:00 2605 /usr/bin/ssh-agent startkde 0.0 00:00:00 4471 sshd: thiagob [priv] 98.0 00:00:05 4479 sshd: thiagob@notty ^^
- These are the versions for the software:
$ ssh -V OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f $ uname -a Linux serpro-1422052.rce.serpro 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 i686 i386 GNU/Linux $ bash --version GNU bash, version 2.05b.0(1)-release (i386-redhat-linux-gnu) Copyright (C) 2002 Free Software Foundation, Inc.
Some weird facts: - The same behavior is observer in two other machines when I open an SSH session from my machine - My logout scripts are empty on all machines, they contain at most a command to clena the term
I hope anyone can help.
Cheers,
Thiago Arrais
Just a quick question that you probably mentioned, but just to be shure: Is the exessive usage on the server side or the client side? What are you running trough ssh - kde? What OS etc. is the server?
Kyrre
fre, 21.10.2005 kl. 18.31 skrev Thiago Arrais:
Ferdorians,
This is my first message to this groups, I don't really know if this would be the best group for my question. I am experiencing this problem for some time now, I hope you can help.
The main problem is that my machine is causing CPU excessive usage when a SSH session is closed. It does not happen when openining, neither during the session, but when it is closed.
I have tried to collect some evidence, here they are:
- This is what I telled the machine for this test:
$ ps -e -o pcpu,cputime,pid,args > before $ ssh localhost thiagob@localhost's password: id: cannot find name for group ID 74594 $ ps -e -o pcpu,cputime,pid,args > during $ exit $ ps -e -o pcpu,cputime,pid,args > after
- Prior to the execution of the SSH client, everything is perfect with
the processes running on the machine. I won't attach the process monitor report here because it is very long and doesn't add much information. There is almost no CPU activity prior to executing the client.
- After opening an SSH terminal, the CPU isn't busy. Here is the
process status I got with the terminal opened:
$ grep ssh during 0.0 00:00:00 1898 /usr/sbin/sshd 0.0 00:00:00 2605 /usr/bin/ssh-agent startkde 0.4 00:00:00 4470 ssh localhost 0.0 00:00:00 4471 sshd: thiagob [priv] 0.0 00:00:00 4479 sshd: thiagob@pts/8 << This is the one that gets hungry
- After executing the `exit` command, the CPU become annoingly busy:
$ grep ssh after 0.0 00:00:00 1898 /usr/sbin/sshd 0.0 00:00:00 2605 /usr/bin/ssh-agent startkde 0.0 00:00:00 4471 sshd: thiagob [priv] 98.0 00:00:05 4479 sshd: thiagob@notty ^^
- These are the versions for the software:
$ ssh -V OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f $ uname -a Linux serpro-1422052.rce.serpro 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 i686 i386 GNU/Linux $ bash --version GNU bash, version 2.05b.0(1)-release (i386-redhat-linux-gnu) Copyright (C) 2002 Free Software Foundation, Inc.
Some weird facts:
- The same behavior is observer in two other machines when I open an
SSH session from my machine
- My logout scripts are empty on all machines, they contain at most a
command to clena the term
I hope anyone can help.
Cheers,
Thiago Arrais
2005/10/21, Kyrre Ness Sjobak kyrre@solution-forge.net:
Just a quick question that you probably mentioned, but just to be shure: Is the exessive usage on the server side or the client side?
Server side.
What are you running trough ssh - kde?
I am not quite sure what to answer here. I am running SSH inside a KDE Konsole terminal and I don't have to run any heavy program to the server to see the behavior. Just loging in and out is sufficient to trigger the CPU to maximum activity.
What OS etc. is the server?
The client and server OSes are the same, all three machines are new and have the same hardware/software environment. So, we can assume the same software that is running on my machine (client) is running on the server.
Regards,
Thiago Arrais
desktop@lists.fedoraproject.org
-
Kyrre Ness Sjobak -
Thiago Arrais