@Wirefall [Moderator note:] I’ve forked this users post since the issue is similar to the OP of this thread, but deals with a different version of FOG. You can find your post here: https://forums.fogproject.org/topic/9201/fog-will-not-boot-failed-to-get-an-ip-via-dhcp

@iyoung Test completed. LDAP plugin added and test login succeeded.

@Tom-Elliott Thanks, that took care of it. My Google Search-fu clearly needs work.

Remoted with @tom-langenfeld and we were able to fix the issue.

He was running Ubuntu 15.10, and the Ondrej repo would install, but there were no PHP packages for wily apparently. Updated to 16.04 and had to run a few tricks to get mysql working, but once all was working, everything appears to be running properly now.

FOG 1.3.0 installs perfectly fine on Ubuntu 16.04, among others. I test this all the time: https://forums.fogproject.org/topic/8730/fog-installer-distro-check

@rnavarro Look here for how to change the kernel:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

@THEMCV In that case, I’d like you to reduce max clients to 1 just for troubleshooting, and also increase the snapin timeout for the fog client. Set it to something much larger, something that you know the snapin will get done within. But it would seem the default is unlimited already… Can you upload a client log from an affected system?

EDIT - this is the timeout field:
0_1482959351373_2016-12-28_15-08-19.png

@sjensen

Then as Wayne said, make a new thread for it, sounds like your install is… special. Sudo being denied permission is silly.

@Timur my advice is for you is to build a new Ubuntu 16.04 server (or debian 8 or Centos 7 or Fedora 25) and install fog 1.3.0.

Here is a resource:
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

Also:
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@abos_systemax said in Fatclone.C: Filesystem isn't in a valid state:

@Wayne-Workman

I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)

— fixed that issue as well…

@sjensen i tried sudo at the start of the string. I am getting could not open lock file /var/lib/dpkg/lock - open (13: permission denied)

@lonnie776 while I am glad that youve taken the steps to find and correct a problem, I feel you may want to look at the latest fog has to offer. First we’ve, and by we I mean @Joe-Schmitt , rewritten the fog client and it is much more secure and less resource intensive on the server. As an overall result the client is much faster than the old client and has many more features to work with. I’d highly recommend updating and using this new client for any system.

Yes JJ it all works now. thanks 🙂

@Quazz yeah, I just use snapins because it’s easier. Click click click and the exact group I’m targeting has the needed snapin assigned.

@george1421

Sounds good. I’ll update when I have more information.

Thanks, is perfect

Good Christmas

How was that missing??

And, the host must be previously registered with the FOG Server, or if not previously registered it must be approved via the web interface when it shows up in pending.

Also - the host must be vista or newer. On Linux, Mono must be installed.

And - life is a whole lot easier if you don’t have the old FOG Client installed.

@Tom-Elliott I seemed to recall this same exact issue in another thread. I’m pretty sure this was the solution then too. I could not find that thread for the life of me, but I know we did see this issue before. As FOG turns 1.3.0 we should get this documented somewhere in a faq that users can find easily.