Hello
I’m running Debian 8 (Jessie).
Last week I updated the server and got an error:
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
Active: failed (Result: exit-code) since Thu 2018-06-07 17:47:02 EEST; 2min 1s ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 1907 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
Main PID: 1907 (code=exited, status=1/FAILURE)
Jun 07 17:47:02 kvm1.prado.lt systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=1/FAILURE
Jun 07 17:47:02 kvm1.prado.lt systemd[1]: Failed to start Apply Kernel Variables.
Jun 07 17:47:02 kvm1.prado.lt systemd[1]: Unit systemd-sysctl.service entered failed state.
then, I checked that the journald daemon has collected by using the journalctl command
journalctl -xn -- Logs begin at Thu 2018-04-19 01:13:40 EEST, end at Thu 2018-06-07 17:52:19 EEST. -- Jun 07 17:52:12 kvm1.prado.lt systemd-sysctl[2467]: Failed to write '262144' to '/proc/sys/vm/max_map_count': Permission denied Jun 07 17:52:12 kvm1.prado.lt systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=1/FAILURE Jun 07 17:52:12 kvm1.prado.lt systemd[1]: Failed to start Apply Kernel Variables. -- Subject: Unit systemd-sysctl.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-sysctl.service has failed. -- -- The result is failed. Jun 07 17:52:12 kvm1.prado.lt systemd[1]: Unit systemd-sysctl.service entered failed state. Jun 07 17:52:19 kvm1.prado.lt systemd[1]: Starting Apply Kernel Variables... -- Subject: Unit systemd-sysctl.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-sysctl.service has begun starting up. Jun 07 17:52:19 kvm1.prado.lt systemd[1]: Failed to reset devices.list on /system.slice/systemd-sysctl.service: No such file or directory Jun 07 17:52:19 kvm1.prado.lt systemd-sysctl[2506]: Failed to write '262144' to '/proc/sys/vm/max_map_count': Permission denied Jun 07 17:52:19 kvm1.prado.lt systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=1/FAILURE Jun 07 17:52:19 kvm1.prado.lt systemd[1]: Failed to start Apply Kernel Variables. -- Subject: Unit systemd-sysctl.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-sysctl.service has failed. -- -- The result is failed. Jun 07 17:52:19 kvm1.prado.lt systemd[1]: Unit systemd-sysctl.service entered failed state.
To load all configuration files manually, execute
sysctl --system
Once the command has been successfully executed, I found where the problem is.
* Applying /etc/sysctl.d/99-sysctl.conf ... * Applying /usr/lib/sysctl.d/elasticsearch.conf ... sysctl: permission denied on key 'vm.max_map_count' * Applying /etc/sysctl.conf ...
Now it’s time to open the file /usr/lib/sysctl.d/elasticsearch.conf where we will need to comment one line and problem should be solved.
We should change one line from
vm.max_map_count=262144
to
#vm.max_map_count=262144
Now we should to restart a service using the command
systemctl restart systemd-sysctl.service
And now we can make sure the service is up and running properly using the command
status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
Active: active (exited) since Wed 2018-06-13 22:29:05 EEST; 5s ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 31532 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
Main PID: 31532 (code=exited, status=0/SUCCESS)