kapela86 10 Posted October 9, 2023 Share Posted October 9, 2023 Today I noticed this notification I then went to update, same information was displayed there, below those two standard green "panes" (I didn't screenshot it), I then manually clicked on "check for updates" and it downloaded something, updated and that notification was gone. I then checked eset log and found out that from time to time this happens, but usually when I'm not working (my PC i running 24/7). Other that that, ESET works fine. But it's not just my PC, I checked few PCs in my company and each one had these errors in log. We use Endpoint Security, currently version 10.1.2050.00. This doesn't happen on our two servers with Server Security 10.0.12012.0. We don't use any proxy etc, updates are directly downloaded from Eset servers. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted October 9, 2023 Administrators Share Posted October 9, 2023 Does the machine connect to the Internet through Apache HTTP proxy? If so, do you have the latest version installed? Link to comment Share on other sites More sharing options...
kapela86 10 Posted October 9, 2023 Author Share Posted October 9, 2023 (edited) No, I wrote "We don't use any proxy etc" If you want to know what that message is in english, then it translates to something like this: "File was not changed in specified time frame/window" Edited October 9, 2023 by kapela86 Link to comment Share on other sites More sharing options...
kapela86 10 Posted October 9, 2023 Author Share Posted October 9, 2023 (edited) I'm sorry, nevermind that, I was mistaken. We use proxy in ESET Protect VA. I update that VA about once a month. Edited October 9, 2023 by kapela86 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted October 9, 2023 Administrators Share Posted October 9, 2023 What version of Apache do you have? Run "apachectl -v" to find out. If it's older than v2.4.11, then it's a known bug in Apache and you should update it to the latest version. Link to comment Share on other sites More sharing options...
kapela86 10 Posted October 9, 2023 Author Share Posted October 9, 2023 Nothing is returned by running that command. I used yum to check: [root@esetprotect ~]# yum list installed | grep apache apache-commons-collections.noarch 3.2.1-22.el7_2 @updates apache-commons-daemon.x86_64 1.0.13-7.el7 @base apache-commons-dbcp.noarch 1.4-17.el7 @base apache-commons-logging.noarch 1.1.2-7.el7 @base apache-commons-pool.noarch 1.6-9.el7 @base Link to comment Share on other sites More sharing options...
kapela86 10 Posted October 13, 2023 Author Share Posted October 13, 2023 @Marcos bump Link to comment Share on other sites More sharing options...
Administrators Marcos 5,082 Posted October 13, 2023 Administrators Share Posted October 13, 2023 Please raise a support ticket. The only cause for this error is a bug in an older version of Apache when updating through a proxy. Link to comment Share on other sites More sharing options...
kapela86 10 Posted October 13, 2023 Author Share Posted October 13, 2023 I just found out that on CentOS you have to use this [root@esetprotect ~]# httpd -v Server version: Apache/2.4.6 (CentOS) Server built: May 30 2023 14:01:11 Link to comment Share on other sites More sharing options...
Recommended Posts