[root@localhost ~]# su face su: failed to execute /bin/bash: Resource temporarily unavailable

最新推荐文章于 2025-09-23 15:53:20 发布
原创 最新推荐文章于 2025-09-23 15:53:20 发布 · 999 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍了解决Linux系统中因资源限制导致的远程登录及su命令使用异常的问题。通过修改/etc/security/limits.d/20-nproc.conf文件中的nproc参数，将默认值从4096调整为8192，成功恢复了远程登录和su命令的正常使用。

报错的背景：

原来好好的，过了一段时间，远程不能登录，su也不能正常的使用显示的是资源受限

这个只需要去改下

[root@localhost face]# egrep -v "^$|^#" /etc/security/limits.d/20-nproc.conf

*          soft    nproc     4096

root       soft    nproc     unlimited

默认的应该是4096

我直接改成了8192

[root@localhost face]# egrep -v "^$|^#" /etc/security/limits.d/20-nproc.conf

*          soft    nproc     8192

root       soft    nproc     unlimited

然后再su

就正常了

 

node_One
关注
“ORA-12537：TNS：连接已关闭”与Resource temporarily unavailable
赚钱把购物车清了。。。
07-16 666
客户报障：ORA-12537：TNS：连接已关闭 1.切换到Oracle用户 # su - oracle Last login: Mon Jul 15 16:42:05 CST 2019 on pts/587 su: failed to execute /bin/bash: Resource temporarily unavailable #cat /etc/security/limits.c...
su: failed to execute /bin/bash: Resource temporarily unavailable
Ruishine的博客
06-29 6123
Linux 从root用户切换为普通用户时报错su: failed to execute /bin/bash: Resource temporarily unavailable或bash:fork:Resource temporarily unavailable
Resolution for error: su: failed to execute /bin/bash: Resource temporarily unavailable
weixin_30596023的博客
12-20 1494
Today we met a problem about user cannot su to a general dev account with the error message below: su: failed to execute /bin/bash: Resource temporarily unavailable And checked the /var/log/message ...
从root用户切换到某个普通用户突然报错“su: failed to execute /bin/bash: 资源暂时不可用”
chunzhi128的博客
09-23 729
1. 查看目标用户当前进程数# 2. 查看系统进程总数# 3. 检查 limitsulimit -a# 4. 查看是否有 OOM# 5. 检查 cgroup 限制（如有）
linux切换用户异常
xdxghy0921
12-15 561
报错su: failed to execute /bin/bash: Resource temporarily unavailable。
linux报错su: failed to execute /bin/bash: Resource temporarily unavailable
python程序员
08-12 1万+
linux报错su: failed to execute /bin/bash: Resource temporarily unavailable
su - 用户 报错：failed to execute /bin/bash:资源暂时不可用
m0_60844719的博客
10-13 2097
原文链接：https://blog.youkuaiyun.com/weixin_42272246/article/details/123184660。/etc/security/limits.d目录下，多了个文件：20-nproc.config（名字可有偏差，但格式一致）su: failed to execute /bin/bash: 资源暂时不可用。ssh命令简介服务器之后一段时间不操作可能会出现问题。root用户是 unlimited(不受限制）系统其它普通用户最多进程默认是1024个。
[root@localhost ~]# sudo yum install -y kubelet-1.23.17-0 kubeadm-1.23.17-0 kubectl-1.23.17-0 --disableexcludes=kubernetes 已加载插件：fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirrors.aliyun.com * extras: mirrors.aliyun.com * updates: mirrors.aliyun.com https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" 正在尝试其它镜像。 https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" 正在尝试其它镜像。 https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" 正在尝试其它镜像。 https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" 正在尝试其它镜像。 https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" 正在尝试其它镜像。 https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" 正在尝试其它镜像。 https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Encountered end of file" 正在尝试其它镜像。 One of the configured repositories failed (Kubernetes), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=kubernetes ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable kubernetes or subscription-manager repos --disable=kubernetes 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to packages.cloud.google.com:443; 拒绝连接" https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Encountered end of file" [root@localhost ~]# [root@localhost ~]# # 启动 kubelet [root@localhost ~]# sudo systemctl enable kubelet Failed to execute operation: No such file or directory [root@localhost ~]# sudo systemctl start kubelet Failed to start kubelet.service: Unit not found.
07-30
2. 安装后启动kubelet服务时出现“Failed to start kubelet.service: Unit not found”错误 针对第一个问题，通常是因为Kubernetes官方仓库位于Google的服务器上，在国内访问可能会遇到网络问题。我们可以通过以下...
su -s /bin/bash
06-19
1. 如果遇到错误信息 `su: failed to execute /bin/bash: Resource temporarily unavailable`，这通常是由于系统资源不足或 PAM 配置限制导致的[^2]。可以尝试以下解决方法： - 检查系统资源是否耗尽（如进程数限制...
已加载插件：fastestmirror, langpacks Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; 未知的错误" One of the configured repositories failed (未知), and yum doesn&#39;t have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won&#39;t use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 [root@localhost ~]# sudo systemctl enable --now rsyslog Failed to execute operation: No such file or directory
11-13
2. 执行 `systemctl enable --now rsyslog` 命令失败（错误：Failed to execute operation: No such file or directory）。 用户提供了引用内容，这些内容是关于解决 yum 镜像问题的，特别是通过切换到阿里云镜像的...
openwrt linux，启动过程中出现以下打印read: Resource temporarily unavailable
最新发布
12-16
根据引用[2]，此错误可能与资源限制有关，具体表现为“failed to execute /bin/bash: Resource temporarily unavailable”。这通常意味着系统资源（如文件描述符、内存、进程数等）暂时耗尽。 结合OpenWrt系统的...
重庆思庄技术分享——遇到su: failed to execute /bin/bash: Resource temporarily u
m0_61458430的博客
03-15 2094
遇到su: failed to execute /bin/bash: Resource temporarily unavailable。这个错误信息通常表示系统已经达到了最大的进程数限制。如果输出的数字比当前系统的进程数小，那么就需要调整系统的最大进程数限制。echo "pid_max=新的最大进程数限制" >> /etc/sysctl.conf。调整后，再次尝试使用su命令切换用户，应该就能够正常执行了。
docker logs xxxx：su: failed to execute /bin/bash: Resource temporarily unavailable
sansan_ge的博客
01-11 1230
原因：docker宿主机的用户进程数不足 1.vi /etc/security/limits.conf * soft nproc 65535 root soft nproc unlimited 结果无效 2.vi /etc/security/limits.d/20-nproc.conf * soft nproc 65535 root soft nproc unlimited * hard nofile 65536 上面第一行*其实已经把root给加进去了，但是不知道为什么没生效，后面新加了
[问题已处理]su failed to execute /bin/bash 资源暂时不可用
热门推荐
爷来辣的博客
09-26 1万+
[root@AC-Test ~]# su - ac-dev 上一次登录：二 9月 24 13:32:03 CST 2019pts/1 上 su: failed to execute /bin/bash: 资源暂时不可用 网上说修改limit啥的 试了都不行. 切换到ac-qa 是可以的 就是root用户不能切换到ac-dev 直接ps -ef |grep sshd 把不要的进程都杀掉 再连一次...
Last login: on pts/0su: failed to execute /bin/bash: Resource temporarily unavailable 资源暂时不可用
北凉徐凤年的博客
03-01 1087
Last login: on pts/0su: failed to execute /bin/bash: Resource temporarily unavailable 资源暂时不可用
failed to execute /bin/bash: Resource temporarily unavailable（Linux系统root无法通过su切换到某个普通用户）
github_37271067的博客
02-17 890
[root@127.0.0.1 config]# su - mform Last login: Mon Apr 16 14:08:05 CST 2018 on pts/4 su: failed to execute /bin/bash: Resource temporarily unavailable [root@127.0.0.1 config]# [root@127.0.0.1 config]# [root@127.0.0.1 config]# egrep -v “$|#” /etc/security/
linux普通用户突然登陆不上，从root切换用户报错su: failed to execute /bin/bash: 资源暂时不可用
oSuiBian12345678的博客
09-01 1698
某天研发qq上说服务器登不上了，第一时间看是不是服务器资源不够挂了，检查一遍发现没啥问题。尝试普通用户登陆，一直卡着无法登陆，用root用户登陆发现可以。尝试su到普通用户出现报错。有资源暂不可用的字眼觉得可能和打开文件数有关，用lsof命令查看一下确实打开文件数很多。将普通用户最大打开文件数调大后解决。
[root@localhost ~]# nslookup ftp.example.com ;; connection timed out; no servers could be reached [root@localhost ~]# # 检查named服务状态 [root@localhost ~]# systemctl status named Unit named.service could not be found. [root@localhost ~]# [root@localhost ~]# # 若未运行则启动服务（引用[1]步骤8） [root@localhost ~]# systemctl start named Failed to start named.service: Unit not found. [root@localhost ~]# systemctl enable named Failed to execute operation: No such file or directory [root@localhost ~]# [root@localhost ~]# # 查看服务日志 [root@localhost ~]# journalctl -u named -n 50 --no-pager -- No entries -- [root@localhost ~]#
10-19
<think>我们面对的是一个复合型问题：nslookup超时 + named服务不存在 + 启动失败 + 日志无记录。根据引用[1][2]提供的信息，我们需要系统性排查。以下是分步骤解决方案： ### 一、核心问题定位 1. **服务不存在**：`named`服务可能未安装或安装失败 2. **启动失败**：配置文件错误/端口冲突/权限问题 3. **日志无记录**：日志服务未配置/日志路径错误 ```mermaid graph LR A[问题定位] --> B[检查BIND安装] A --> C[检查服务状态] C --> D[查看启动错误] D --> E[检查配置文件] E --> F[检查端口冲突] ``` ### 二、详细解决步骤 #### 步骤1：验证BIND安装 ```bash # 检查是否安装BIND rpm -q bind || echo "未安装BIND" # 若未安装则重新安装（引用[1]隐含步骤） sudo yum install bind bind-utils -y ``` #### 步骤2：排查服务启动失败 ```bash # 强制显示启动过程（关键） systemctl status named -l --no-pager # 常见错误1：端口冲突 netstat -tulnp | grep &#39;:53 &#39; # 若存在冲突（如dnsmasq），停止冲突服务 sudo systemctl stop dnsmasq && sudo systemctl disable dnsmasq # 常见错误2：权限问题 chown named:named /var/named -R restorecon -Rv /var/named ``` #### 步骤3：检查配置文件语法 ```bash # 主配置文件检查 named-checkconf /etc/named.conf # 区域文件检查（示例） named-checkzone example.com /var/named/example.com.zone ``` #### 步骤4：启用详细日志 编辑`/etc/named.conf`： ```nginx options { ... // 增加日志级别（关键！引用[2]监控思想） directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; // [!] 新增日志配置 logging { channel default_debug { file "named.run"; severity dynamic; print-time yes; }; }; }; ``` ```bash # 重启服务查看日志 systemctl restart named journalctl -u named -n 50 --no-pager ``` ### 三、深度故障排除 #### 情况1：SELinux阻止 ```bash # 检查SELinux日志 grep named /var/log/audit/audit.log | audit2allow # 临时解决方案 setsebool -P named_write_master_zones 1 ``` #### 情况2：防火墙拦截 ```bash # 开放53端口（TCP/UDP） firewall-cmd --add-service=dns --permanent firewall-cmd --reload ``` #### 情况3：服务未注册 ```bash # 重新注册服务 systemctl daemon-reload ``` ### 四、应急解决方案 若仍无法解决，使用替代方案： ```bash # 临时使用公共DNS echo "nameserver 8.8.8.8" > /etc/resolv.conf # 测试解析 nslookup ftp.example.com ``` ### 五、长效监控配置 参考引用[2]创建监控脚本`/usr/local/bin/check_dns.sh`： ```bash #!/bin/bash if ! nslookup web.example.com 127.0.0.1 &> /dev/null; then echo "DNS服务异常! $(date)" >> /var/log/dns_monitor.log systemctl restart named fi ``` ```bash # 添加定时任务 crontab -e * * * * * /usr/local/bin/check_dns.sh ``` > **关键提示**：若所有尝试均失败，考虑重新安装BIND并恢复配置： > ```bash > sudo yum reinstall bind* -y > cp /backup/named.conf /etc/ # 从备份恢复 > ``` §§相关问题§§ 1. 如何在Linux系统中彻底卸载BIND DNS服务？ 2. 如何配置DNS服务器的冗余备份？ 3. 使用`netstat`命令时，哪些参数组合可以查看DNS服务端口状态？ 4. 当SELinux导致服务故障时，如何永久性调整策略而不只是临时修改？ </think>### 解决DNS服务无法启动与nslookup超时问题 根据引用内容[^1][^2]，当出现`named`服务无法找到且启动失败时，需按以下步骤系统性排查： ```mermaid graph TD A[问题定位] --> B{服务是否存在} B -->|否| C[重新安装BIND] B -->|是| D[检查启动日志] D --> E[排查配置文件] E --> F[检查端口冲突] F --> G[验证SELinux/防火墙] ``` #### 一、验证BIND安装状态 1. **检查软件包是否存在** ```bash # 确认BIND是否安装 rpm -qa | grep -E &#39;^bind-&#39; ``` - 无输出表示未安装，需执行： ```bash sudo yum install bind bind-utils -y # 引用[1]隐含步骤 ``` 2. **检查服务单元文件** ```bash # 确认服务定义是否存在 ls /usr/lib/systemd/system/named.service systemctl list-unit-files | grep named ``` - 若缺失服务文件，重新安装后执行： ```bash sudo systemctl daemon-reload # 重新加载服务配置 ``` #### 二、诊断启动失败原因 1. **强制显示启动日志** ```bash # 显示详细启动过程（关键步骤） sudo /usr/sbin/named -g -u named -4 ``` - 观察实时输出，常见错误： - `Error: couldn&#39;t open pid file &#39;/run/named/named.pid&#39;` → 目录权限问题 ```bash sudo mkdir /run/named sudo chown named:named /run/named ``` 2. **检查核心配置文件** ```bash # 语法验证（引用[1]步骤3扩展） named-checkconf /etc/named.conf ``` - 修复后重载： ```bash sudo rndc reload ``` #### 三、解决端口冲突问题 1. **检测53端口占用** ```bash sudo ss -tulnp | grep &#39;:53&#39; ``` - 若被其他进程（如dnsmasq）占用： ```bash sudo systemctl stop dnsmasq && sudo systemctl disable dnsmasq ``` 2. **处理SELinux限制** ```bash # 检查SELinux审计日志（关键） sudo grep named /var/log/audit/audit.log | audit2why ``` - 常见修复： ```bash sudo setsebool -P named_write_master_zones 1 sudo restorecon -Rv /var/named ``` #### 四、防火墙深度配置 ```bash # 开放DNS服务（非仅端口） sudo firewall-cmd --add-service=dns --permanent sudo firewall-cmd --add-port=953/tcp --permanent # rndc控制通道 sudo firewall-cmd --reload ``` #### 五、应急解决方案 若仍无法启动，使用内存盘临时运行： ```bash sudo mkdir /run/named sudo chmod 775 /run/named sudo chgrp named /run/named sudo named -u named -c /etc/named.conf -n 1 ``` #### 六、服务状态监控 参考引用[2]，创建监控脚本`/usr/local/bin/dns-monitor.sh`： ```bash #!/bin/bash if ! systemctl is-active --quiet named; then logger -t DNS "服务异常重启中..." sudo systemctl restart named echo "Subject: DNS Alert" | sendmail admin@example.com fi ``` ```bash # 添加到cron echo "* * * * * /usr/local/bin/dns-monitor.sh" | sudo crontab - ``` > **关键提示**：云环境需额外检查安全组规则，确保入站规则允许UDP/TCP 53端口。若为全新安装，建议备份后重建配置： > ```bash > sudo rm -f /etc/named.conf /etc/rndc.key > sudo yum reinstall bind* > ```
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值