It starts to become a non-responsive from time to time with 100% cpu usage eventhough there is no applications running except a browser. I have been running centos 4 for the past 6 months without any problem with regular update. Now, I have to reboot whenever it shows signs of a non-response. It starts to exhibit this behaviour a cople of days ago. I could not figure it out the reason and need help.
Is there any tools to troubleshoot this ? I have tried top, system monitor..
I have attache screen shoot of system monitor if it helps.
Mohamed Yusuf
__________________________________________________________ Find your next car at http://autos.yahoo.ca
mohamed yusuf myusuf32@yahoo.ca wrote:
Is there any tools to troubleshoot this ? I have tried top, system monitor..
And you're seeing no CPU?
What about vmstat and iostat? Especially vmstat, unless you're doing audio, network and/or disk, then iostat.
It's hard to pin-point I/O usage in Linux, but even desktops today can literally feel the pinch of I/O.
I have attache screen shoot of system monitor if it helps.
Well, _regardless_, I would run something like this:
while true; do date >> /tmp/mystat.log 2>&1 for i in `seq 1 100`; do vmstat 1 1 >> /tmp/mystat.log 2>&1 iostat -d 1 1 >> /tmp/mystat.log 2>&1 sleep 3 done done
From a script, and call it in the background.
Hello Mohamed,
I can only guess what is happening exactly, but i suspect some process is running wild. I have encountered such a problem with Firefox and the Flash- or Java-plugin.
It will help to know the process which uses up all CPU. Try using top. It shows much more information than the Gnome System Monitor and you'll find the process quite soon.
Regards, Andreas
Thanks Andreas,
I think you are right. The culprit appears to be firefox browser which took about 180 meg of ram. I don't know why ? Anyway, I swiched to opera browser and it's ok now
Mohamed
--- Andreas Rogge arogge@gmx.de wrote:
Hello Mohamed,
I can only guess what is happening exactly, but i suspect some process is running wild. I have encountered such a problem with Firefox and the Flash- or Java-plugin.
It will help to know the process which uses up all CPU. Try using top. It shows much more information than the Gnome System Monitor and you'll find the process quite soon.
Regards, Andreas
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
I am an Opera user for over four years now, and let me assure you - Opera goes nuts much more often than firefox.
Take care, Alex
On 8/31/05, mohamed yusuf myusuf32@yahoo.ca wrote:
Thanks Andreas,
I think you are right. The culprit appears to be firefox browser which took about 180 meg of ram. I don't know why ? Anyway, I swiched to opera browser and it's ok now
Mohamed
--- Andreas Rogge arogge@gmx.de wrote:
Hello Mohamed,
I can only guess what is happening exactly, but i suspect some process is running wild. I have encountered such a problem with Firefox and the Flash- or Java-plugin.
It will help to know the process which uses up all CPU. Try using top. It shows much more information than the Gnome System Monitor and you'll find the process quite soon.
Regards, Andreas
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi,
Help. I have an issue adding accounts to a centos box of joy that has otherwise been 100% reliable.
Basically if I run a "useradd test" as root it returns useradd: unable to lock password file.
There is a /etc/passwd.lock file:
[root@bill etc]# more passwd.lock 6697
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 6697 root 25 0 22672 22M 612 R 47.2 1.1 1:02 1 useradd
Eating lots of cpu... but doing what?
If anyone has any clues I'd really appreciate the help :)
Cheers,
Nick
Nick,
Were you already running a useradd before you started this one? Maybe in another terminal session.
Try killing the process and see if the passwd.lock file is still there.
Wayne
On 9/1/05, Nick list@everywhereinternet.com wrote:
Hi,
Help. I have an issue adding accounts to a centos box of joy that has otherwise been 100% reliable.
Basically if I run a "useradd test" as root it returns useradd: unable to lock password file.
There is a /etc/passwd.lock file:
[root@bill etc]# more passwd.lock 6697
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 6697 root 25 0 22672 22M 612 R 47.2 1.1 1:02 1 useradd
Eating lots of cpu... but doing what?
If anyone has any clues I'd really appreciate the help :)
Cheers,
Nick
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On
Behalf Of Wayne Bastow
Sent: Thursday, 1 September 2005 1:14 PM To: CentOS mailing list Subject: Re: [CentOS] useradd: unable to lock password file
Nick,
Were you already running a useradd before you started this one? Maybe in
another terminal session.
Yes. It gets called about 10 times a minute at busy times... however it was working fine then just suddenly stopped :(
Try killing the process and see if the passwd.lock file is still there.
I've been through and looked for any other process and can't find one :(
Any other ideas?
On 9/1/05, Nick list@everywhereinternet.com wrote: Hi,
Help. I have an issue adding accounts to a centos box of joy that has otherwise been 100% reliable.
Basically if I run a "useradd test" as root it returns useradd: unable to lock password file.
There is a /etc/passwd.lock file:
[root@bill etc]# more passwd.lock 6697
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 6697 root 25 0 22672 22M 612 R 47.2 1.1 1:02 1 useradd
Eating lots of cpu... but doing what?
If anyone has any clues I'd really appreciate the help :)
Cheers,
Nick
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
looking forward this problem since rh8, why redhat came with passwd pam.d with lock file?
compare with passwd pam.d that come with mandrake heard, if that can avoid for corrupt database
On 9/1/05, Nick list@everywhereinternet.com wrote:
Hi,
Help. I have an issue adding accounts to a centos box of joy that has otherwise been 100% reliable.
Basically if I run a "useradd test" as root it returns useradd: unable to lock password file.
There is a /etc/passwd.lock file:
[root@bill etc]# more passwd.lock 6697
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 6697 root 25 0 22672 22M 612 R 47.2 1.1 1:02 1 useradd
Eating lots of cpu... but doing what?
If anyone has any clues I'd really appreciate the help :)
Cheers,
Nick
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi,
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just doesn't die or return anything and just sits there chewing data :(
Man down.
Nick
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Lewi Kristianto Sent: Thursday, 1 September 2005 1:51 PM To: CentOS mailing list Subject: [CentOS] Re: useradd: unable to lock password file
looking forward this problem since rh8, why redhat came with passwd pam.d with lock file?
compare with passwd pam.d that come with mandrake heard, if that can avoid for corrupt database
On 9/1/05, Nick list@everywhereinternet.com wrote:
Hi,
Help. I have an issue adding accounts to a centos box of joy that has otherwise been 100% reliable.
Basically if I run a "useradd test" as root it returns useradd: unable
to
lock password file.
There is a /etc/passwd.lock file:
[root@bill etc]# more passwd.lock 6697
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU
COMMAND
6697 root 25 0 22672 22M 612 R 47.2 1.1 1:02 1
useradd
Eating lots of cpu... but doing what?
If anyone has any clues I'd really appreciate the help :)
Cheers,
Nick
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- ichtus _______________________________________________ Lewi Supranata .K iPLUG Team
GnuPG Public Key: http://mbone.petra.ac.id/u/ichtus/ichtus-keys2 _______________________________________________ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 8/31/05, Nick Bryant list@everywhereinternet.com wrote:
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just doesn't die or return anything and just sits there chewing data :(
Man down.
How about pwck and/or grpck ?
And if that fixes it, send the money to the CentOS developers.
Greg
On 8/31/05, Nick Bryant list@everywhereinternet.com wrote:
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just
doesn't
die or return anything and just sits there chewing data :(
Man down.
How about pwck and/or grpck ?
And if that fixes it, send the money to the CentOS developers.
Be glad too.
Ok I think I found the problem... is there a maximum number of entries in /etc/passwd? I just removed the last 1000 lines and its working again, total entires in the file now 59463.
Problem is its really slow to add new users now (around 10 seconds). We have several scripts that create newusers so I guess that's what caused the locking situation.
Could a corruption be whats slowing it down (running pwck -r now) or am I just approaching the limits of a flat file auth scheme?
Cheers,
N
On Thu, 2005-09-01 at 15:32 +1000, Nick Bryant wrote:
On 8/31/05, Nick Bryant list@everywhereinternet.com wrote:
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just
doesn't
die or return anything and just sits there chewing data :(
Man down.
How about pwck and/or grpck ?
And if that fixes it, send the money to the CentOS developers.
Be glad too.
Ok I think I found the problem... is there a maximum number of entries in /etc/passwd? I just removed the last 1000 lines and its working again, total entires in the file now 59463.
Problem is its really slow to add new users now (around 10 seconds). We have several scripts that create newusers so I guess that's what caused the locking situation.
Could a corruption be whats slowing it down (running pwck -r now) or am I just approaching the limits of a flat file auth scheme?
Take a look at /etc/login.defs the stock max UID is 60000.
Sean
On Thu, 2005-09-01 at 15:32 +1000, Nick Bryant wrote:
On 8/31/05, Nick Bryant list@everywhereinternet.com wrote:
Ok $200USD for anyone who can help me fix this now.... rebooted and
it
doesn't say the file is locked anymore... the useradd command just
doesn't
die or return anything and just sits there chewing data :(
Man down.
How about pwck and/or grpck ?
And if that fixes it, send the money to the CentOS developers.
Be glad too.
Ok I think I found the problem... is there a maximum number of entries
in
/etc/passwd? I just removed the last 1000 lines and its working again,
total
entires in the file now 59463.
Problem is its really slow to add new users now (around 10 seconds). We
have
several scripts that create newusers so I guess that's what caused the locking situation.
Could a corruption be whats slowing it down (running pwck -r now) or am
I
just approaching the limits of a flat file auth scheme?
Take a look at /etc/login.defs the stock max UID is 60000.
Bingo! That's got to be what caused it to just keel.
[root@bill syd01]# cut -d":" -f 3 passwd |sort -rn |more 60000 59999
If I just change that file will I need to restart anything? Sorry for the noob question but I'm a +60K user virgin. (The sub-dir 32K limit for home dirs was equally as big a learning curve ;o)
N
On Thu, 2005-09-01 at 15:40 +1000, Nick Bryant wrote:
On Thu, 2005-09-01 at 15:32 +1000, Nick Bryant wrote:
On 8/31/05, Nick Bryant list@everywhereinternet.com wrote:
Ok $200USD for anyone who can help me fix this now.... rebooted and
it
doesn't say the file is locked anymore... the useradd command just
doesn't
die or return anything and just sits there chewing data :(
Man down.
How about pwck and/or grpck ?
And if that fixes it, send the money to the CentOS developers.
Be glad too.
Ok I think I found the problem... is there a maximum number of entries
in
/etc/passwd? I just removed the last 1000 lines and its working again,
total
entires in the file now 59463.
Problem is its really slow to add new users now (around 10 seconds). We
have
several scripts that create newusers so I guess that's what caused the locking situation.
Could a corruption be whats slowing it down (running pwck -r now) or am
I
just approaching the limits of a flat file auth scheme?
Take a look at /etc/login.defs the stock max UID is 60000.
Bingo! That's got to be what caused it to just keel.
[root@bill syd01]# cut -d":" -f 3 passwd |sort -rn |more 60000 59999
If I just change that file will I need to restart anything? Sorry for the noob question but I'm a +60K user virgin. (The sub-dir 32K limit for home dirs was equally as big a learning curve ;o)
Nick-
I don't think you need to restart anything. login.defs is part of the shadow-utils rpm which looks to just contain applications. i suspect they simply read it at invocation.
Am Donnerstag, den 01.09.2005, 15:40 +1000 schrieb Nick Bryant:
If I just change that file will I need to restart anything? Sorry for the noob question but I'm a +60K user virgin. (The sub-dir 32K limit for home dirs was equally as big a learning curve ;o)
Hello Brian,
are you sure you want to go with /etc/passwd? You're talking about >60k users. Maybe you should look at LDAP or an equivalent solution. Especially if you are going to set up other machines with large user-bases it will simplify management a lot. With LDAP you can manage users, groups, group-membership and the like in a central directory. You can even configure sendmail, autofs and other services to lookup data in the directory (which makes the whole thing - at least imho - much easier and straightforward to manage).
Regards, Andreas
Hi,
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just doesn't die or return anything and just sits there chewing data :(
Man down.
Nick
when you run the useradd, are you doing so as root or via another method?
then check these things as root
cd / ls -axl
check to see if all directories, permissions and ownerships look right for everything from the root dir
then check this file with vi or pico or more or whatever... :-)
/etc/default/useradd
all look ok there?
i always look in /tmp to see if there is any garbage lurking around causing probs even if it isnt necessarily related to exactly what i am looking for at that moment.
a few other things escape me at the moment as i am hungry. back inna few
regards,
- rh
Robert Hanson Abba Communications http://www.abbacomm.net
On Thu, 2005-09-01 at 14:19 +1000, Nick Bryant wrote:
Hi,
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just doesn't die or return anything and just sits there chewing data :(
Man down.
---- I vaguely recall this type of thing happening when /etc/passwd & /etc/shadow /etc/shadow- had hand edits that didn't align together with each other.
If this helps - I like Greg's idea - money to CentOS.org developers
Craig
On Thu, 2005-09-01 at 14:19 +1000, Nick Bryant wrote:
Hi,
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just doesn't die or return anything and just sits there chewing data :(
Man down.
---- you didn't say which version of CentOS
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126709
Craig
On Thu, 2005-09-01 at 14:19 +1000, Nick Bryant wrote:
Hi,
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just
doesn't
die or return anything and just sits there chewing data :(
Man down.
you didn't say which version of CentOS
Sorry, 3.5.
Sounds similar... expect I don't seem to get the non-removing lock file everytime. I guess there was some condition that caused it to not remove itself.
On Thu, 2005-09-01 at 14:19 +1000, Nick Bryant wrote:
Hi,
Ok $200USD for anyone who can help me fix this now.... rebooted and it doesn't say the file is locked anymore... the useradd command just doesn't die or return anything and just sits there chewing data :(
Man down.
---- one more thing to check
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157795
Craig
mohamed yusuf wrote:
Thanks Andreas,
I think you are right. The culprit appears to be firefox browser which took about 180 meg of ram. I don't know why ? Anyway, I swiched to opera browser and it's ok now
Maybe it's time to drop the profile and start a new one? Corrupted profiles used to screw me up all the time but it hasn't happened in quite some time.
http://www.mozilla.org/support/firefox/profile
--Ajay
-
Ajay Sharma -
Andreas Rogge -
Bryan J. Smith -
Canaris -
Craig White -
Greg Knaddison -
Lewi Kristianto -
mohamed yusuf -
Nick -
Nick Bryant
-
roberth＠abbacomm.net -
Sean O'Connell -
Wayne Bastow