Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
07-07-2013, 03:48 PM
|
#1
|
Member
Registered: Feb 2005
Location: Germany
Distribution: Aptosid
Posts: 148
Rep:
|
Server keeps locking up - how to find cause?
Hi!
I've got a server set up that keeps locking up to the point of not even responding to ping, presumably due to excessive CPU usage. Problem is, I can only ssh into it, and the session becomes unresponsive and terminates as soon as this happens. How can I find out what's causing the problem? It's only got busybox, so I can't use top -b. Would renicing sshd help, for instance? Or are there any other recommendable ways of logging CPU usage?
Thanks!
V.
|
|
|
07-07-2013, 04:12 PM
|
#2
|
Senior Member
Registered: Jan 2012
Distribution: Slackware
Posts: 3,348
Rep: 
|
In my opinion, it's unlikely that a process in userspace is able to hog the CPU to such an extent that the IP stack stops responding.
Are you sure this is not a kernel panic or a hard lock-up? How do you get the server back up and running when this happens?
|
|
|
07-07-2013, 06:40 PM
|
#3
|
Member
Registered: Feb 2005
Location: Germany
Distribution: Aptosid
Posts: 148
Original Poster
Rep:
|
I don't do anything to relieve it, it happens regularly - last time I timed it, the lockups happened every minute for about 30 seconds. There's nothing in the crontab to suggest regular activity. It's a NAS, so I'm not exactly sure what could be going on in there...
|
|
|
07-07-2013, 07:05 PM
|
#4
|
Senior Member
Registered: Jan 2012
Distribution: Slackware
Posts: 3,348
Rep: 
|
I would suspect some kind of hardware failure. Are there any logs on this system?
Have you looked closely at the network interface, cables and switch ports? Have you tried connecting the NIC on the unit directly to a PC?
|
|
|
07-08-2013, 09:58 AM
|
#5
|
LQ Newbie
Registered: Oct 2012
Distribution: CentOS or Debian
Posts: 25
Rep:
|
It might be bad memory, have you tried running Memtest86 on it?
|
|
|
07-08-2013, 02:19 PM
|
#6
|
Member
Registered: Oct 2012
Location: Tucson, AZ
Distribution: Debian/CentOS
Posts: 124
Rep:
|
I agree that it may be faulty hardware. I have had the same problem with a corrupt hard drive before. The system tries & tries to correct the problem but in the end the problem is unfixable by the OS and it ends up just hogging CPU time while it attempts repairs.
|
|
|
All times are GMT -5. The time now is 04:56 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|