NSSM service eats 100% CPU
NSSM logstash service can cause a fatal CPU hungry outage in your clients unless you override the AppExit default value.
By default it comes as default 'Restart'
To change it to 'Stop service' you need to run the following command
nssm set logstash AppExit Default Exit
It will change the service definition as follow
By default it comes as default 'Restart'
To change it to 'Stop service' you need to run the following command
nssm set logstash AppExit Default Exit
It will change the service definition as follow
Other v
alid exit actions are:
Restart
Ignore
Exit
Suicide
Comments
Post a Comment