Failed to start kesl astra linux

Failed to start kesl astra linux

Support for Business Products

Kaspersky Endpoint Security 11 for Linux

Kaspersky Endpoint Security for Linux: High protection without compromising performance
Extended technical support (MSA): High‑priority incident processing

kesl-supervisor won’t start after installation of Kaspersky Endpoint Security 11 for Linux on Astra Linux Common Edition

Issue

During the installation of Kaspersky Endpoint Security for Linux on Astra Linux Common Edition and start of the initial setup script kesl-setup.pl, in some cases the kesl-supervisor service may not start and you may get the following notification:

Error: Job for kesl-supervisor.service failed because the control process exited with error code. See «systemctl status kesl-supervisor.service» and «journalctl -xe» for details. kesl not started

The system log will show a message of the following type:

Dec 14 10:06:30 exampleserver systemd[1]: kesl-supervisor.service: Control process exited, code=exited status=255

Cause

The error occurs when using the installation package kesl-astra_11.2.0-4961_amd64.deb. It is intended for installation on Astra Linux Special Edition in the restricted application environment. When the application is installed from such installation package, the kesl-supervisor is started using the execaps utility, which is not included into Astra Linux Common Edition.

Читайте также:  Linux send file tcp

Solution

To install the application on Astra Linux Common Edition, use the installation package without the word “astra” in the name, for example:

What to do if the solution did not help

If the solution didn’t help, contact Kaspersky technical support by choosing the topic and filling out the form.

Источник

Failed to start kesl astra linux

Support for Business Products

Kaspersky Endpoint Security 11 for Linux

Kaspersky Endpoint Security for Linux: High protection without compromising performance
Extended technical support (MSA): High‑priority incident processing

kesl-supervisor won’t start after installation of Kaspersky Endpoint Security 11 for Linux on Astra Linux Common Edition

Issue

During the installation of Kaspersky Endpoint Security for Linux on Astra Linux Common Edition and start of the initial setup script kesl-setup.pl, in some cases the kesl-supervisor service may not start and you may get the following notification:

Error: Job for kesl-supervisor.service failed because the control process exited with error code. See «systemctl status kesl-supervisor.service» and «journalctl -xe» for details. kesl not started

The system log will show a message of the following type:

Dec 14 10:06:30 exampleserver systemd[1]: kesl-supervisor.service: Control process exited, code=exited status=255

Cause

The error occurs when using the installation package kesl-astra_11.2.0-4961_amd64.deb. It is intended for installation on Astra Linux Special Edition in the restricted application environment. When the application is installed from such installation package, the kesl-supervisor is started using the execaps utility, which is not included into Astra Linux Common Edition.

Solution

To install the application on Astra Linux Common Edition, use the installation package without the word “astra” in the name, for example:

Читайте также:  Linux kernel processor family

What to do if the solution did not help

If the solution didn’t help, contact Kaspersky technical support by choosing the topic and filling out the form.

Источник

Failed to start kesl astra linux

Support for Business Products

Kaspersky Endpoint Security 11 for Linux

Kaspersky Endpoint Security for Linux: High protection without compromising performance
Extended technical support (MSA): High‑priority incident processing

kesl-supervisor won’t start after installation of Kaspersky Endpoint Security 11 for Linux on Astra Linux Common Edition

Issue

During the installation of Kaspersky Endpoint Security for Linux on Astra Linux Common Edition and start of the initial setup script kesl-setup.pl, in some cases the kesl-supervisor service may not start and you may get the following notification:

Error: Job for kesl-supervisor.service failed because the control process exited with error code. See «systemctl status kesl-supervisor.service» and «journalctl -xe» for details. kesl not started

The system log will show a message of the following type:

Dec 14 10:06:30 exampleserver systemd[1]: kesl-supervisor.service: Control process exited, code=exited status=255

Cause

The error occurs when using the installation package kesl-astra_11.2.0-4961_amd64.deb. It is intended for installation on Astra Linux Special Edition in the restricted application environment. When the application is installed from such installation package, the kesl-supervisor is started using the execaps utility, which is not included into Astra Linux Common Edition.

Solution

To install the application on Astra Linux Common Edition, use the installation package without the word “astra” in the name, for example:

What to do if the solution did not help

If the solution didn’t help, contact Kaspersky technical support by choosing the topic and filling out the form.

Читайте также:  Astra linux special edition руководство администратора часть 2

Источник

Как запустить систему

photo_2019-03-27_16-54-48.jpg

Gave up waiting for suspend/resume device
/dev/sdc1: recovering journal
/dev/sdc1: clean, 172491/959104 files, 3835904/3840000 blocks
[[0;1;31mFAILED[0m] Failed to start kesl.
See ‘systemctl status kesl-supervisor.service’ for details.
[[0;32m OK [0m] Started Save/Restore Sound Card State.
[[0;32m OK [0m] Started PARSec events logging daemon.
[[0;32m OK [0m] Started Login Service.
[[0;32m OK [0m] Started LSB: Start some power management scripts.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;1;31mFAILED[0m] Failed to start Hostname Service.
See ‘systemctl status systemd-hostnamed.service’ for details.
[[0;32m OK [0m] Started VirtualBox Linux kernel module.
Starting vboxballoonctrl-service.service.
Starting vboxweb-service.service.
Starting vboxautostart-service.service.
[[0;32m OK [0m] Started vboxballoonctrl-service.service.
[[0;32m OK [0m] Started vboxweb-service.service.
[[0;32m OK [0m] Started vboxautostart-service.service.
[[0;32m OK [0m] Started Intitialize Parsec Subsystem.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting Permit User Sessions.
Starting OpenBSD Secure Shell server.
Starting Network Manager Wait Online.
[[0;32m OK [0m] Started Permit User Sessions.
Starting Network Manager Script Dispatcher Service.
Starting Hold until boot process finishes up.
Starting Terminate Plymouth Boot Screen.
[[0;32m OK [0m] Started The FLY get exec service.
[[0;32m OK [0m] Started The FLY login manager.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.

Источник

Оцените статью
Adblock
detector