tobiasperschon 0 Posted April 30, 2019 Posted April 30, 2019 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) Debian (64-bit), Version 8.11 Update module1072 (20180813) Translation support module1733 (20190319) Configuration module1663.15 (20181129) SysInspector module1274 (20180918) SSL module1028.1 (20190327) Push Notification Service module1052 (20190122)
Administrators Marcos 5,730 Posted April 30, 2019 Administrators Posted April 30, 2019 Can clients connect to and download installers from any IP address? In such case, installers should be downloaded from a CDN and the download should not fail. If your firewall restricts connections only to specific IP addresses, you will need to allow communication with the following addresses and set the repository to repositorynocdn.eset.com as per https://support.eset.com/kb332/: repository.eset.com 91.228.166.23 91.228.167.25 38.90.226.20
tobiasperschon 0 Posted April 30, 2019 Author Posted April 30, 2019 the firewall on my client and also on the server does not restrict outgoing connections.
ESET Staff MartinK 384 Posted April 30, 2019 ESET Staff Posted April 30, 2019 Mentioned error indicates problem during creation of installer itself, which is performed after all MSI installers are successfully downloaded so we can exclude network related errors. It is not clear from trace log message, but I/O error most probably indicates problem with disk space or insufficient free memory. Could you please verify there is enough space (temporary directory for system services) and also enough free RAM (at leas 512MB)? There is also possibility that ESMC service is not able to access disk due to some security restriction, but I guess there is no SELinux enabled on Debian system.
tobiasperschon 0 Posted April 30, 2019 Author Posted April 30, 2019 I restarted the server and now it worked. so it was probably due to memory (RAM) exhaustion (Server has 2GB of memory)
Recommended Posts