ezzadin
asked on
CentOS 6.4 Core files
Hi,
I have installed CentOS 6.4 64bit few days ago and noticed that the hard drive got full within few days. I looked in /tmp folder and noticed lots of core.numbers files ie core.1111 core.32323
These files are being created every few seconds.
ulimit -c shows zero which basically means that no core file should be created.
I would like to know why these files are being created? Apparently I need to know the application that is creating this file before debugging.
And how do I stop these files from being created?
Thanks.
I have installed CentOS 6.4 64bit few days ago and noticed that the hard drive got full within few days. I looked in /tmp folder and noticed lots of core.numbers files ie core.1111 core.32323
These files are being created every few seconds.
ulimit -c shows zero which basically means that no core file should be created.
I would like to know why these files are being created? Apparently I need to know the application that is creating this file before debugging.
And how do I stop these files from being created?
Thanks.
ASKER
I did not find anything unusual here. Will you please post :
/etc/sysctl.conf
/var/log/messages
/etc/sysctl.conf
/var/log/messages
It seems that your system was configured to generate core dump files for crashes. I think we need to find what is causing crashes.
ASKER
Hi,
here is sysctl:
I didnt see anything is /var/log/messages.
I rebooted the system few minutes ago and it stopped creating the files...
here is sysctl:
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 0
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
# Controls the use of TCP syncookies
net.ipv4.tcp_syncookies = 1
# Disable netfilter on bridges.
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
# Controls the default maxmimum size of a mesage queue
kernel.msgmnb = 65536
# Controls the maximum size of a message, in bytes
kernel.msgmax = 65536
# Controls the maximum shared segment size, in bytes
kernel.shmmax = 68719476736
# Controls the maximum number of shared memory segments, in pages
kernel.shmall = 4294967296
I didnt see anything is /var/log/messages.
I rebooted the system few minutes ago and it stopped creating the files...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I actually had this box installed and configured in the office and had is running for few days then shut it down and moved it to our data-center and powered up.
The system started creating the dump file when it was powered up in the data-center, so as you mentioned maybe it just booted from rescue kernel and once the server was rebooted, it started normally.
In any case, thanks for your help.
The system started creating the dump file when it was powered up in the data-center, so as you mentioned maybe it just booted from rescue kernel and once the server was rebooted, it started normally.
In any case, thanks for your help.
You're welcome.
Will you post your dmsesg output here?
Cheers,
K.