02-18-2008
Server become too slow
Hi,
Since last week our server become too slow when we try to run application on it. When we run top command, it show as below:
Quote:
System: xxxxxx Mon Feb 18 10:56:14 2008
Load averages: 21.60, 21.56, 21.55
120 processes: 97 sleeping, 21 running, 2 zombies
Cpu states:
LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
21.60 45.4% 0.0% 54.6% 0.0% 0.0% 0.0% 0.0% 0.0%
Memory: 383576K (112220K) real, 367628K (107192K) virtual, 1138632K free Page#
1/3
TTY USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
? 16671 root 222 20 168K 212K run 10:56 4.94 4.93 asasd
? 16695 root 222 20 168K 224K run 10:47 4.91 4.90 asasd
? 16567 root 223 20 168K 224K run 10:41 4.89 4.88 asasd
? 16583 root 223 20 168K 220K run 10:54 4.87 4.86 asasd
? 16615 root 223 20 168K 188K run 10:55 4.86 4.85 asasd
? 16631 root 223 20 168K 212K run 10:54 4.85 4.84 asasd
? 16591 root 223 20 168K 188K run 10:56 4.82 4.82 asasd
? 16663 root 223 20 168K 224K run 9:28 4.80 4.79 asasd
? 16711 root 223 20 168K 212K run 10:49 4.78 4.77 asasd
? 16575 root 222 20 168K 212K run 10:55 4.76 4.75asd
? 16679 root 222 20 168K 220K run 10:55 4.68 4.67 asasd
? 16655 root 223 20 168K 224K run 10:50 4.66 4.65 asasd
? 16607 root 223 20 168K 188K run 10:54 4.65 4.64 asasd
? 16687 root 221 20 168K 188K run 10:52 4.64 4.63 asasd
? 19366 root 223 20 200K 220K run 1:04 4.61 4.60 asasd
? 16559 root 223 20 168K 220K run 10:58 4.61 4.60 asasd
? 16639 root 223 20 168K 212K run 10:56 4.61 4.60 asasd
? 16703 root 223 20 168K 212K run 10:50 4.58 4.57 asasd
? 16599 root 168 20 168K 224K sleep 10:45 4.00 3.99 asasd
? 16540 root 152 20 2364K 7304K run 14:33 3.96 3.95 java
? 16623 root 168 20 168K 220K sleep 10:54 3.61 3.60 asasd
? 17720 www 154 20 24404K 21592K sleep 1:18 1.98 1.98-httpd
? root 152 20 0K 0K run 0:24 0.90.92 0.92fsd
pts/tc 19888 root 168 20 3416K 648K run 0:00 0.20 0.18 top
So it's nothing to do with heavy utilization, right? Can you give some opinion on what actually had happended?
Thank you very much...
9 More Discussions You Might Find Interesting
1. OS X (Apple)
We have just added 5 macs to what used to be an all Windows shop. Everything works great except the macs upload to a windows 200 file server extremly slow. Are there any suggestions to make the upload faster? (2 Replies)
Discussion started by: wbeard6142
2 Replies
2. SCO
Hi,
Wonder is someone can help.
I've got a server SCO_SV 3.2v5.0.7 PentIII that is located at a different site and is running slow and has been for a week. I've been speaking to a third party who say nothing is wrong with it but its still running slow.
The 3rd party advise it could be a... (2 Replies)
Discussion started by: tez
2 Replies
3. Post Here to Contact Site Administrators and Moderators
Hi Guys,
Since last 20-30 min Server was Too slow ..even few of times i got Database connection error.
Thanks
Sanjay Tripathi (0 Replies)
Discussion started by: SanjayLinux
0 Replies
4. UNIX for Advanced & Expert Users
Hello,
I am using Redhat redhat 4 update 4 kernal 2.6. My server is some time suddenly running slow.
The averge cpu load goes up to 50 to 60. (There is only two CPU and usually, the averge load
is between 1 to 2.5) That time, i see, there are several sessions connected.
Normally, we have... (5 Replies)
Discussion started by: govindts
5 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Following my last post I've mounted the remote server on my local server. However copying files from this mounted server is increadbily slow. If I copy files using rcp it's very fast so I assume there must be a setting somewhere?
Any help appreicated.
Thanks (2 Replies)
Discussion started by: AngryBunny
2 Replies
6. UNIX for Dummies Questions & Answers
Hi guyes our linux server is very slow today and load average is more than 16 .I m new in linux request you to kindly help resolving the issue.
Where can i find the log for the cause.
# lsb_release -a
LSB Version: ... (2 Replies)
Discussion started by: pinga123
2 Replies
7. Solaris
I recently configured a WANBoot server on a Ldom 2.0 running Solaris10u9 with ZFS root. When i start the installation form the client with
Ok Boot net - install ,
it takes at least 20-25 minutes just to download the miniroot on the client .. i read there was a bug on T servers firmware... (2 Replies)
Discussion started by: fugitive
2 Replies
8. Infrastructure Monitoring
There is a big problem with the server (VPS based on OpenVZ, CentOS 5, 3GB RAM). The problem is the following. The first 15-20 minutes after starting the server is operating normally, the load average is less than or about 1.0, but then begins to increase sharply% wa, then hovers around 95-99%.... (2 Replies)
Discussion started by: draiphod
2 Replies
9. AIX
Hello,
All the commands on AIX are running very slow.
Below is few stats but I didn't find any issue in cpu or memory reosurces
vmstat
System configuration: lcpu=4 mem=6144MB ent=1.00
kthr memory page faults cpu
----- -----------... (2 Replies)
Discussion started by: Vishal_dba
2 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)
NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO
sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)