Jump to content

andre.s

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by andre.s

  1. Hi Kurco, that was the solution. Thank you!
  2. Every 10 seconds this line appears in syslog. sysinfod[4392]: ESET Server Security-Fehler: Cannot parse /var/log/eset/RemoteAdministrator/Agent/status.html: Internal error I have changed permissions from directory and file but line is still present. Any idea what is the problem and how I can get away this message? Debin10 64 bit ESET Management Agent Version 8.1.2209.0 ESET Server Security Version 8.1.565.0
  3. ./ueavbe.x86_64.de.linux --accept-license --force-install Warning: Cannot detect operating system type, package won't be installed. Warning: You are probably trying to install ESET Endpoint Antivirus to unsupported distribution. If this is not the case, please use appropriate package manager of your distribution to install extracted packages, e.g.: yum install ./eea-7.1.6.0-el7.x86_64.rpm apt-get install ./eea-7.1.6.0-ubuntu18.x86_64.deb Extracting: eea-7.1.6.0-ubuntu18.x86_64.deb eea-7.1.6.0-el7.x86_64.rpm eea-7.1.6.0-el8.x86_64.rpm eea-7.1.6.0-sled15.x86_64.rpm cat /etc/debian_version 10.5
  4. Hallo, Why does Version 7.1.6 only support Suse, Ubuntu and Red Hat? Were is the support for Debian, as in Version 7.0.13? Regards
  5. The newest Google Chrome 79 crashes if ESET NOD32 is running. If I uninstall eset Google Chrome is working fine. If I install Google Chrome 78 and eset is running its also fine an no crashes. OS is Debian 9 or 10 google-chrome-stable 79.0.3945.79-1 Here is what I see on terminal if Google Chrome crashes ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [2831:135:1217/143835.660701:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. [2854:151:1217/143837.090861:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [2854:151:1217/143849.147978:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [4334:4334:1217/144249.309433:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [4521:4521:1217/144259.214596:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [4601:4601:1217/144310.006822:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [2489:2509:1217/144319.131218:FATAL:gpu_data_manager_impl_private.cc(990)] The display compositor is frequently crashing. Goodbye. Trace/Breakpoint ausgelöst Any hint what I can try that the newest Google Chrome is working?
  6. Every time I edit a bash script and want to save it after execution, it isn't possible. It only works if I completely disable "Real-time file system protection", but only for new files. For existing file I have to reboot the server. Restart of services doesn't work. Is there any solution for that? Disable "Real-time file system protection" cant be the solution.
  7. @MartinK if I install Version 5.3.10 it works. But why I have to use a version from 20-Jan-2018? And why are there are no hints in the docs that a special version must be used?
  8. @Pinni3 yes I use Administrator to login. @MartinK Database version is MySQL 5.7.28-1debian9 libodbc1 is version 2.3.4-1 MySQL Connector is Version 5.3.14 Like Pinni3 said I install ERA Server and not ESMC
  9. Hello, after a fresh install of server and Web-Console and changing the initial password, I cant login in to the Web-Console. The error is: Login failed: Invalid username or password In /var/log/eset/RemoteAdministrator/Server/trace.log I see this message: 2019-11-13 09:30:20 Error: CServerSecurityModule [Thread 7fa115ffb700]: AuthenticateNativeUser: Native user login failed In Tomcat log I see this messages: 13-Nov-2019 10:30:20.968 INFORMATION [SocketLayer worker thread] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-11-13 10:30:20.968] V2 [] <ERROR> Connection closing because of ERA server communication error: Message parsing error: java.io.IOException: SSL Engine reading side closed. 13-Nov-2019 10:30:20.969 INFORMATION [SocketLayer worker thread] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-11-13 10:30:20.969] V2 [] <INFO> Closing connection 13-Nov-2019 10:30:20.969 INFORMATION [https-openssl-apr-443-exec-8] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-11-13 10:30:20.969] V2 [Administrator] <WARNING> Login (session creation) failed (code 8) from address XXX.XXX.XXX.XXX. 13-Nov-2019 10:30:20.972 INFORMATION [https-openssl-apr-443-exec-8] sk.eset.era.g2webconsole.server.modules.logger.FileLogWriter.addItem [2019-11-13 10:30:20.969] V1 [Administrator] <TRACE> Login failed. Reason: name/password pair not authorized. OS is Debian 9 ERA Server: 6.5.417.0 Web-Console: 6.5.388.0 Java: 8u232-b09-1~deb9u1 Tomcat: 8.5.14-1+deb9u3 What can I do that I can login in to the Web-Console?
×
×
  • Create New...