Might also be the reason for the freezes or webpages not loading (trying to get something before loading but failing). Noticing the same issues as Megachip, but with different websites and also includes JS files as well as CSS files. Can't remember if I had these problems on the other location (which the 22:XX logs matching) too.Ġ2.04.15 22:54:59,902 ReportCrash: Saved crash report for esets_proxy version ? to /Library/Logs/DiagnosticReports/esets_proxy_-225459_Megs-MacBook-Pro.crashĠ2.04.15 22:54:59,947 esets: error: ESET Daemon: Untergeordneter Vorgang proxy hat Signal 11 nicht verarbeitet, Neustart in 0 SekundenĠ2.04.15 22:57:28,981 ReportCrash: Saved crash report for esets_proxy version ? to /Library/Logs/DiagnosticReports/esets_proxy_-225728_Megs-MacBook-Pro.crashĠ2.04.15 22:57:29,034 esets: error: ESET Daemon: Untergeordneter Vorgang proxy hat Signal 11 nicht verarbeitet, Neustart in 0 SekundenĠ2.04.15 22:58:47,062 ReportCrash: Saved crash report for esets_proxy version ? to /Library/Logs/DiagnosticReports/esets_proxy_-225847_Megs-MacBook-Pro.crashĠ2.04.15 22:58:47,109 esets: error: ESET Daemon: Untergeordneter Vorgang proxy hat Signal 11 nicht verarbeitet, Neustart in 0 Sekunden The following errors seems occurring frequently (but not in the timespan where the problem occurred. Lastly, are there any messages in the 'Events' log mentioning "Child process proxy" or anything severe (highlighted orange or red) that looks out of the ordinary?Ġ2.04.15 12:25:07,879 esets: error: Protoscan Proxy-Agent: Text (0x151000e3:#=336592983) kann nicht lokalisiert werden: Fehler beim Scanner-Aufruf02.04.15 20:25:13,584 esets: error: Protoscan Proxy-Agent: CONNECT - c_fd=22 s_fd=-1 c_addr=::1:50729 s_addr=2a00:1450:4008:800::100d:80 pid=407 ppid=1 uid=501 ruuid=501 gid=20 app_name= app_path=/Applications/Safari.app/Contents/MacOS/Safari.Are there any entries in the 'Web Control' and 'Filtered Websites' logs (Open EES, go to Tools > Log files > Log: and check the two) that list the websites that are not working?Īre these logs accessible after uninstalling?.Does the issue occur on a secondary browser?ĭidn't test, but afair it worked in virtualBox.The CSS problem exists since I've installed EES. At this point web-control and firewall was disabled already. As described "uninstall works", I can't check your questions and suggestions anymore.īut the problem with accessing webpages started at (as far as I remember) on 2nd of april.
0 kommentar(er)
