@RLane It does appear that may have been the issue as the permissions alteration has fixed it.
@Wayne-Workman All solved!

Thanks for the assistance, really appreciated.

@Lee-Rowlett Thanks for the update. I have pulled commit 18be28c669b02a8372230d29de8524e24acc58ff on the dev-branch and the issue has either changed or a new issue has emerged. It is saying Invalid Mac Address. I have done a bit of a google and not found anything applicable to this situation. Is this just the new message for the same issue or something else entirely?

Hate to bump but this is still happening and I am not confident blaming it on the specific devices for an RMA but we cannot just waste the devices by not imaging them either.

@Wayne-Workman FOG Version 3771 on ubuntu server 12.04 LTS using undionly.kpxe and have have checked and there is nothing conflicting and the server has been rebooted during this time period. Also this isn’t an inconsistent thing. These two specific machines are failing the same way over multiple days, though I do understand the need to ask and be sure.

Hi All,

Recently we have started getting an odd issue with a very select number of computers. Over the past week 2 out of 10 computers we have imaged with FOG have failed in the inventory stage and will not procede to imaging.

8 of the computers where the same hardware (from the same batch) of which 1 failed. The other 2 are laptops of the same hardware of which 1 failed in this following way.

Everything looks good when doing a full or quick registration however at the end of the inventory collection, when it attempts to send to the server, we get the error in picture linked below and it just sits there forever.
https://instagram.com/p/5IwSa2jKI-/

The final line says:

• Attempting To Send Inventory … Invalid Host

The two machines that this is happening on have not been registered to FOG before and I have attempted updating FOG and updating (as well as downgrading) the kernel used as well, with no success.

Any advice what to try next or assistance in resolving this would be much appreciated.

@RLane It does appear that may have been the issue as the permissions alteration has fixed it.
@Wayne-Workman All solved!

Thanks for the assistance, really appreciated.

@Wayne-Workman I did see that one. While the permissions are set to 777 /images is all root:root as the owner, along with previous failed attempts getting past that ntfs flag and getting stuck on “Stopping fog status reporter” however I was not able to bring that one up when I decided to write this post.

I will give that a go though and see if it resolves the issue.

Thanks Wayne.

@Jbob: Sorry for leaving that out. It is indeed commit 8442096388f0e044f19bc18b9c9e6a3c86f1022a.

Although this was happening yesterday as well. Updated then too so that was a few commits behind what it is now.

Hi All,

I am using the latest “dev-branch” of the git repo for FOG that is available at the time I am posting this.

We love FOG and use it to image many computers however recently we have not done that much imaging. Upon returning to imaging yesterday I found that we cannot update any FOG images. The hardware of the server and clients has not changed since it worked.

The upload seems to work perfectly until it attempts to wrap up and I just get this screen.

That last part, the new line containing just an asterisk, just goes on forever. Every few minutes it just adds another one of those lines, forever.

Any assistance or tips as to what to do next would be much appreciated as we really need to update our images.

Looks like this was fixed by r2226. Cheers.

I have just updated to revision 2225 and i can no longer PXE boot into the fog interface as i get ipxe error 1d0c6139. After further investigation it seems to be because of this in the apache logs:

[CODE]File does not exist: /var/www/mod_pagespeed_beacon, referer: http://gxn-fog/fog/management/index.php?node=about&sub=kernel-update
PHP Fatal error: Call to undefined method BootMenu::HookManager() in /var/www/fog/lib/fog/BootMenu.class.php on line 408[/CODE]

I am sure it will be fixed soon but i just wanted to make sure someone knew about it.