FOG Snapin Client download error

[Timo]

Hi Wayne,

ok thx i’ll update then to the newer version via git.

Any way for me to download the newest version of FOG Client or is it included in the newest Server Version?!

[Wayne Workman]

@Timo

It’s included. It will download during installation and all clients in your environment will update automatically as well.

[Timo]

Ok i’ve updated now to the latest 7228 but Error is still there with my Big Snapin

what can i do?

[Wayne Workman]

@Timo Adjust those two settings I mentioned earlier, and see how that goes.

[Tom Elliott]

@Wayne-Workman You only need to make the change if you’re updating from a version that already got setup as it’s looking for the default values to be present before setting. If I always changed it, people might be upset.

[Wayne Workman]

@Tom-Elliott So would he need to change them?

[Tom Elliott]

@Wayne-Workman I’m assuming so.

I’m just trying to help clarify. “Fresh install – you shouldn’t have to make the change” “Update from trunk to newer trunk – most likely you will have to make the change manually”

[Timo]

@Wayne-Workman said in FOG Snapin Client download error:

@Timo Adjust those two settings I mentioned earlier, and see how that goes.

i’ve changed the settings in the beginning in php.ini as i mentioned in my first Post. Upload Size 2900M post_size 2900M and restartet the Apache

[Wayne Workman]

@Timo And now can you upload the snapin?

[Timo]

Log entry’s i 've marked the IP and Mac with stars

0.04.2
20.04.2016 16:33 Middleware::Communication URL: http:///fog/service/snapins.file.php?mac=||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=101
20.04.2016 16:33 Middleware::Communication ERROR: Could not download file
20.04.2016 16:33 Middleware::Communication ERROR: Der Server hat eine Protokollverletzung ausgeführt… Section=ResponseHeader Detail=“Content-Length”-Headerwert ist ungültig
20.04.2016 16:33 Middleware::Communication URL: http:///fog/service/snapins.checkin.php?taskid=101&exitcode=-1&mac=***||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1

[Wayne Workman]

@Timo Am I correct in assuming you can now upload the snapin to FOG, but the client will not download it?

[Timo]

My Topic aka question is not too upload the Snapin, it is to DOWNLOAD the snapin to the Windows Client via Task

[Timo]

@Wayne-Workman said in FOG Snapin Client download error:

@Timo Am I correct in assuming you can now upload the snapin to FOG, but the client will not download it?

Yes!

[Wayne Workman]

@Timo Ok then… apologies, it wasn’t totally clear to me. I’m informing @Jbob about it to see what he says then.

[Joe Schmitt]

Redirecting ping to @Tom-Elliott, this is most likely a server issue.

[Sebastian Roth]

@Timo said:

…Section=ResponseHeader Detail=“Content-Length”-Headerwert ist ungültig…

This translates to “value of Content-Length header is invalid”! Possibly .Net does not like such a big value??

[Timo]

Good Morning, this MOrning i’ve updated to latest GIT 7242. Now when i try to download the Snapin via Basic Task “Single Snapin” it comes up in the Log with " Unable to hash file, The file is too long. This process currently only supports files with a size of less than 2 GB.

So i think at this time it is not possible… !!!

[Timo]

@Sebastian-Roth said in FOG Snapin Client download error:

@Timo said:

…Section=ResponseHeader Detail=“Content-Length”-Headerwert ist ungültig…

This translates to “value of Content-Length header is invalid”! Possibly .Net does not like such a big value??

Is it possible to increase that? If so, where i can change that value?

[Tom Elliott]

@Timo Can you simply try updating? I removed the Content-Length setter in hopes that is all it takes to fix the issue at hand.

[Timo]

@Tom-Elliott said in FOG Snapin Client download error:

@Timo Can you simply try updating? I removed the Content-Length setter in hopes that is all it takes to fix the issue at hand.

I#ve just updated to 7246 via GIT, but unfortunately the same error in Log, unable to hash File, The file is too long. This process currently only supports files with a size of less than 2 GB.