Is there any solution for service start after OOM-KILL

[akadi81]

I found that sometime mariadb is killed by OOM-KILL, even there are about 10 GB free RAM… weird…
I just want that the killed service to be restarted automatically. Does hestia have a solution for that? Sould i use mmonit or something like that?

Thank you.

[caos30]

Here a user has solved it with a very simple bash script:

SystemD auto restart services (Debian, Nginx only)

Here is my code. I kept finding that my service would abend. I have this running every minute now, and it will check the service start if it’s not running send me an email if it’s not running #!/bin/bash # Variables LOG_FILE="/var/log/mariadb_service_monitor.log" SERVICE_NAME="mariadb" # Change this to "mariadb" if that's your service name # Log function log_message() { local MESSAGE="$1" echo "$(date +'%Y-%m-%d %H:%M:%S') - $MESSAGE" | tee -a "$LOG_FILE" } # Check service status …

But i’m exploring to use opensource monit software (it comes with ubuntu/debian repositories) which let automatically restart services consuming too much resources (CPU or RAm) based on a very simple text configuration files per service