A server suddenly fails to connect, but root can log in. Su – Tong reports an error
su: cannot set user id: Resource temporarily unavailable
Most people on the Internet say that the number of user processes is limited, but only 122 processes (PS – EF | WC – L) can be found on the whole server. But according to the following operation modification is really feasible, but also confused
Nproc (maximum number of processes available to a single user)
The problem can be solved by modifying the nproc value of the system
1. Add the following two lines to the limit file
vi /etc/security/limits.conf
* soft nproc 10240
* hard nproc 10240
2. Modify the default value of nproc from 1024 to 10240
[ root@cn-collect01 ~]# vi /etc/security/limits.d/90-nproc.conf
* soft nproc 10240
Similar Posts:
- [Solved] JVM Error: Failed to write core dump. Core dumps have been disabled.(jar was Forced to Exit)
- [Solved] Elasticsearch Startup Error: node validation exception
- [Solved] MYSQL Error: [Warning] Changed limits: max_open_files: 1024
- [Solved] Linux Start solr Server Error: Your open file limit is currently 1024
- Nginx report 500 internal server error
- [Solved] Linux Start solr Error: Your Max Processes Limit is currently 31202. It should be set to 65000 to avoid operational disruption.
- Error: too many open files [How to Solve]
- [Solved] ERROR: bootstrap checks failed memory locking requested for elasticsearch process but memory is not locked
- [Solved] Mariadb Start Error: Could not increase number of max_open_files to more than 1024 (request: 5035)
- Elasticsearch startup error, bootstrap checks failed [How to Solve]