Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had an issue this morning where had to kill a process in order to bring things back to normal.
On one of my servers with my application-id when I tried to login via putty the login never was successful [ did nothing just sat on putty blank screen], however to the same server when tried using other ID's I was able to login, from the system level logs, I was able to see that whenever the APP-ID was trying to login it was recording:
sshd: fatal: setresuid 745600: Resource temporarily unavailable
sshd: Received disconnect from xx.xxx.xxx.xx: xx: Connection discarded by broker
Note: IP number is been masqueraded to XX
This was happening only for this particular ID, the ulimit -u on this ID is at unlimited. When 1 of the process owned by this user was killed is when the login thru putty came back.
Can someone explain why and how the resource contention was happening only for this particular ID, even thou when the ulimit for this ID was set to unlimited.
Are there any other logs to be checked where we can understand why the contention occurred at the first place.
The ulimit -n is also at 8192 and I did not see in any log the error: "Too many files open" which makes me believe that it was not the file descriptor causing the issue.
Is there any system level limit that is getting enforced and overriding the ulimit -u, if so what file I should be looking at.
RH Version: Red Hat Enterprise Linux Server release 6.2 (Santiago)
and for the user who was already had a putty session with this ID, for him the screen just froze, even simple ls -lh command never came back with a result.
from an Ubuntu forum that indicates that you may be running out of process table entries (rarely happens). This would appear to be a hard limit on the number of processes a specific user is restricted to.