Guest Posted July 10, 2014 Share Posted July 10, 2014 Ever since updating my 4 machines to ESET Cyber Security Pro (for Mac) version 6.0.9.1 I've been seeing an error message, "Cannot connect to /tmp/esets.sock: No such file or directory". After the error message appears, it seems to temporarily kill wireless network connectivity. It also kills Time Machine backups (until the machine is rebooted). The error message will continue to pop-up, if cleared (by clicking 'OK'. The only way to actually clear the error message is to reboot the machine. Four different device types are affected, a late-2010 MacBook Air, a mid-2012 MacBook Air, a mid-2011 iMac and a late-2009 Mac Mini. Reverting to version 5.0.115.0 resolve the issue. I've performed a clean uninstall and reinstall on all machines. Any advice or insight anyone is able to provide is appreciated. Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,168 Posted July 11, 2014 ESET Moderators Share Posted July 11, 2014 Hello, it is probably permissions issue. How often do you see this error? In case you would like to test new build (users reporting this same issue told us that the issue does not reoccur with 6.0.13), send me a private message. Link to comment Share on other sites More sharing options...
Freehandkilla 0 Posted July 16, 2014 Share Posted July 16, 2014 @Peter Randziak "In case you would like to test new build (users reporting this same issue told us that the issue does not reoccur with 6.0.13)," Looking at the ESET site, i see the current build is 6.0.9.1, does this mean this is issue should have been fixed in 6.0.1.3?? The build number you entered doesnt make sense. Link to comment Share on other sites More sharing options...
Arakasi 549 Posted July 16, 2014 Share Posted July 16, 2014 (edited) Build isn't released. Peter said: In case you would like to test new build, send me a private message. Edited July 16, 2014 by Arakasi Link to comment Share on other sites More sharing options...
suzuryo 0 Posted July 18, 2014 Share Posted July 18, 2014 me too. > Cannot connect to /tmp/esets.sock Link to comment Share on other sites More sharing options...
Sachio 0 Posted July 19, 2014 Share Posted July 19, 2014 me too. Same error message in Japanese.( because I'm using Japanese version.) Link to comment Share on other sites More sharing options...
SweX 871 Posted July 20, 2014 Share Posted July 20, 2014 @suzuryo, @sachio Please DO send a PM to Peter to get your hands on the test build so you can find out if it fixes the problem for you too..... https://forum.eset.com/topic/2794-cannot-connect-to-tmpesetssock-no-such-file-or-directory/?p=16180 Link to comment Share on other sites More sharing options...
jbold 0 Posted August 27, 2014 Share Posted August 27, 2014 I've been getting this issue with 6.0.13, so it isn't entirely fixed in that build either. Link to comment Share on other sites More sharing options...
Most Valued Members planet 232 Posted August 28, 2014 Most Valued Members Share Posted August 28, 2014 (edited) I also seem to be having this error with the latest version, but instead of "no such file or directory" I have "connection refused". esets_mac[1583]: error[062f0000]: Cannot connect to /tmp/esets.sock: Connection refused Edited August 28, 2014 by planet Link to comment Share on other sites More sharing options...
tmatsuno 0 Posted October 9, 2014 Share Posted October 9, 2014 same error occurred just now at ESET Cyber Security Pro 6.0.9.1 10534, OSX 10.9.5, MacBook Pro Retina 13-inch Late 2013. how should I do for fix it? Link to comment Share on other sites More sharing options...
tmatsuno 0 Posted October 9, 2014 Share Posted October 9, 2014 In my case, This issue is occurred in case of update checking the Eclipse Luna. Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,168 Posted October 14, 2014 ESET Moderators Share Posted October 14, 2014 Hello, can you please try to install most up to date version of ESET Cyber Security Pro 6.0.13? Please let us know how it went. Link to comment Share on other sites More sharing options...
Most Valued Members planet 232 Posted October 28, 2014 Most Valued Members Share Posted October 28, 2014 (edited) Still getting this error with 6.0.14.0 on Yosemite. Edit: Now resolved with recent updates. Edited March 29, 2015 by planet Link to comment Share on other sites More sharing options...
Recommended Posts