Can i clean out /home/coredump?

[brononius]

Hey,

I've noticed that i've got about 5gig of coredumps in /home/coredump.
Most files are from days ago.

I'm wondering if i can safetly remove these files.
Or will this be done automaticly?

[l3mce]

You can remove them. I would be curious what is crashing gratuetously enough to create them...

[brononius]

Me too.   

I think it's related to the IP-camera issue.

But since i'm using a small SSD card of 60GB for my os, i'm trying to keep the diskspace as healthy as possible.
So the dumps will be dumped. Thanks!

[brononius]

Seems it has nothing to do with the IP-camera's. They're removed since yesterday (+/-10h), and the dumps started again today.
The server dies again almost each minute... And a new corefile of 500MB (?) is created each minute...

What's the best way to investigate this?


In my /var/log/pluto folder, i've got following files:

ls -lh d*

-rw-r--r-- 1 root root 1.6K 2012-12-14 10:50 deaths
-rw-r--r-- 1 root root  29K 2012-12-14 10:40 device.2012-12-14-10:40:21
-rw-r--r-- 1 root root  29K 2012-12-14 10:41 device.2012-12-14-10:41:32
-rw-r--r-- 1 root root  29K 2012-12-14 10:42 device.2012-12-14-10:42:36
-rw-r--r-- 1 root root  29K 2012-12-14 10:43 device.2012-12-14-10:43:40
-rw-r--r-- 1 root root  29K 2012-12-14 10:45 device.2012-12-14-10:45:07
-rw-r--r-- 1 root root  29K 2012-12-14 10:46 device.2012-12-14-10:46:40
-rw-r--r-- 1 root root  29K 2012-12-14 10:47 device.2012-12-14-10:47:40
-rw-r--r-- 1 root root  29K 2012-12-14 10:49 device.2012-12-14-10:49:03
-rw-r--r-- 1 root root  252 2012-12-14 09:56 dhcp_pnp.log
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_153_153
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_162_162
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_164_164
-rw-r--r-- 1 root root  272 2012-12-14 10:49 died_166_166
-rw-r--r-- 1 root root  238 2012-12-14 10:50 died__DCERouter

ls -lh Spaw*

--ws--s--t 1 root root  0 2012-12-14 10:46 SpawnDaemon_SendVoiceMailEvent.sh_10261.log
--ws--s--t 1 root root  0 2012-12-14 10:46 SpawnDaemon_SendVoiceMailEvent.sh_10263.log
--ws--s--t 1 root root  0 2012-12-14 10:47 SpawnDaemon_SendVoiceMailEvent.sh_13631.log
--ws--s--t 1 root root  0 2012-12-14 10:47 SpawnDaemon_SendVoiceMailEvent.sh_13633.log
--ws--s--t 1 root root  0 2012-12-14 10:43 SpawnDaemon_SendVoiceMailEvent.sh_1600.log
--ws--s--t 1 root root  0 2012-12-14 10:43 SpawnDaemon_SendVoiceMailEvent.sh_1618.log
--ws--s--t 1 root root  0 2012-12-14 10:49 SpawnDaemon_SendVoiceMailEvent.sh_17524.log
--ws--s--t 1 root root  0 2012-12-14 10:49 SpawnDaemon_SendVoiceMailEvent.sh_17526.log
--ws--s--t 1 root root  0 2012-12-14 10:41 SpawnDaemon_SendVoiceMailEvent.sh_26938.log
--ws--s--t 1 root root  0 2012-12-14 10:41 SpawnDaemon_SendVoiceMailEvent.sh_26940.log
--ws--s--t 1 root root  0 2012-12-14 10:42 SpawnDaemon_SendVoiceMailEvent.sh_30511.log
--ws--s--t 1 root root  0 2012-12-14 10:42 SpawnDaemon_SendVoiceMailEvent.sh_30513.log
--ws--s--t 1 root root  0 2012-12-14 10:45 SpawnDaemon_SendVoiceMailEvent.sh_6485.log
--ws--s--t 1 root root  0 2012-12-14 10:45 SpawnDaemon_SendVoiceMailEvent.sh_6487.log
--ws--s--t 1 root root  0 2012-12-14 10:46 Spawn_start-asterisk_10510.log
--ws--s--t 1 root root  0 2012-12-14 10:47 Spawn_start-asterisk_13803.log
--ws--s--t 1 root root  0 2012-12-14 10:49 Spawn_start-asterisk_17747.log
--ws--s--t 1 root root  0 2012-12-14 10:43 Spawn_start-asterisk_1790.log
--ws--s--t 1 root root  0 2012-12-14 10:41 Spawn_start-asterisk_27143.log
--ws--s--t 1 root root  0 2012-12-14 10:42 Spawn_start-asterisk_30623.log
--ws--s--t 1 root root  0 2012-12-14 10:45 Spawn_start-asterisk_6692.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10650.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10740.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10750.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10758.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10772.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10786.log
--ws--s--t 1 root root 22 2012-12-14 10:47 Spawn_storagedevices_10794.log
--ws--s--t 1 root root 22 2012-12-14 10:48 Spawn_storagedevices_14137.log
--ws--s--t 1 root root 22 2012-12-14 10:48 Spawn_storagedevices_14165.log
--ws--s--t 1 root root 22 2012-12-14 10:48 Spawn_storagedevices_14169.log
....

more deaths

Code: [Select]

Fri Dec 14 10:40:14 CET 2012 DCERouter died
Fri Dec 14 10:41:07 CET 2012 153 died
Fri Dec 14 10:41:07 CET 2012 164 died
Fri Dec 14 10:41:07 CET 2012 162 died
Fri Dec 14 10:41:08 CET 2012 166 died
Fri Dec 14 10:41:26 CET 2012 DCERouter died
Fri Dec 14 10:42:11 CET 2012 153 died
Fri Dec 14 10:42:12 CET 2012 164 died
Fri Dec 14 10:42:12 CET 2012 166 died
Fri Dec 14 10:42:12 CET 2012 162 died
...

And following corefiles:

ls -lh /home/coredump/1/

total 42M
-rw------- 1 root root 550M 2012-12-14 10:40 core_DCERouter_1355478014_11
-rw------- 1 root root 550M 2012-12-14 10:41 core_DCERouter_1355478085_6
-rw------- 1 root root 550M 2012-12-14 10:42 core_DCERouter_1355478149_11
-rw------- 1 root root 560M 2012-12-14 10:43 core_DCERouter_1355478214_11

[l3mce]

dcerouter log dmesg syslog would be where I started, and of course reading the dump

[brononius]

Problem with the log files is, to much info...
I went through some of them, but couldn't find any reason why the server dies. He just dies. The lines before are each time different things. Inputs of my eib installation, file operation scripts... For the moment, he runs now 2 days without any crash. I did remove a lot of stuff that was wrong in my eyes (the IP-cam things, motion wrapper, a disk that wasn't connected anymore, a diskless mediadirector that wasn't working like it should...). So i hope it has something to do with this.


How can i read the dump? Is this a kind of zip file?

[l3mce]

Problem with the log files is, to much info...
I went through some of them, but couldn't find any reason why the server dies. He just dies. The lines before are each time different things. Inputs of my eib installation, file operation scripts... For the moment, he runs now 2 days without any crash. I did remove a lot of stuff that was wrong in my eyes (the IP-cam things, motion wrapper, a disk that wasn't connected anymore, a diskless mediadirector that wasn't working like it should...). So i hope it has something to do with this.


How can i read the dump? Is this a kind of zip file?

You need to open them with a debugger... gdb for instance.

man gdb