Cannot update image anymore
-
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.
-
What is the revision number? “latest” doesn’t mean much around here because we commit many times throughout the day. Preferably check the cloud in the upper left hand corner of the web portal, or get the commit hash (I’m assuming its 8442096388f0e044f19bc18b9c9e6a3c86f1022a )
-
@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.
-
What do you know, I have a link just for you!
-
@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.
-
Please report back your findings.
If this thread gets solved, I’ll link it to that part of the WiKi like the others.
-
I had this issue as well when I upgraded my 1.2.0 machine to r3551, however, when I did a fresh install of r3551 by itself, it worked fine. Perhaps a funky issue with permissions when it upgrades from one revision to another? Just a hunch…
-
@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.
-
@tlawson To be clear, you set your permissions to 777 and it’s fixed?
What did you do to fix it?
