SmartInstaller on mac ERROR !

Warget · Mar 30, 2017, 12:33 PM

Server

FOG Version: 1.3.5
OS: Debian

Client

Service Version: 10.11.6
OS: El Capitan 10.11.6

Description

Hello everyone sorry for my bad english but… I have a problem with FOG Client on MAC. When i follow process : https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Installing_-_OSX it’s not working he return this error :

And log error :

Thank’s for all help !

Joe Schmitt · Mar 31, 2017, 8:49 AM

@Warget can you try this build: https://download.mono-project.com/archive/4.3.2/macos-10-universal/MonoFramework-MDK-4.3.2.macos10.xamarin.universal.pkg if it still doesn’t work I can make another bug report to mono about this issue.

Tom Elliott · Mar 30, 2017, 12:35 PM

So, when you were installing, did you ensure the SERVER address was set to point at your actual FOG Server? I believe (I haven’t done installation of the client on Linux or Mac) that it follows a similar premise as the windows client with a default set for fog-server if you don’t specify the server address.

If you don’t enter the ip it will try using a dns lookup for fog-server in your network. Two ways to fix, during installation tell it to look at the fog server, or create a dns entry that will point fog-server at your actual fog server.

Tom Elliott · Mar 30, 2017, 12:57 PM

Also, you may be required to run the installer as root. Based on the permissions issues, this is all I can guess.

Of course @joe-schmitt will likely have more useful information than I do at this point.

Warget · Mar 30, 2017, 1:33 PM

@Tom-Elliott said in SmartInstaller on mac ERROR !:

If you don’t enter the ip it will try using a dns lookup for fog-server in your network. Two ways to fix, during installation tell it to look at the fog server, or create a dns entry that will point fog-server at your actual fog server.

I try all of ur proposition but… nothing works.

I search more solution, if somebody have a solution or proposition 0/ !

(Tom Elliott, thank’s for u implication in my problem )

Joe Schmitt · Mar 30, 2017, 1:37 PM

@Warget unfortunatly this is a bug with mono we’ve been waiting to get patched for awhile now. Once upon a time they did fix it for that version of OS X.

What version of mono are you running (do mono --version)?