Problem: When building Jenkins task, it was found that the target host could not be connected. After manually executing SSH command on the command line, an error was reported: Shell Request failed on channel 0
Cause: The number of system processes on the target host is too small to connect
Solution: need to modify the/etc/security/limits. D/20 – nproc. The values in the conf file, change the 4096 older, such as 65535
Cause: The number of system processes on the target host is too small to connect
Solution: need to modify the/etc/security/limits. D/20 – nproc. The values in the conf file, change the 4096 older, such as 65535
[zhangsan@note1 /]$ cat /etc/security/limits.d/20-nproc.conf
* soft nproc 4096
root soft nproc unlimited
Re-ssh, and you are done.
Read More:
- windows GitLab: PTY allocation request failed on channel 0
- When local git connects to github: PTY allocation request failed on channel 0
- subsystem request failed on channel 0 Couldn’t read packet: Connection reset by peer
- Centos8 solves SSH secure shell error algorithmic negotiation failures
- ansible Q&A: Failed to connect to the host via ssh: ssh_exchange_identification and Authentication or per
- Solve the problem of keyboard interactive authentication with the SSH2 server failed
- [Error resolution] paramiko.ssh_exception.SSHException: Error reading SSH protocol banner setting
- Solve the problem of shell script “syntax error near unexpected token `fi’”.
- Common shell (1): shell gets the current time stamp of the system
- An undetermined call to function ‘shell’: missing ‘. Stop. Problem encountered when using shell command in makefile
- In the HTML page request Ajax times 400 error, solve Yii submit post form 400 error, and Ajax post request 400 problem (example code)
- SSH write failed broken pipe
- Flask Request an extension before_request after_request errorhandler
- Cloning failed using an SSH key for authentication
- Failed to restart ssh.service: Unit not found.
- IIS “Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long.”
- Rsync: failed to exec SSH: no such error in remote Rsync
- SSH Remote ulimit does not work
- Centos Failed to Modify the port of SSH: error: Bind to port 27615 on 0.0.0.0 failed: Permission denied.
- Solve the problem of request method ‘get’ not supported