Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Hi @MarcusMüller, thank you very much for answering. So rich answers, again, thanks very much. So I've began trying to import into SQLight, but I was taking long and as it doesn't outputs progress I got a SSH broken-pipe. I got interested about implementing a distinct counter my self. Think we could add a how to check for whom killed the process to your answers, that's will make it so complete. Please take a look at the updated I've made into the question. Again thank you very much so far. Commented Apr 10, 2022 at 20:46
  • 6
    But I told you what killed your process in the first sentence: it's the out-of-memory killer. Other things don't randomly kill processes. That's how I found out: elimination of other options and experience. (also the comments under your question indicate you need to read the system log, dmesg and/or journalctl -xe.) Commented Apr 10, 2022 at 21:03
  • Comments are not for extended discussion; this conversation has been moved to chat. Commented Apr 13, 2022 at 16:12