Stressapptest is getting killed on debian linux system

[supramod sp]

root:~/> stressapptest -s 120

2025/09/22-07:25:33(PDT) Log: Commandline - stressapptest -s 120

2025/09/22-07:25:33(PDT) Stats: SAT revision 1.0.9_autoconf, 64 bit binary

2025/09/22-07:25:33(PDT) Log: reproducible @ reproducible on Sat Jun 17 00:59:38 UTC 2023 from open source release

2025/09/22-07:25:33(PDT) Log: 1 nodes, 288 cpus.

2025/09/22-07:25:33(PDT) Log: Defaulting to 288 copy threads

2025/09/22-07:25:33(PDT) Log: Total 98269 MB. Free 91867 MB. Hugepages 0 MB. Targeting 93164 MB (94%)

2025/09/22-07:25:33(PDT) Log: Prefer plain malloc memory allocation.

2025/09/22-07:25:33(PDT) Log: Using mmap() allocation at 0x7fe9386b0000.

2025/09/22-07:25:33(PDT) Stats: Starting SAT, 93164M, 120 seconds

Killed

what could be the reason for this failure and any solution to fix this ?

[Nick Sanders]

The reason is probably that you don't have enough free memory. You can check for an OOM (out of memory) kill in /var/log/messages

2025/09/22-07:25:33(PDT) Log: Total 98269 MB. Free 91867 MB. Hugepages 0 MB. Targeting 93164 MB (94%)

Try specifying less memory (-M 90000) or turning off whatever else you are running concurrently to free up some memory.

--

---
You received this message because you are subscribed to the Google Groups "stressapptest-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stressapptest-di...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/stressapptest-discuss/b402d76d-089e-49df-953b-a6d05de6a758n%40googlegroups.com.