You are not logged in.

Pages: 1

#1 2015-04-10 04:09:26

boes
Member
Registered: 2012-03-17
Posts: 28

[SOLVED]core dump file

hi, i've been struggling all day debugging my segfault application
after reading the wiki, it says core dump file should be generated using coredumpctl
well, the problem is after trying this, the system returns message "Cannot retrieve coredump from journal nor disk."

here's my terminal snippet

[root@ARCHHOME cuda]# ulimit -c   
unlimited
[root@ARCHHOME cuda]# coredumpctl list alphabet_index
TIME                            PID   UID   GID SIG PRESENT EXE
Fri 2015-04-10 10:25:11 WIB    7802  1000  1000  11   /home/user/workspace/cuda/alphabet_index
Fri 2015-04-10 10:27:30 WIB    7820  1000  1000  11   /home/user/workspace/cuda/alphabet_index
Fri 2015-04-10 10:28:58 WIB    7827     0     0  11   /home/user/workspace/cuda/alphabet_index
Fri 2015-04-10 10:37:54 WIB    7970     0     0  11   /home/user/workspace/cuda/alphabet_index
Fri 2015-04-10 10:38:12 WIB    7973     0     0  11   /home/user/workspace/cuda/alphabet_index
Fri 2015-04-10 10:56:19 WIB    8605  1000  1000  11   /home/user/workspace/cuda/alphabet_index
Fri 2015-04-10 10:56:54 WIB    8610     0     0  11   /home/user/workspace/cuda/alphabet_index
[root@ARCHHOME cuda]# coredumpctl -o alphabet_index.core dump alphabet_index
           PID: 8610 (alphabet_index)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Fri 2015-04-10 10:56:52 WIB (8min ago)
  Command Line: ./alphabet_index -f LOCATIONS.sql -p PO
    Executable: /home/user/workspace/cuda/alphabet_index
 Control Group: /user.slice/user-1000.slice/session-c2.scope
          Unit: session-c2.scope
         Slice: user-1000.slice
       Session: c2
     Owner UID: 1000 (user)
       Boot ID: 7146b63ba3e74f23b71e07a84b219492
    Machine ID: f7e8b38bcb8c40f0b74e8f496ead90ea
      Hostname: ARCHHOME
       Message: Process 8610 (alphabet_index) of user 0 dumped core.
Cannot retrieve coredump from journal nor disk.
Coredump retrieval failed: No such file or directory

anybody knows what's wrong? why can't i generate core dump even after setting ulimit -c unlimited?

thanks in advance
PS: i think this is the correct subforum to ask about coredump, sorry if not

Last edited by boes (2015-04-11 10:30:04)

Offline

#2 2015-04-10 07:43:45

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,283

Re: [SOLVED]core dump file

On my machine it seems to work:

ewaller@odin ~ 1005 %coredumpctl list
No coredumps found.
ewaller@odin ~ [1]1006 %cd devel/C/crashGen 
ewaller@odin ~/devel/C/crashGen 1007 %ll
total 16
-rwxr-xr-x 1 ewaller users 8175 May 23  2014 crashme
-rw-r--r-- 1 ewaller users  234 May 23  2014 crashme.c
-rw-r--r-- 1 ewaller users  209 May 23  2014 crashme.c~
ewaller@odin ~/devel/C/crashGen 1008 %./crashme 
This should crash as we are about to write 1 to address 0
zsh: segmentation fault (core dumped)  ./crashme
ewaller@odin ~/devel/C/crashGen [139]1009 %coredumpctl 
TIME                            PID   UID   GID SIG PRESENT EXE
Fri 2015-04-10 00:32:40 PDT   14771  1000   100  11 * /home/ewaller/devel/C/crashGen/crashme
ewaller@odin ~/devel/C/crashGen [1]1012 %coredumpctl -o crashme.core dump crashme
           PID: 14771 (crashme)
           UID: 1000 (ewaller)
           GID: 100 (users)
        Signal: 11 (SEGV)
     Timestamp: Fri 2015-04-10 00:32:40 PDT (4min 39s ago)
  Command Line: ./crashme
    Executable: /home/ewaller/devel/C/crashGen/crashme
 Control Group: /user.slice/user-1000.slice/session-c6.scope
          Unit: session-c6.scope
         Slice: user-1000.slice
       Session: c6
     Owner UID: 1000 (ewaller)
       Boot ID: fa73e57f8d9544aab415ddd15ab48fc8
    Machine ID: 78170aeea466aef82a0611e20000059c
      Hostname: odin
      Coredump: /var/lib/systemd/coredump/core.crashme.1000.fa73e57f8d9544aab415ddd15ab48fc8.14771.1428651160000000.lz4
       Message: Process 14771 (crashme) of user 1000 dumped core.
More than one entry matches, ignoring rest.
ewaller@odin ~/devel/C/crashGen 1013 %ll
total 252
-rw-r--r-- 1 ewaller users      0 Apr 10 00:35 alphabet_index.core
-rwxr-xr-x 1 ewaller users   8175 May 23  2014 crashme
-rw-r--r-- 1 ewaller users    234 May 23  2014 crashme.c
-rw-r--r-- 1 ewaller users    209 May 23  2014 crashme.c~
-rw-r--r-- 1 ewaller users 241664 Apr 10 00:37 crashme.core
ewaller@odin ~/devel/C/crashGen 1014 %gdb -core=crashme.core 
GNU gdb (GDB) 7.9
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
/home/ewaller/.gdbinit:1: Error in sourced command file:
Undefined command: "".  Try "help".
[New LWP 14771]
Core was generated by `./crashme'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000400594 in ?? ()
(gdb) l
No symbol table is loaded.  Use the "file" command.
(gdb) q
ewaller@odin ~/devel/C/crashGen 1015 %cat crashme.c

#include <stdlib.h>
#include <stdio.h>

int main (int argc, char ** argv)
{
  int *foo = NULL;
  char x;
  printf("This should crash as we are about to write %i to address %i",argc,foo);
  x=getchar();
  *foo = argc;  /* Boom ! */
}
ewaller@odin ~/devel/C/crashGen 1016 %

Last edited by ewaller (2015-04-10 07:45:02)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2015-04-10 09:21:48

boes
Member
Registered: 2012-03-17
Posts: 28

Re: [SOLVED]core dump file

well, i have no idea what's wrong with my system
for a workaround, i found that modifying file 

/proc/sys/kernel/core_pattern

content with 

core

will dump segfault to core.<PID> in the working directory, instead of sending it to journald

Offline

#4 2015-04-10 13:15:45

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED]core dump file

Hi boes,

boes wrote:

well, i have no idea what's wrong with my system

by any chance is your journal corrupted? What does the following command say?

journalctl --verify

-- edit: can you also post the status of the journald service?

systemctl status systemd-journald.service

Last edited by mauritiusdadd (2015-04-10 13:18:43)

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

#5 2015-04-11 01:42:51

boes
Member
Registered: 2012-03-17
Posts: 28

Re: [SOLVED]core dump file

[boes@ARCHHOME ~]$ systemctl status systemd-journald.service
* systemd-journald.service - Journal Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled)
   Active: active (running) since Sat 2015-04-11 00:55:58 WIB; 7h ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 166 (systemd-journal)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-journald.service
           `-166 /usr/lib/systemd/systemd-journald
[boes@ARCHHOME ~]$ journalctl --verify
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119fc5677806-76e042b18e0fa517.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119fc5677806-76e042b18e0fa517.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-000000000006e0b1-00051347ae39da24.journal:38f960 (of 16777216 bytes, 22%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-000000000006e0b1-00051347ae39da24.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000072d5c-00051347c4f20f31.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000072d5c-00051347c4f20f31.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119f21a36c26-2c16d24fae5e9532.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119f21a36c26-2c16d24fae5e9532.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000736c1-00051347c8093d78.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000736c1-00051347c8093d78.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/system@000500cf3b3a9ec0-8793aa8681f892d0.journal~:38f960 (of 16777216 bytes, 22%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/system@000500cf3b3a9ec0-8793aa8681f892d0.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000416f1-000513470f1da137.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000416f1-000513470f1da137.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@bea5aa3a69f44775b1c3ed5726a8d2fd-000000000000045b-0004faf4e765d04f.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@bea5aa3a69f44775b1c3ed5726a8d2fd-000000000000045b-0004faf4e765d04f.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-000000000007056b-00051347b95d31cc.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-000000000007056b-00051347b95d31cc.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00050e3c02b9fff2-a429664474f25977.journal~:38f960 (of 25165824 bytes, 14%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00050e3c02b9fff2-a429664474f25977.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000722e1-00051347c20f6873.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000722e1-00051347c20f6873.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@879b077ac2074b709c1eec1eff5594bb-00000000000b0170-00051022282149e5.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@879b077ac2074b709c1eec1eff5594bb-00000000000b0170-00051022282149e5.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/system@0004faf48a1bd50e-0c33edc9026d8290.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/system@0004faf48a1bd50e-0c33edc9026d8290.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000074b99-00051347ce444d80.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000074b99-00051347ce444d80.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005067b6c4bf4a0-a59a177f16039639.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005067b6c4bf4a0-a59a177f16039639.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@000506a7ad6cc8fb-6536de4605e9abb3.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@000506a7ad6cc8fb-6536de4605e9abb3.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00050f092bf3bfd3-4b1998031a0b511e.journal~:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00050f092bf3bfd3-4b1998031a0b511e.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000029c31-0005131e12c803b8.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000029c31-0005131e12c803b8.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000071923-00051347bf0fc75d.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000071923-00051347bf0fc75d.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119f33ccb735-10c80e62d4be3253.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119f33ccb735-10c80e62d4be3253.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000000470-000511ee49201c36.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000000470-000511ee49201c36.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000057bed-000513475a12ead4.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000057bed-000513475a12ead4.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000071034-00051347bc160566.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-0000000000071034-00051347bc160566.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@b5a14f1703174a23a2a58d8327c833c7-000000000006e6dc-00050f092bf54dc2.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@b5a14f1703174a23a2a58d8327c833c7-000000000006e6dc-00050f092bf54dc2.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-000000000006fc80-00051347b661f11e.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-000000000006fc80-00051347b661f11e.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@09a1bdd5887744e688d573c931cd49cb-0000000000000427-000506a7ad6d4cbc.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@09a1bdd5887744e688d573c931cd49cb-0000000000000427-000506a7ad6d4cbc.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@09a1bdd5887744e688d573c931cd49cb-000000000000f939-00050d973e3bf352.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@09a1bdd5887744e688d573c931cd49cb-000000000000f939-00050d973e3bf352.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@000511ee491f4de5-ec361297e7f523fc.journal~:38f960 (of 67108864 bytes, 5%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@000511ee491f4de5-ec361297e7f523fc.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00051199e05b83db-46ef7baffde869b4.journal~:38f960 (of 25165824 bytes, 14%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00051199e05b83db-46ef7baffde869b4.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@b5a14f1703174a23a2a58d8327c833c7-000000000008fdc3-00051021b70fdd1c.journal:38f960 (of 134217728 bytes, 2%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@b5a14f1703174a23a2a58d8327c833c7-000000000008fdc3-00051021b70fdd1c.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00051022281ec81d-fef720a807e708ae.journal~:38f960 (of 67108864 bytes, 5%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@00051022281ec81d-fef720a807e708ae.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000740a5-00051347cb15ad23.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@e5b48418fa6e4dfd8657a263dc26f8fb-00000000000740a5-00051347cb15ad23.journal (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119fca66fc59-eafee698bf3138e4.journal~:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@0005119fca66fc59-eafee698bf3138e4.journal~ (No space left on device)
File corruption detected at /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@09a1bdd5887744e688d573c931cd49cb-0000000000008ee9-0005090d2e663013.journal:38f960 (of 8388608 bytes, 44%).
FAIL: /var/log/journal/f7e8b38bcb8c40f0b74e8f496ead90ea/user-1000@09a1bdd5887744e688d573c931cd49cb-0000000000008ee9-0005090d2e663013.journal (No space left on device)
[boes@ARCHHOME ~]$ df -h  
Filesystem      Size  Used Avail Use% Mounted on
dev             3.9G     0  3.9G   0% /dev
run             3.9G  9.0M  3.9G   1% /run
/dev/sdc3        48G   48G     0 100% /
tmpfs           3.9G   14M  3.9G   1% /dev/shm
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
tmpfs           3.9G   52K  3.9G   1% /tmp
/dev/sdc1       495M   29M  441M   7% /boot
/dev/sdc4        91G   22G   65G  25% /home
tmpfs           797M     0  797M   0% /run/user/997
tmpfs           797M  8.0K  797M   1% /run/user/1000
/dev/sdb3       369G   38G  331G  11% /run/media/boes/426204C86204C2A1
/dev/sda1       932G  498G  434G  54% /run/media/boes/309A97F59A97B636

you are right, some files on journal is corrupted. my root partition is full. didn't see that coming
i think this is the root problem.
thanks for the hints smile

Offline

#6 2015-04-11 05:24:29

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED]core dump file

That is the problem indeed: it seems that the presence of even only one corrupted file is enough to screw up coredumpctl, even if there is enough space left on the disk. The only solution is to remove all the file from the journal and restart the service systemd-journald (note however that this will delete also the core dumps).

Well, if you manage to get it working, please remember to mark this thread as [SOLVED] by editing the first post and prepending it to the title wink

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

Offline

Pages: 1

Board footer

Powered by FluxBB