I’m having a node where main disc is close to being used
I noticed the existence of a core file, that is quite large, around 4 gigs
ubuntu@ip-10-35-142-176:/opt/couchbase/var/lib/couchbase$ ls -all -h
drwxr-xr-x 6 couchbase couchbase 4.0K Nov 18 07:14 .
drwxr-xr-x 4 couchbase couchbase 4.0K Oct 2 08:20 ..
drwxr-xr-x 2 couchbase couchbase 4.0K Nov 15 10:49 config
-rw-r----- 1 couchbase couchbase 4.0G Nov 17 20:03 core
Is that a kind of dump file from a crash? Can it be deleted or moved without any problems
Yes this is probably a dump from a process crash. Hard to say what this the source of it without analysis.
You can delete it but it would be nice to see what is causing this.
So you can
- run “file” against each of them so we can see what process it’s from
- then, based on that, we may want to get him to run gdb to extract the backtrace and file an issue
gdb path_to_binary core_file
thread apply all bt
Also provide some detailed information about your environment such as:
- OS and hardware
- Couchbase version and configuration
Thanks, will try to follow the steps and post result here
Ok, I did ran file and got the following output
/mnt/dump-files/core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from ‘/opt/couchbase/lib/erlang/erts-5.8.5/bin/beam.smp -A 16 -sbt u -P 327680 -K tru’
Are you interested in more info
I’m running Version: 2.2.0 enterprise edition (build-821) on aws large instances