Topics created by Marcus Allen

So, after uninstalling the Legacy Client, and not rebooting but just immediately re-trying the new client, it works, it installed without error.

@Uncle-Frank

It literally says, repeated over and over:

9/22/2015 7:04 PM FOG::SnapinClient Module is disabled on this host

Nothing else. Thats it for the last several hours, except replace the word “host” with “mac” earlier in the day until I manually added the mac by going into the individual host and adding it there.

We have the snapinmodule disabled as we don’t use it. I just forgot to uncheck the box when installing the fog client again.

@Tom-Elliott Tom I can confirm that I had to do a FULL wipe as well for it to work. I think it may be database related. I upgraded to the latest, took a copy of the DB then did a FULL wipe. Tested it and everything worked. Restored the database backup, and it started the issue again. Not a huge deal since I have my snapshots and went to a known working version again though.

@Tom-Elliott said:

If you don’t mind opening a separate thread please regarding this now new issue. With the new thread can you post the fog servers Apache error logs?

No problem: https://forums.fogproject.org/topic/5822/checking-in-error-on-git-7428

Thanks for your help again!

@Marcus-Allen Look inside of /var/log I had some pretty big files in there too.

@Tom-Elliott Gotcha. We’re just imaging like crazy and that is creating a lot of these errors which filled about 12GB of logspace up. I’ve adjusted my logrotation (which is probably the better answer anyways).

So, I’m not quite sure what the issue was but I couldnt wait to get back to imaging. I ended up getting new install going and now its working fine.

Yes. Nothing has changed except the upgrade of fog. Now I’m currently using the Domain Admin account to ensure that it has permissions needed.