Jump to content

cocorina

Members
  • Content Count

    18
  • Joined

  • Last visited

About cocorina

  • Rank
    Candidate
  1. KSC 11 still name as "Kaspersky Security 10" under console. see attached.
  2. cocorina

    comments

    I am not able to make this works due to several reasons 1. I am not well-verse in Linux, even though there are step by step guide, but the scenarios provided to too complicated 2. And in the market how many using squid as proxy? Does it support other proxy? 3. Installation is not easy, you need to first install Linux and worker and control. Customers prefer plug and play or at least a ova file which could be install on virtual machine.
  3. Can i restore the KSC backup of cluster KSC onto single KSC server?
  4. cocorina

    kesl-supervisor.service failed to start

    Thank you. I have solved the problem by installing the glibc library.
  5. cocorina

    kesl-supervisor.service failed to start

    [root@localhost bin]# ./kesl-setup.pl Kaspersky Endpoint Security 10 SP1 for Linux Beta version 10.1.0.46 Setting up the Anti-Virus Service default locale You must specify a locale that the Anti-Virus Service will use when applying the protection settings. It is important to specify the locale you are using when working with the file system names (in most cases this should be the system default locale) [en_US.UTF-8]: Anti-Virus Service default locale is changed to 'en_US.UTF-8'. Service will be restarted if it is already running. Configuring file interceptors Checking if fanotify is available... Cannot use fanotify Setting up kernel-level real-time protection Linux kernel source code is found at '/lib/modules/3.10.0-514.el7.x86_64/build'. >>> Building the kernel-level real-time protection module using the Linux kernel source code from /lib/modules/3.10.0-514.el7.x86_64/build. checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu CentOS Linux release 7.3.1611 (Core) checking for linux kernel sources... /lib/modules/3.10.0-514.el7.x86_64/build checking for linux kernel version file... /lib/modules/3.10.0-514.el7.x86_64/build/include/generated/utsrelease.h checking for linux kernel version... 3.10 checking for arch_ptrace... found, address 0xffffffff81038a10 checking for access_process_vm... found, address 0xffffffff811b21b0 checking for __ptrace_link... found, address 0xffffffff81094280 checking for __ptrace_unlink... found, address 0xffffffff810945e0 checking for get_empty_filp... found, address 0xffffffff812001f0 checking for release_open_intent... found, address 0 checking for sys_call_table... found, address 0xffffffff816a0800 checking for kstrdup... found, address 0xffffffff8119ee00 checking whether dentry.d_child is available... no checking whether struct inode_operations have rename2... yes checking whether struct inode_operations have dentry_open... yes checking whether __ptrace_link uses task cred struct as a third argument... no configure: creating ./config.status config.status: creating redirfs/Makefile config.status: creating Makefile config.status: creating kavmon.h config.status: creating osdef.h config.status: creating module.linux/Makefile >>> Compiling the kernel-level real-time protection module Cleaning redirfs make[1]: Entering directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs' make -C /lib/modules/3.10.0-514.el7.x86_64/build SUBDIRS=/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs clean make[2]: Entering directory `/usr/src/kernels/3.10.0-514.el7.x86_64' make[2]: Leaving directory `/usr/src/kernels/3.10.0-514.el7.x86_64' rm -f ../bin//redirfs.ko make[1]: Leaving directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs' Cleaning module.linux make[1]: Entering directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux' make -C /lib/modules/3.10.0-514.el7.x86_64/build SUBDIRS=/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux clean make[2]: Entering directory `/usr/src/kernels/3.10.0-514.el7.x86_64' make[2]: Leaving directory `/usr/src/kernels/3.10.0-514.el7.x86_64' rm -f ../bin//kav4fs_oas.ko redirfs Module.symvers Modules.symvers rm -f kernel.c queue.c cache.c cache.h kavmon.h kernel.h osdef.h queue.h util.h make[1]: Leaving directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux' Making link in redirfs make[1]: Entering directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs' make -C /lib/modules/3.10.0-514.el7.x86_64/build SUBDIRS=/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs modules make[2]: Entering directory `/usr/src/kernels/3.10.0-514.el7.x86_64' CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_path.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_root.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_info.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_file.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_dentry.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_flt.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_inode.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_dcache.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_chain.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_ops.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs_data.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/rfs.o LD [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/redirfs.o Building modules, stage 2. MODPOST 1 modules CC /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/redirfs.mod.o LD [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/redirfs.ko make[2]: Leaving directory `/usr/src/kernels/3.10.0-514.el7.x86_64' make[1]: Leaving directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs' Making link in module.linux make[1]: Entering directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux' make -C /lib/modules/3.10.0-514.el7.x86_64/build SUBDIRS=/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux modules make[2]: Entering directory `/usr/src/kernels/3.10.0-514.el7.x86_64' CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/module.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/interface.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/interface_monitor.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/files.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/operations.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/kernel.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/queue.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/cache.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/interceptor_rfs.o CC [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/watchdog.o LD [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/kav4fs_oas.o Building modules, stage 2. MODPOST 1 modules CC /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/kav4fs_oas.mod.o LD [M] /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/kav4fs_oas.ko make[2]: Leaving directory `/usr/src/kernels/3.10.0-514.el7.x86_64' make[1]: Leaving directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux' >>> Installing the module as /lib/modules/3.10.0-514.el7.x86_64/misc/kav4fs_oas.ko >>> Installing the module as /lib/modules/3.10.0-514.el7.x86_64/misc/redirfs.ko make[1]: Entering directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs' make -C /lib/modules/3.10.0-514.el7.x86_64/build SUBDIRS=/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs clean make[2]: Entering directory `/usr/src/kernels/3.10.0-514.el7.x86_64' CLEAN /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/.tmp_versions CLEAN /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs/Module.symvers make[2]: Leaving directory `/usr/src/kernels/3.10.0-514.el7.x86_64' rm -f ../bin//redirfs.ko rm -f Makefile make[1]: Leaving directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/redirfs' make[1]: Entering directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux' make -C /lib/modules/3.10.0-514.el7.x86_64/build SUBDIRS=/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux clean make[2]: Entering directory `/usr/src/kernels/3.10.0-514.el7.x86_64' CLEAN /var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux/.tmp_versions make[2]: Leaving directory `/usr/src/kernels/3.10.0-514.el7.x86_64' rm -f ../bin//kav4fs_oas.ko redirfs Module.symvers Modules.symvers rm -f kernel.c queue.c cache.c cache.h kavmon.h kernel.h osdef.h queue.h util.h rm -f Makefile Makefile.in make[1]: Leaving directory `/var/opt/kaspersky/kesl/10.1.0.46_1513326086/opt/kaspersky/kesl/src/kernel/module.linux' rm -f Makefile config.status config.log kavmon.h osdef.h >>> Rebuilding modules.dep >>> Probing a new module Starting Kaspersky Endpoint Security 10 SP1 for Linux Beta. This can take some time. Please wait. 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
  6. when I install kesl beta verison on my test machine running on centos 7, I encounter error when I run setup.pl 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 [root@localhost bin]# systemctl status kesl-supervisor.service ● kesl-supervisor.service - kesl Loaded: loaded (/etc/systemd/system/kesl-supervisor.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2017-12-15 00:31:43 PST; 17s ago Process: 27817 ExecStart=/etc/init.d/kesl-supervisor start (code=exited, status=255) Dec 15 00:31:33 localhost.localdomain systemd[1]: Starting kesl... Dec 15 00:31:43 localhost.localdomain kesl-supervisor[27817]: /etc/init.d/kesl-supervisor: line 170: kill: (27827) - No such process Dec 15 00:31:43 localhost.localdomain kesl-supervisor[27817]: kesl could not be started Dec 15 00:31:43 localhost.localdomain systemd[1]: kesl-supervisor.service: control process exited, code=exited status=255 Dec 15 00:31:43 localhost.localdomain systemd[1]: Failed to start kesl. Dec 15 00:31:43 localhost.localdomain systemd[1]: Unit kesl-supervisor.service entered failed state. Dec 15 00:31:43 localhost.localdomain systemd[1]: kesl-supervisor.service failed. [root@localhost bin]# cd /etc/init.d/ [root@localhost init.d]# ls functions kesl-supervisor netconsole network README [root@localhost init.d]# ./kesl-supervisor status kesl is stopped [root@localhost init.d]# ./kesl-supervisor start 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 [root@localhost init.d]# vi /etc/init.d/kesl-supervisor [root@localhost init.d]# vi /etc/init.d/kesl-supervisor Any idea?
  7. hi, As per the fixes mentioned in KB, patch "a" fix the connection problem from master ksc to slave ksc http://support.kaspersky.com/13102#block1 Do I need to install all patch a? For console, server, NA? Thanks
  8. 1. Installed and connected 2 devices to cloud - mobile (which OS - iOS or Android?) and Windows. --> Yes, one mobile (android) and windows 2. You have removed both applications from local devices? Not from cloud console? i remove KES from laptop; not from cloud 3. Now you still have devices in console as connected devices? Correct? (need screenshot). Under devices, i still have 2 devices 4. The statuses of the devices in "Device" section are ok? yes
  9. The status remains the same since day one.
  10. I removed KES from my laptop; mobile KSM remains. Under monitoring > AV protection is not running, i can see my laptop is without AV protection (KES uninstalled); However, the status under devices still with "ticked" [OK].
  11. hi, I installed both KSM and KES 10 for windows. But after i have removed both applications. I can see the under monitoring that AV protection is not running for these two devices; but the devices status still showing ok under devices.
  12. cocorina

    FLE status [In progress]

    I am using KES SP1 MR2. If i am going to apply the policy across my network, it is not possible to check one by one machine if FLE is successfully applied. And is there any way in KSC i can check the status? Thank you.
×

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.