Deploy large file

Content Authoring
1

Hi,

I’m trying to deploy an ISO to clients using prefetch command, but it fails.
It’s a big file -over 4GB- and some utils -small files- so I have that settings:

In client:
_BESClient_Download_NormalStageDiskLimitMB=6144
_BESClient_Download_ChannelThreshold=10485760

In server/relay:
_BESGather_Download_ChannelThreshold=10485760

With this settings the space limit stablished as client cache is 6GB and the secondary communication line for files lower than 10MB.

Note: If the file is lower than 3GB runs fine.

The code of action:

begin prefetch block 
 if {architecture of operating system = "x86_64"} 
     add prefetch item name=7z.exe sha1=71411f50fbfbb9f77d61860aac3b9133d428274f size=284160 url=http://myserver:53211/Uploads/71411f50fbfbb9f77d61860aac3b9133d428274f 
     add prefetch item name=7z.dll sha1=79e6cfa11747b633eb3d742d62dbed93a7b5f0d7 size=1422336 url=http://myserver:53211/Uploads/79e6cfa11747b633eb3d742d62dbed93a7b5f0d7 
 else 
     add prefetch item name=7z.exe sha1=20fea1314dbed552d5fedee096e2050369172ee1 size=163840 url=http://myserver:53211/Uploads/20fea1314dbed552d5fedee096e2050369172ee1 
     add prefetch item name=7z.dll sha1=344faf61c3eb76f4a2fb6452e83ed16c9cce73e0 size=914432 url=http://myserver:53211/Uploads/344faf61c3eb76f4a2fb6452e83ed16c9cce73e0 
 endif 
 add prefetch item name=SQL_SERVER_2012_Standard.zip sha1=8c84125cd0d316699f9ef47b31d95a320c28e6bc size=3128891655 url=http://myserver:53211/Uploads/8c84125cd0d316699f9ef47b31d95a320c28e6bc 
end prefetch block 
wait {download path "SQL_SERVER_2012_Standard.zip"}

createfile until _END_ 
echo off 
cd >>report.txt 
cd .\__Download 
cd >>report.txt 
7z.exe x SQL_SERVER_2012_Standard.zip -aoa >> report.txt 
cd SQL SERVER 2012 Standard
0_main.cmd undefined
_END_ 
move __createfile zipSQL_SERVER_2012_Standard.bat 
if {architecture of operating system = "x86_64"} 
   action uses wow64 redirection false 
endif 
wait .\zipSQL_SERVER_2012_Standard.bat >> report.txt 
notify client forcerefresh

The action result is :
Status
0,00% Completed (0 of 1 applicable computers)
Status Download Failed
Count 1
Percentage 100,00%

Downloads

File

Status
Details

71411f50fbfbb9f77d61860aac3b9133d428274f Complete Cached on Server
79e6cfa11747b633eb3d742d62dbed93a7b5f0d7 Complete Cached on Server
20fea1314dbed552d5fedee096e2050369172ee1 Complete Cached on Server
344faf61c3eb76f4a2fb6452e83ed16c9cce73e0 Complete Cached on Server
8c84125cd0d316699f9ef47b31d95a320c28e6bc Complete Cached on Server

Somebody can help me?

2

Are there relays in the infrastructure here? They may need their sizing increased as well to not have the download thrown out of their cache as well. It would be good to look inside one of the targets logs to see what it says.

I’m also presuming that the sha/size is valid as well for the items you have here (most likely they are).

In addition the “action uses wow64 redirection false” could be interestingly problematic as paths that the client is using do change when you do that (you’re in a redirected path in “Program Files (x86)” ) and I’m not sure why this would be needed for the action.

3

How much free space is on the hard drive of the failing client?

What is this client setting set to?

_BESClient_Download_MinimumDiskFreeMB
4

Generally the error should be different if it comes back because of space. From memory its something like Disk Free Limited

1 Like
5

@Alan, Is a test environment, v9.0.853. There’s only a server with twenty clients, without relays.

Here’s a cut from client log, when is trying to download files:

At 11:51:11 +0100 - 
   ActionLogMessage: (action 91768) Submitting download request
   ActionLogMessage: (action 91768) Download url: 'http://myserver:53211/Uploads/71411f50fbfbb9f77d61860aac3b9133d428274f'
   ActionLogMessage: (action 91768) Download url: 'http://myserver:53211/Uploads/79e6cfa11747b633eb3d742d62dbed93a7b5f0d7'
   ActionLogMessage: (action 91768) Download url: 'http://myserver:53211/Uploads/20fea1314dbed552d5fedee096e2050369172ee1' (skip non relevant)
   ActionLogMessage: (action 91768) Download url: 'http://myserver:53211/Uploads/344faf61c3eb76f4a2fb6452e83ed16c9cce73e0' (skip non relevant)
   ActionLogMessage: (action 91768) Download url: 'http://myserver:53211/Uploads/8c84125cd0d316699f9ef47b31d95a320c28e6bc'
At 11:51:12 +0100 - 
   ActionLogMessage: (action 91768) JobFailed - cancel and fail action
   ActionLogMessage: (action 91768) DownloadJobFailed
At 11:51:14 +0100 - 
   ActionLogMessage: (action 91768) ending action
At 11:51:14 +0100 - actionsite (http://myserver:52311/cgi-bin/bfgather.exe/actionsite)
   Not Relevant - Installacio de SQL SERVER 3GB a arqowast21 150127114711 (fixlet:91768)
At 11:51:52 +0100 - 
   Report posted successfully.

@James, as Alan deduced, there’s no space problem, the client have a more than 20GB free space.
Anyway, the ‘_BESClient_Download_MinimumDiskFreeMB’ setting is not set.

1 Like
6

Solved!

The problem wasn’t the client settings

setting "_BESClient_Download_PreCacheStageDiskLimitMB"="10614400"
setting "_BESClient_Download_NormalStageDiskLimitMB"="10614400"

The problem was the SHA1.exe tool. It doesn’t works fine with files larger than 2GB and the info showed is not correct. Obtaining the hash and size by another way ( powershell ) the file is downloaded correctly.

Thanks to all.

1 Like
7

Can you post your powershell script?

1 Like
8

You can use the Fixlet Debugger / QnA / Relevance to determine the SHA1s of files, rather than the tool.

This task will automate the entire process: (You provide a URL and nothing else, it does the rest)

http://bigfix.me/fixlet/details/3968

Here is some relevance for generating prefetches:

http://bigfix.me/relevance/details/2998744

http://bigfix.me/relevance/details/2998745

http://bigfix.me/relevance/details/2999075

9

There is probably a newer version of the tool online though I’m not 100% sure where it is. The tool was updated at some point to handle > 2GB files (the 8.0 version of the platform was our first to do so) but not sure of the versioning of the tool.

As @jgstew said, you can use relevance to determine this (and the SHA256 value for newer platforms)

1 Like
10

OMG, sorry for too late response, I was out of office.

The script sentences used:
To obtain the size of file:
(get-item $file).Length

Calculate hash of file:
Get-FileHash $file -Algorithm SHA1 | select Algorithm, Hash

More info about: https://technet.microsoft.com/en-us/library/dn520872.aspx

1 Like