ubuntu 12.04 - Process Core dumps are not created after crash -
I have configured the system configuration to make process core dumps.
Below are my configurations.
/etc/sysctl.conf kernel.core_uses_pid = 1 kernel.core_pattern = /var/core/core.%e.%p.%h.%t fs.suid_dumpable = 2 / etc / Security / Limit.conf * Soft Core Unlimited Root Soft Core Unlimited
Here are the steps I'm following to process the process.
1) I have restarted the Mysql service and executed command " kill -s SEGV
" then I have a core dump file in the / var / core space Found
<2> Then I have started my service mysql "/ etc / init.d / mysql start"
or "mysql service Start "
. Now if I give " kill -s SEGV
" then the core dump file is not being created.
3) To recover a crash file, I only have to restart the mysql service if I use " Can anyone please help me solve this? First of all, you can confirm that the core dumps are disabled for the MySQL process to run: "soft" limit is one, in this case zero means that the core dump is disabled Are there. Limitations start by interactively / etc / security / Limits.conf only apply to programs by default. If you are lucky, you can enable coredumps for your current shell and restart it using the daemon. .d script: As you can see, it works for MySQL on my system. Please note that this will not work for applications like Apache, which calls internally to disable the original dump, not init.d script which uses upstart. kill -s SEGV
# cat / proc / `pidof -s mysqld` / limits | Egrep '(range | core)' border soft limit hard limit units maximum core file size 0 unlimited bytes
# ulimit -c unlimited # /etc/init.d/mysql restart * mysql database server mysqld block [ok] * mysql database server for mysqld start [ok] * for Check tables that require upgrades, are corrupted or not cleaned off # cat / proc / `pidof -s mysqld` / limits | Egrep '(range | core)' border soft border hard limit units max core file size unlimited bytes
Comments
Post a Comment