S
S
Sergey2021-05-28 17:49:38
linux
Sergey, 2021-05-28 17:49:38

What are core files on the server?

I wanted to copy the certificate file from the local computer to the server with the command " scp -i "path_to_id_rsa path_to_my_certificate_file [email protected]:/etc/ssl/certs".
The server asked about confirming the connection via ssh. I entered yes and yes 2 times and the terminal hung - started something like
"
y
y
y
y
y
"
And so on ad infinitum. I reset the ctrl + C process. As a result, there are a bunch of core files on the server. And it turns out they are 20Mb on average.

What to do with this and what does it threaten?

60b102b3aef39386754429.png

Answer the question

In order to leave comments, you need to log in

4 answer(s)
S
shurshur, 2021-05-28
@shurshur

We look at any core file using the file utility:

$ file core.666
core.666: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/foobar', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0

Here you can see that the foobar process crashed.
Further, with the help of:
gdb -c core.666
you can study what really happened there, but this is already more difficult, especially without debugging data and in general with someone else's code.
All this is most likely not connected with the launch of scp, except that the core file remains from sshd itself.

S
Smithson, 2021-05-28
@Smithson

These are the files for debugging the falling process. Depending on the version of unix, they can be called core.ManyDigits or FallingSoftName.core
Feel free to delete, but I advise you to try to understand who produces them: something you have a lot of them (if this is not a stock for many years), at such a pace they can fill the entire disk.

A
Alexey Kharchenko, 2021-05-28
@AVX

The letters "y" after the second input of yes are the result of the "yes" command (yes, there is such a program!). Actually, by itself, it prints "y" to the terminal until it is killed.
But why she (or maybe not she?) Left so many files during the destruction, it is not clear. Maybe this is a feature of running yes under ssh, or something else fell.
You need to look at the dates of creation of these files using ls -l, and it will be clear whether they were created now (then 90% that yes is so buggy), or the dates are different, then you need to figure it out ...

C
CityCat4, 2021-05-28
@CityCat4

This something fell and the system created a file for analysis. Usually they are simply erased, but if there are so many of them, it would be better to see what process they belong to and what's the matter.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question