FOG Client 0.11.3 - no config.json file

[Wayne Workman]

@Tom-Elliott max_input_time is not defined, max_execution_time is set to 30. I’ll change all these to 900 and try again.

[Wayne Workman]

@Tom-Elliott No luck.

[Tom Elliott]

@Wayne-Workman how fast is it returning? Is it a specific interval? Is it possible firewall blocking due to size ?

[Wayne Workman]

@Tom-Elliott After clicking the “update” button at the bottom of the snapin, it takes approx. 50 seconds until the message at the top displays “Snapin updated”. During that time, I can see percentage progress in the bottom left corner of Chrome.

[Tom Elliott]

@Wayne-Workman the progress on chrome only shows to the tmp location on the server it’s uploading to. This is typically loaded to /tmp on the file system. Is there enough space to that file system?

[Tom Elliott]

@Wayne-Workman based on the replied posting here tmpfs only has 2.0G. Could you try a smaller large file just to see if this is the issue?

[Wayne Workman]

@Tom-Elliott If that’s the case, I will rebuild this server. I’ll try a 1GB-ish file soon.

[Tom Elliott]

@Wayne-Workman going to guess a bit further the upload gets to about 80% when it returns?

[Wayne Workman]

@Tom-Elliott No sir, it goes all the way. It hesitates for just the slightest moment at 99% and then says completed.

[Tom Elliott]

@Wayne-Workman that’s okay I’m just guessing anyway. I am thinking this is the issue then with the 0 size file.

[Tom Elliott]

Any update?

[Wayne Workman]

@Tom-Elliott I scripted it.

But I’m still willing to troubleshoot.

[Tom Elliott]

For now I’m solving this. I realize the issue at hand is likely still there, but this (at this point) is not a problem of FOG or the FOG Client in a “bug” form. This seems much more likely to be a problem simply with disk space. Of course feel free to post info as we find more info out.