Jump to content

Recommended Posts

В KSC не включена защита. Непосредственно на машине пишет

"SELinux is preventing /usr/bin/mandb from getattr access on the file /var/opt/kaspersky/kesl/10.1.0.5960_1526309614/usr/local/share/man5/kesl-oafim.conf.5.gz."

Share this post


Link to post

Понял проблему. Решил отключением SELinux.

Но в KSC статус постоянной защиты "Отключена" стоит

Share this post


Link to post
Спойлер

/opt/kaspersky/klnagent/bin/klnagchk: Relink `/opt/kaspersky/klnagent/lib/libklcurl.so' with `/lib/libpthread.so.0' for IFUNC symbol `siglongjmp'
Starting klnagchk utility
Checking command-line arguments...OK
Initializing basic libraries...OK
Current host is ''
Network agent version is '10.5.1.7'


Reading settings...OK
Checking settings...OK
Administration Agent settings:
  Server address: '10.26.12.18'
  Use SSL: 1
  Compress traffic: 1
  Server SSL ports: '13000'
  Server ports: '14000'
  Use proxy: 0
  Certificate: present
  Open UDP port: 1
  UDP ports: '15000'

  Ping period, minutes: 15
  Conn timeout, s: 30
  RW timeout, s: 180
  HostId: 2c36a339-37e1-4c23-b83d-12356e8b05e1


Connecting to server...OK

Connecting to the Administration Agent...OK
Administration Agent is running
Acquire Administration Agent statistics...OK
  Administration Agent statistics:
  Ping count: 3
  Succ. pings: 3
  Sync count: 0
  Succ. syncs: 0
  Last ping:15.05.2018 09:48:40 GMT (15.05.2018 12:48:40)


Deinitializing basic libraries...OK

 

Вот

Share this post


Link to post

License key file is not installed -  Runtime task ID: 0; Task type: ODFIM;

License not installed

На сервере есть ключ, не подтягивает что ли. Только сейчас в событиях увидел.

Не обновляются базы, не запускается защита.

Share this post


Link to post

По логам klnagchk видно что у агента отсутсвует соединение с KSC. Проверьте доступность KSC с данного компьютера и правильно ли указан адрес в агенте.

Спасибо!

Share this post


Link to post

Решил все сделать с нуля. Но во время postinstall получил

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

С этим мне туда же идти?

Share this post


Link to post

Здравствуйте,

спасибо за информацию!
Пожалуйста, ожидайте ответ в рамках инцидента в ближайшее время.

СпасибО!

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.