sigma.software 0 Posted February 9, 2016 Share Posted February 9, 2016 Hi All! I have problems installing eset agent on Mac OS 10.11.3. It fails with message "error occurred while checking openssl". eraagentinstaller.log ends with "../Agent/setup/CustomActions: cannot execute binary file". Has anybody managed to install agent correctly? Any help will be greatly appreciated Thanks in advance. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 11, 2016 ESET Staff Share Posted February 11, 2016 Hi All! I have problems installing eset agent on Mac OS 10.11.3. It fails with message "error occurred while checking openssl". eraagentinstaller.log ends with "../Agent/setup/CustomActions: cannot execute binary file". Has anybody managed to install agent correctly? Any help will be greatly appreciated Thanks in advance. Hello, I guess you are using non-default OpenSSL library on you system. If it is your case make sure it is so called "universal" because ERA requires i386 (32bit) version of OpenSSL. For example in case you are using macports, you can use command: sudo port install openssl +universal to install OpenSSL libraries suitable for both platforms. Link to comment Share on other sites More sharing options...
sigma.software 0 Posted February 12, 2016 Author Share Posted February 12, 2016 Hi! Thx for reply! I've just reinstalled OS from scratch, so its fresh copy without any additional software. Still can't install ERA agent. installation ends with error: readlink: illegal option -- e usage: readlink [-n] [file ...] failure 840: Error occured while checking OpenSSL Pls, advise. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 12, 2016 ESET Staff Share Posted February 12, 2016 Hi! Thx for reply! I've just reinstalled OS from scratch, so its fresh copy without any additional software. Still can't install ERA agent. installation ends with error: readlink: illegal option -- e usage: readlink [-n] [file ...] failure 840: Error occured while checking OpenSSL Pls, advise. To be honest, we have not seen such error... Could you please describe how exactly you install AGENT (installer version, installing using dmg? installing using generated ERA live installer?) Seems process installation fails on shell script syntax error .. any chance your system user (current user used to install) uses some non-standard shell interpreter? Installer was created for default /bin/bash interpreter and there are known issues with alternative interpreters. Link to comment Share on other sites More sharing options...
sigma.software 0 Posted February 15, 2016 Author Share Posted February 15, 2016 To be honest, we have not seen such error... Could you please describe how exactly you install AGENT (installer version, installing using dmg? installing using generated ERA live installer?) Seems process installation fails on shell script syntax error .. any chance your system user (current user used to install) uses some non-standard shell interpreter? Installer was created for default /bin/bash interpreter and there are known issues with alternative interpreters. I've just check - the shall is /bin/bash. Regarding agent installation - I use installer generated by ERA server Version 6.3.136.0 Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 15, 2016 ESET Staff Share Posted February 15, 2016 To be honest, we have not seen such error... Could you please describe how exactly you install AGENT (installer version, installing using dmg? installing using generated ERA live installer?) Seems process installation fails on shell script syntax error .. any chance your system user (current user used to install) uses some non-standard shell interpreter? Installer was created for default /bin/bash interpreter and there are known issues with alternative interpreters. I've just check - the shall is /bin/bash. Regarding agent installation - I use installer generated by ERA server Version 6.3.136.0 In case there are still installation files in /Application/ESET Remote Administratrator Agent.app/, could you please search for mentioned binary file CustomActions and provide output of command: otool -L <some path>/CustomActions Does it work on some machines or you have tried only this one? Have you tried any other installation method (manual installation or remote deployment task)? For manual installation, simply download installer .dmg file from ESET website. You will be prompted for connection parameters, CA certificate and AGENT certificate during installation wizard. Link to comment Share on other sites More sharing options...
sigma.software 0 Posted February 16, 2016 Author Share Posted February 16, 2016 otool returns: CustomActions: is not an object file. Yes, I tried several machines - result just the same. Today I tried to install agent manually and that did the trick. Now I see mac reporting to ERA server with name macmini-xxxxxx, where xxxxxx is the part of ethernet card mac address. Can I somehow change this name? What will happen if I switch to WiFi - will ERA server recognize that this is the same machine or I will need additional license? Thx. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 16, 2016 ESET Staff Share Posted February 16, 2016 otool returns: CustomActions: is not an object file. Yes, I tried several machines - result just the same. Today I tried to install agent manually and that did the trick. Now I see mac reporting to ERA server with name macmini-xxxxxx, where xxxxxx is the part of ethernet card mac address. Can I somehow change this name? What will happen if I switch to WiFi - will ERA server recognize that this is the same machine or I will need additional license? Thx. This name was created on SERVER using reverse DNS resolving. You can: rename it manually on SERVER (it won't have any effect on connecting and device will be recognized) use SERVER task "Rename computers" that can be set to rename computer automatically to their name as stored in "Device identifiers" section of client's detail view. You can change network as you wish, device will be still the same (until you reinstall it or run specific task "Reset cloned agent"for this purpose). Link to comment Share on other sites More sharing options...
sigma.software 0 Posted February 16, 2016 Author Share Posted February 16, 2016 regarding name - after a while it changed to the one specified in system preferences - sharing. Link to comment Share on other sites More sharing options...
sigma.software 0 Posted February 16, 2016 Author Share Posted February 16, 2016 Now I have another question - as i see policy for Mac doesn't support setting password for accessing setup. Can you confirm that? Link to comment Share on other sites More sharing options...
Recommended Posts