Difference between revisions of "Cannot allocate memory"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | xz -9 file_to_compress | + | [[xz -9]] file_to_compress |
| + | [[journalctl -r]] | ||
| + | Jun 09 05:18:59 server1 [[nagios3]][1113]: Warning: The check of service 'Current Load' on host 'localhost' could not be performed due to a fork() error: 'Cannot allocate memory'. The check will be rescheduled. | ||
| − | [[journalctl -r]] | grep oom | + | |
| + | [[journalctl -r]] | [[grep oom]] | ||
{{OOM}} | {{OOM}} | ||
Latest revision as of 05:59, 9 June 2024
xz -9 file_to_compress
Jun 09 05:18:59 server1 nagios3[1113]: Warning: The check of service 'Current Load' on host 'localhost' could not be performed due to a fork() error: 'Cannot allocate memory'. The check will be rescheduled.
journalctl -r | grep oom
OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s), systemd-oomd, OOMKilled, oom-killer, memcpy, sar -r, Exit code: 137
Advertising:
