Jump to content

Archived

This topic is now archived and is closed to further replies.

mintuz

Failed push install onto OSX Mountain Lion

Recommended Posts

This occurs on multiple machines. It seems the disk image is unmounting before the install has even finished.

 

ADAMS-IMAC:22

Diagnostics user context: adam
 
Installation result:
== Exit code: 1 (Failure)
 
== Output from installation:
 
installer: Error the package path specified was invalid: '/Volumes/2d815f2a-6531-4b6a-b1f1-56272aca16e0/Resources/Install.pkg'.
 
== Detailed command output:
 
$ scp --> /tmp/481d48d6-65e6-4e33-9e8f-f197d897db8.install
$ scp --> /tmp/2e6c2af9-16b8-4d07-8386-b1571b82f6f.xml
$ id -u
501
[Command exited with code 0]
$ sudo -S -p "" -l
Matching Defaults entries for adam on this host:
    env_reset, env_keep+=BLOCKSIZE, env_keep+="COLORFGBG COLORTERM",
    env_keep+=__CF_USER_TEXT_ENCODING, env_keep+="CHARSET LANG LANGUAGE LC_ALL
    LC_COLLATE LC_CTYPE", env_keep+="LC_MESSAGES LC_MONETARY LC_NUMERIC
    LC_TIME", env_keep+="LINES COLUMNS", env_keep+=LSCOLORS,
    env_keep+=SSH_AUTH_SOCK, env_keep+=TZ, env_keep+="DISPLAY XAUTHORIZATION
    XAUTHORITY", env_keep+="EDITOR VISUAL", env_keep+="HOME MAIL"
 
User adam may run the following commands on this host:
    (ALL) ALL
[Command exited with code 0]
$ sudo -S -p "" hdiutil mount /tmp/481d48d6-65e6-4e33-9e8f-f197d897db8.install -mountpoint /Volumes/2d815f2a-6531-4b6a-b1f1-56272aca16e0 -quiet -noautoopen -noverify
[Command exited with code 0]
$ sudo -S -p "" installer -pkg /Volumes/2d815f2a-6531-4b6a-b1f1-56272aca16e0/Resources/Install.pkg -target /
installer: Error the package path specified was invalid: '/Volumes/2d815f2a-6531-4b6a-b1f1-56272aca16e0/Resources/Install.pkg'.
[Command exited with code 1]
[Applying configuration settings]
$ sudo -S -p "" "/Applications/.esets/Contents/MacOS/esets_daemon" --import-xml /tmp/2e6c2af9-16b8-4d07-8386-b1571b82f6f.xml
sudo: /Applications/.esets/Contents/MacOS/esets_daemon: command not found
[Command exited with code 1]
[Trying v4 configuration process]
$ sudo -S -p "" "/Applications/ESET NOD32 Antivirus 4.app/Contents/MacOS/esets_daemon" --import-xml /tmp/2e6c2af9-16b8-4d07-8386-b1571b82f6f.xml
sudo: /Applications/ESET NOD32 Antivirus 4.app/Contents/MacOS/esets_daemon: command not found
[Command exited with code 1]
[Cleaning up after the installation process]
$ sudo -S -p "" hdiutil unmount /Volumes/2d815f2a-6531-4b6a-b1f1-56272aca16e0
"/Volumes/2d815f2a-6531-4b6a-b1f1-56272aca16e0" unmounted successfully.
[Command exited with code 0]
$ rm /tmp/481d48d6-65e6-4e33-9e8f-f197d897db8.install
[Command exited with code 0]
$ rm /tmp/2e6c2af9-16b8-4d07-8386-b1571b82f6f.xml
[Command exited with code 0]
 

Share this post


Link to post
Share on other sites

Hi Mintuz,

 

I just want to check to see if you're attempting to remote install to Mac using ESET Remote Administrator. You'll need to use Apple Remote Desktop to push to Mac clients, for instructions, check out our Knowledgebase article.

I realize it may be the case that you're already following this procedure, if so let us know and we can look into further examining your error.

Share this post


Link to post
Share on other sites

Hi Thankyou, We aren't using the Apple Remote Desktop.

Share this post


Link to post
Share on other sites

Hi mintuz,

 

If you are not using Apple Remote Desktop, how are you trying to deploy NOD32 to your workstations?

 

Also, what version of NOD32 for OSX are you installing?

 

Thank you,

ChadH

Share this post


Link to post
Share on other sites

use the .dmg file you download from ESET and not the .pkg file.

 

I made the same mistake using the .pkg I created for an ARD install.

 

I actually read the error and saw what it was trying to do, which was mount the .dmg and run the installer.  Once I used the .dmg instead of the .pkg it all worked just fine.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...