I’d bring this to your attention:

No more recursive calls in sanitize_items function.

This was pushed up for RC-5, while it doesn’t refer to the blank page for host creation, this is what the issue was referring to. The reason it didn’t implicitly call out the create new host is because it actually impacting many other elements.

Updating to RC-5 or higher will bring this “issue” to rest for you.

In addition to below, on your FOG server please key in showmount -e 127.0.0.1 that will show what is exported (shared via nfs) on your FOG server.

@Wayne-Workman
Thank you Wayne and Tom for your replies.
I guess i didnt understand the idea of snapins, anyway, now I do.
Eventually, I solved the problem with creating a new path to the sanpins.

Regardless of this problem, I have another one now.
I just noticed that since updating to 1.3.0-RC-10, I cant capture any machine.
The progress is stuck on the client, like this:
0_1474521399902_fog-stuck-on-mountingfilesystem.JPG

im trying to capture an image i already captured, just for testing, I left it all night and it didnt continued…
Im sure about the settings i set for the new image, since its the same as the image settings that already deployed to the machine.

Should I post a new topic about this or wait here for help?

Niv.

i looked for /opt/fog/.fogsettings and changed the password the for fog user to the password i set before the update.
After that, re-runed the installer - seems to fix the problem.

tnx 🙂
Niv

well,
i tried another way and solved it.
installed grab4dos on the hard drive and set up a menu that will grab and boot thinstation.iso.
captured it as a linux image, and deployed with no problems!