Jump to content

tobiasperschon

Members
  • Content Count

    28
  • Joined

  • Last visited

Profile Information

  • Location
    Austria
  1. I restarted the server and now it worked. so it was probably due to memory (RAM) exhaustion (Server has 2GB of memory)
  2. the firewall on my client and also on the server does not restrict outgoing connections.
  3. Downloading an all-in-one installer package (32 or 64bit) results in an Internal Server Error at about 60% progress. these lines are from trace.log: 2019-04-30 09:26:08 Error: CInstallersModule [Thread 7f90648bc700]: CInstallerPackageProcessor::BuilderThread end unexpected with error: I/O error 2019-04-30 09:26:08 Error: ConsoleApiModule [Thread 7f9067ff7700]: 14179 Unexpected error while processing GetFileProgress request: I/O error ESET Security Management Center (Server), Version 7.0 (7.0.471.0) ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) D
  4. Hi, yes I did that. I checked the installed application list and the new app does not appear and I looked through the list and a lot of installed apps (from before a couple of days) do not appear and a lot of them have old versions listed. Interestingly the "Last Connection" Time is current... Is there a way to "force refresh" the infos from the device? cheers
  5. I downloaded it from the Google Play Store. I just went there and checked again. For ESET Endpoint Secruity it says Version 2.1.18.0 Updated on 14.Jun 2017. This version is installed for more than one day... also I removed and re-enrolled the device already once.
  6. Hi, this is what I see under "outdated applications": Group by (Application name) Group by (Application vendor) Group by (Application version) Group by (Latest application version) ESET Endpoint Security ESET, spol. s r.o. 2.1.11.0 2.1.16.0 this is what is displayed under "Installed Applications" for
  7. I applied the fix. I will check if the second problem is gone. I will also check the server if the first problem occurs again. Interestingly the server was running fine for over a year now. I apt-get upgraded it many times in this year but the first problem I mentioned just started recently. (I did not add more clients...) anyway, we'll see and I will get back to you! thanks for the advice so far! Update: so far no more errors... lets see how long the server will keep running Update2: The patch seems to have fixed both issues. Server is running fine now.
  8. Hi, I noticed that the server dies every 2 days or so. The trace log shows these lines ever 10 seconds: 2016-04-23 22:51:39 Error: NetworkModule [Thread 7fbab4ff9700]: remote_endpoint: Bad file descriptor 2016-04-23 22:51:49 Error: NetworkModule [Thread 7fbab77fe700]: remote_endpoint: Bad file descriptor 2016-04-23 22:51:49 Error: NetworkModule [Thread 7fbab4ff9700]: remote_endpoint: Bad file descriptor the last entries in the last-error.html: Scope Time Text NetworkModule 2016-Apr-22 17:09:32 remote_endpoint: Bad file descriptor SchedulerModule 2016-Apr-22 17:09:35 Received message:
  9. But as I can only see the changelog for the ERA server. Even if I select the agent at the top of the page. Another thing: the current version for the agent reported by ERA Console is 6.2.190 but the download page lists version 6.2.200.0. Aparently the latest Linux and Windows Versions are different.
  10. Hi, in light of the recent agent update to 6.2.190.0, I was wondering where I can find the change logs? kind regards
  11. I have the same problem. Completely uninstalling and reinstalling ESS/EAV did not help. This did also not help: hxxp://support.eset.com/kb217/?locale=en_US&viewlocale=en_US Until this is fixed you can disable "Report network firewall issues" and "Report virus and spyware protection issues" via an agent policy.
×
×
  • Create New...