core dumpsを開く[bash:ulimit:core file size:cannot modify limit:Operation not permitted]
Original Site: https://www.akadia.com/services/ora_enable_core.html
概要(Overview)
In most Linux Distributions core file creation is disabled by default for a normal user. However, it can be necessary to enable this feature for an application (e.g. Oracle). For example, if you encounter an ORA-7445 error in Oracle, then it must be possible to write a core file for the user «oracle».
To enable writing core files you use the ulimit command, it controls the resources available to a process started by the shell, on systems that allow such control.
If you try to enable writing core files, usually you run in the following problem. Normally SSH is used to logon to the server.
Now,try(not as user root)to change the core file size to unlimited
解決方法(Solution)
1.
現在のユーザーの下にあるshellプロファイルのいずれかを確認します.たとえば、
2.すべてのユーザー(グローバル)に対してCore Dump機能(Globally enable Core Dumps)を開く
このステップはrootユーザで操作する必要があります.通常、
3.現在のユーザーを登録して再登録して設定する(Logoff and Logon again and set ulimit)
まず、現在のユーザーがunlimitedであるかどうかを確認します.
0の場合core dumpファイルは出力されません.この場合、まずrootユーザで一度設定する(Try to set the limit as user root first)
さらにoracleなどの自分のユーザー名で、一度設定します(Now you can set ulimit also for user
Perhaps the last step number 3 is not necessary, but we have figured out, that this is the way which always work. The core file size limitation is usually also set in different configuration files. If you want to enable cores, you can uncomment them.
In/etc/profile (Redhat)
In/etc/init.d/functions (Redhat)
Now, from this current shell you can generate the core, so check ulimit before.
概要(Overview)
In most Linux Distributions core file creation is disabled by default for a normal user. However, it can be necessary to enable this feature for an application (e.g. Oracle). For example, if you encounter an ORA-7445 error in Oracle, then it must be possible to write a core file for the user «oracle».
To enable writing core files you use the ulimit command, it controls the resources available to a process started by the shell, on systems that allow such control.
If you try to enable writing core files, usually you run in the following problem. Normally SSH is used to logon to the server.
ssh oracle@ora-server
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 65536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16384
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Now,try(not as user root)to change the core file size to unlimited
ulimit -c unlimitedコマンドを使用してcoreファイルサイズを無限に設定する場合、問題が発生します.$ ulimit -c unlimited
-bash: ulimit: core file size: cannot modify limit: Operation not permitted
解決方法(Solution)
1.
ulimitの運転環境を確認する(Check Environment for ulimit)現在のユーザーの下にあるshellプロファイルのいずれかを確認します.たとえば、
$HOME/.bash_profileまたは$HOME/.bashrcファイルにulimit -c 0が設定されているかどうかを確認します.ファイルに設定がある場合は、行をコメントします.(The first step is to check, that you don’t set ulimit -c 0 in any shell configuration files for this user, for example in $HOME/.bash_profile or $HOME/.bashrc . Uncomment it if you have such an entry.) #
#Do not produce core dumps
#
#ulimit -c 0
2.すべてのユーザー(グローバル)に対してCore Dump機能(Globally enable Core Dumps)を開く
このステップはrootユーザで操作する必要があります.通常、
/etc/security/limits.confファイルで設定されます.(最後の行* soft core unlimited)(This must be done as user root,usually in/etc/security/limits.conf)#/etc/security/limits.conf
#
#Each line describes a limit for a user in the form:
#
# -
#
* soft core unlimited
3.現在のユーザーを登録して再登録して設定する(Logoff and Logon again and set ulimit)
まず、現在のユーザーがunlimitedであるかどうかを確認します.
ssh oracle@ora-server
$ ulimit -c
0
0の場合core dumpファイルは出力されません.この場合、まずrootユーザで一度設定する(Try to set the limit as user root first)
$ su -
$ ulimit -c unlimited
$ ulimit -c
unlimited
さらにoracleなどの自分のユーザー名で、一度設定します(Now you can set ulimit also for user
oracle)$ su - oracle
$ ulimit -c unlimited
$ ulimit -c
unlimited
Perhaps the last step number 3 is not necessary, but we have figured out, that this is the way which always work. The core file size limitation is usually also set in different configuration files. If you want to enable cores, you can uncomment them.
In/etc/profile (Redhat)
# No core files by default
# ulimit -S -c 0 > /dev/null 2>&1
In/etc/init.d/functions (Redhat)
# make sure it doesn't core dump anywhere unless requested
# ulimit -S -c ${DAEMON_COREFILE_LIMIT:-0} >/dev/null 2>&1
Now, from this current shell you can generate the core, so check ulimit before.
$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 65536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16384
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited