Tranquil IT Forum

Good morning,

I'm developing a package to deploy the Adobe CC suite. I'm developing it with PyScript. During installation and uninstallation tests, everything works correctly. But when I run the build-upload, I encounter a problem I've never experienced before.

The package signing process works, although this step is quite long compared to other packages (I imagine it's due to the size of the installation files, around 26 GB). However, afterwards, according to the Python console, approximately 16 GB are sent to the server, and then the process stops with the following message: Could this be due to the size of the package files?

Thank you in advance for your answers.

Sincerely,

Guillaume Fuchs

Hi Guillaume,

have you increased the value of `client_max_body_size` in nginx? By default it's 12GB I believe, which is already quite large, but you're exceeding that.

Denis

Good morning,

Thank you for your reply!

I increased the client_max_body_size value and the client_body_timeout value.

This time the package seems to upload completely, but I'm still getting the error: The upload also crashed nginx in the process.

I think I'm going to abandon the package; it seems far too heavy for the system.

Guillaume

Hi Guillaume,

which Linux OS version are you using? It's possible that nginx is caching in a partition that doesn't have enough disk space...

otherwise, you can upload your file using rsync/ssh and run `wapt-scanpackages` again after the upload.

For large packages like this, you need to make sure there's enough disk space available on the client machines, because with a 16GB package downloaded, then 26GB unzipped, and I think around 50GB installed, you need close to 100GB of free space on the client machine...

Best regards,

Denis

Look here
https://www.wapt.fr/fr/doc-2.2/wapt-com ... rface.html
wapt-get sign-package c:\waptdev\tis-dropbox
wapt-get -i build-upload c:\waptdev\tis-dropbox