Killing CentOS was just the tip of iceberg
Every single bit of the source code in RHEL is available from the CentOS Stream repo.
You can also use CentOS Stream without any limits.
Individuals can use the Developer Sub to use RHEL for free.
There are other special programs (such as for Open Source projects that use RHEL as infrastructure) that allow the free use of RHEL.
It's probably time to add a moderation reason called "Removed - Untrue". I've come close this week.
More on reddit.comlinux - What killed my process and why? - Stack Overflow
CentOS Linux is dead—and Red Hat says Stream is “not a replacement”
CentOS 7 EOL is coming. What is your replacement?
"It is okay for Red Hat to paywall RHEL sources because they are open-source driven and give us distros for free"
The free distros RH give us:
Every single bit of the source code in RHEL is available from the CentOS Stream repo.
You can also use CentOS Stream without any limits.
Individuals can use the Developer Sub to use RHEL for free.
There are other special programs (such as for Open Source projects that use RHEL as infrastructure) that allow the free use of RHEL.
It's probably time to add a moderation reason called "Removed - Untrue". I've come close this week.
Rage baiting for clicks
If the user or sysadmin did not kill the program the kernel may have. The kernel would only kill a process under exceptional circumstances such as extreme resource starvation (think mem+swap exhaustion).
Try:
dmesg -T| grep -E -i -B100 'killed process'
Where -B100 signifies the number of lines before the kill happened.
Omit -T on Mac OS.
The problem was indeed memory related.
I've talked HostGator into increasing memory temporally while they performed yum update themselves, and now it's fixed.
Create a Linux Swap File temporarily , 1GB is enough for "yum update -y" https://linuxize.com/post/create-a-linux-swap-file/
Hi,
the date is coming (30 June 2024) and CentOS 7 will be EOL. Probably many have already migrated their server and other will run C7 for some months after the EOL and then migrate.
Have you already migrated?
What replaces CentOS 7 in your workplace?
Thank you in advance!!
Previous thread
If the kernel killed a process (because the system ran out of memory), there will be a kernel log message. Check in /var/log/kern.log (on Debian/Ubuntu, other distributions might send kernel logs to a different file, but usually under /var/log under Linux).
Note that if the OOM-killer (out-of-memory killer) triggered, it means you don't have enough virtual memory. Add more swap (or perhaps more RAM).
Some process crashes are recorded in kernel logs as well (e.g. segmentation faults).
If the processes were started from cron, you should have a mail with error messages. If the processes were started from a shell in a terminal, check the errors in that terminal. Run the process in screen to see the terminal again in the morning. This might not help if the OOM-killer triggered, because it might have killed the cron or screen process as well; but if you ran into the OOM-killer, that's the problem you need to fix.
Process Accounting could help here.
In brief:
apt-get install acct
Then try commands like:
lastcomm
sa
or on Ubuntu:
lastcomm -f /var/log/account/pacct
sa /var/log/account/pacct
See:
- http://tldp.org/HOWTO/Process-Accounting/pasetup.html
- http://tldp.org/HOWTO/Process-Accounting/misccommands.html
UPDATE
Strangely, the pacct file has information about exit status, but neither lastcomm nor sa seem to print it.
So as far as I can see, you'd have to write your own C program to access the information.
UPDATE 2
Here's a version that prints the exit code.
The last two fields are "S" for signaled and "E" for exited, followed by the signal number or exit status.
So in your case, you're probably looking for "S 15" meaning it got a SIGTERM.
sleep X mikel stdin 0.00 secs Fri Mar 25 20:15 S 15
Compared to "E 0" which means the process exited without an error.
true mikel stdin 0.00 secs Fri Mar 25 20:16 E 0
Only minimally tested.
- http://mikelward.com/software/lastcomm.exitcode.patch
- http://mikelward.com/software/lastcomm