ulimit – 无法切换,ssh到特定用户:su:无法设置用户ID:资源暂时不可用?

前端之家收集整理的这篇文章主要介绍了ulimit – 无法切换,ssh到特定用户:su:无法设置用户ID:资源暂时不可用?前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
在/ var /日志/安全:
su: pam_keyinit(su-l:session): Unable to change UID to 500 temporarily
su: pam_keyinit(su-l:session): Unable to change UID to 500 temporarily
su: pam_unix(su-l:session): session opened for user adtech by root(uid=0)
su: pam_unix(su-l:session): session closed for user adtech

我想这是由每用户限制造成的,但与其他用户比较时没有什么不同.

这是针对adtech的ulimit -n:

[adtech@hmaster87 root]$ulimit -a
core file size          (blocks,-c) 0
data seg size           (kbytes,-d) unlimited
scheduling priority             (-e) 0
file size               (blocks,-f) unlimited
pending signals                 (-i) 192025
max locked memory       (kbytes,-l) 64
max memory size         (kbytes,-m) unlimited
open files                      (-n) 655360
pipe size            (512 bytes,-p) 8
POSIX message queues     (bytes,-q) 819200
real-time priority              (-r) 0
stack size              (kbytes,-s) 10240
cpu time               (seconds,-t) unlimited
max user processes              (-u) 1024
virtual memory          (kbytes,-v) unlimited
file locks                      (-x) unlimited

这个用于量子:

[quanta@hmaster87 ~]$ulimit -a
core file size          (blocks,-v) unlimited
file locks                      (-x) unlimited

adtech运行的进程数:

[root@hmaster87 ~]# ps -U adtech | wc -l
25

还有其他要检查的东西吗?

更新周六7月21日09:21:26 ICT 2012:

# getent passwd adtech
adtech:x:500:502::/home/adtech:/bin/bash

正如我在下面的评论中所说,我的同事发现了可能是罪魁祸首的过程:

adtech 12901 1 0 08:58? 00:00:00 /home/adtech/nexus/bin/../bin/jsw/linux-x86-64/wrapper /home/adtech/nexus/bin/../bin/jsw/conf/wrapper.conf包装.syslog.ident = nexus wrapper.pidfile = / home / adtech / nexus / bin /../ bin / jsw / linux-x86-64 / nexus.pid wrapper.daemonize = TRUE

adtech 12903 12901 1 08:58? 00:00:24 java -Dsun.net.inetaddr.ttl = 3600 -DbundleBasedir =. -Djava.io.tmpdir =./ tmp -DjettyContext = nexus.properties -DjettyContextIncludeKeys = bundleBasedir -DjettyPlexusCompatibility = true -Djava.library.path = bin / jsw / lib -classpath bin / jsw / lib / wrapper-3.2.3. jar:./ lib / plexus-classworlds-2.4.jar:./ conf / -Dwrapper.key = ejxHaBJASiFkAB8w -Dwrapper.port = 32000 -Dwrapper.jvm.port.min = 31000 -Dwrapper.jvm.port.max = 31999 -Dwrapper.pid = 12901 -Dwrapper.version = 3.2.3 -Dwrapper.native_library = wrapper -Dwrapper.service = TRUE -Dwrapper.cpu.timeout = 10 -Dwrapper.jvmid = 1 org.codehaus.plexus.classworlds.launcher.启动器./conf/jetty.xml

通过杀死这个过程,问题就会消失,但我们仍然不知道超出了哪个限制.

更新于12月15日星期六00:56:13 ICT 2012:

@ favadi的回答是正确的,但我在这里更新以防有人google这个帖子.

日志文件说:

jvm 1    | Server daemon died!
jvm 1    | java.lang.OutOfMemoryError: unable to create new native thread
jvm 1    |      at java.lang.Thread.start0(Native Method)
jvm 1    |      at java.lang.Thread.start(Thread.java:640)
jvm 1    |      at org.tanukisoftware.wrapper.WrapperManager.privilegedStopInner(WrapperManager.java:3152)
jvm 1    |      at org.tanukisoftware.wrapper.WrapperManager.handleSocket(WrapperManager.java:3797)
jvm 1    |      at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:4084)
jvm 1    |      at java.lang.Thread.run(Thread.java:662)

解决方法

最大用户进程(-u)1024可能太低.

请记住,进程和线程在一起计算.你可以使用ps -eLF | grep adtech | wc -l显示您当前的值.

原文链接:https://www.f2er.com/linux/401745.html

猜你在找的Linux相关文章