ERROR building package

[dcardon]

Hello Mathieu,

While waiting for a solution, I switched to another package, also large (AdobeCC). I have exactly the same problem:

ERROR building N:\futur-AdobeCC_2018-wapt: Bad magic number for file header

. Is this a problem with WAPT and large packages?

We have already had to deal with much larger packages, and I know several admins who deploy AdobeCC with WAPT, so no, it's not just a WAPT problem with large packages.

Could you test with different software sizes to see at what size it crashes on your system? How much RAM/swap space do you have on your machine? Is your hard drive full?

Sincerely,

Denis

[Mathieu]

Could you test with different software sizes to see at what size it crashes on your system? How much RAM/swap space do you have on your machine? Is your hard drive full?

For testing the different sizes: I did Office 2016 (2GB) which works, then I have two applications, one of 6.38GB which has a build error and the other of 3.13GB with the error.

My waptdev folder is located on the shared wapt server to allow access to all technicians. I therefore performed the build/upload test on my machine, but I'm getting the same error.

On our wapt server we have 2010 MB of RAM and 879 MB of SWAP (this is not the final server).

We have space on the server for the disk.

Apparently, this is a problem with Python's ZipFile library.
Can you try opening the file n:\futur-Datastage_11-1_all.wapt that needs to be created?
It's a ZIP file that 7-Zip, for example, should be able to open and unzip.
If 7-Zip can't, then Python's ZipFile library has a problem...

In the signing process that follows the creation of the Zip file, the control file is replaced in the Zip, and the manifest and certificate are added. This phase seems to be the problem because an entry in the Zip file during the previous phase is incorrect.

I find many posts on the internet concerning the zipfile module but I don't understand how to configure it.

[htouvet]

Hello,
I retested with a 5GB package that successfully built and installed, which I can unzip with 7-Zip, but with a header problem warning...
We're investigating...

[Mathieu]

Hello,

I'm contacting you again to see if you have any ideas on how to resolve the problem which is still present?

[Mathieu]

I finally managed to package Photoshop Elements and Adobe CC

No problem with Photoshop.

However, with Adobe I get an error message:

Code: Select all

Uploading C:\Temp\dev\futur-AdobeCC_2018_2018.0.0-4_all.wapt: 6762126720 / 6762126720
Done Uploading C:\Temp\dev\futur-AdobeCC_2018_2018.0.0-4_all.wapt
FATAL ERROR : HTTPError: 413 Client Error: Request Entity Too Large for url: /api/v3/upload_packages
Exit code:  3

So I modified the configuration file thanks viewtopic.php?t=1158 to increase the size, but now I have another error:

Code: Select all

FATAL ERROR : HTTPError: 504 Server Error: Gateway Time-out for url: /api/v3/upload_packages

[Mathieu]

I don't know why, but the error is no longer present on the Adobe CC and Photoshop Elements packages.

But still on my 3GB package despite changing workstations for package creation.

Code: Select all

ERROR building N:\futur-Datastage-wapt: Bad magic number for file header

What I don't understand is that the error for Adobe CC is gone, but when I do the Build-Upload I get the error

Code: Select all

FATAL ERROR : HTTPError: 504 Server Error: Gateway Time-out for url: /api/v3/upload_packages

but the package is still present in the console even after modifying the line in the conf file concerning the time-out.

[sfonteneau]

Hello,

Following our private exchange, I was able to try building the Wapt package you sent me.

It works for me.

Could you try it with the latest nightly build?

https://wapt.tranquil.it/wapt/nightly/w ... -fab3d82b/

Simon

[Mathieu]

I just updated to the nightly build and I still have the same problem when resuming the project

Code: Select all

ERROR building Y:\futur-Visual_Studio_2015_Pro-wapt: Bad magic number for file header
0 packages successfully built
1 packages failed 
List of errors :
Y:\futur-Visual_Studio_2015_Pro-wapt
Buildind and uploading packages to https://futwapt
FATAL ERROR : Exception: No package to upload
Exit code:  3

I tried creating a package and it worked for Visual Studio

However, I still have the same problem with my other package, whether I resume the project or create it anew

Code: Select all

  ERROR building C:\Temp\futur-DataStage_V11-wapt: Bad magic number for file header
0 packages successfully built
1 packages failed 
List of errors :
C:\Temp\futur-DataStage_V11-wapt
Buildind and uploading packages to https://futwapt
FATAL ERROR : Exception: No package to upload
Exit code:  3

I tried packaging the software and compressing the contents; it works, it's not pretty, but it works. I think there's a file in the package that's interfering with the build process. So I need to copy the .zip file to the machine, extract it, and then install it.

[Mathieu]

I haven't encountered the problem yet, but now I'm getting the error

Code: Select all

Uploading C:\Temp\futur-AdobeCC_2018_2018.0.0-15_all.wapt: 6762126924 / 6762126924
Done Uploading C:\Temp\futur-AdobeCC_2018_2018.0.0-15_all.wapt
FATAL ERROR : HTTPError: 500 Server Error:  for url: https://futwapt/api/v3/upload_packages
Exit code:  3
>>> 

[dcardon]

Hello Mathieu,

I haven't encountered the problem yet, but now I'm getting the error

Code: Select all

Uploading C:\Temp\futur-AdobeCC_2018_2018.0.0-15_all.wapt: 6762126924 / 6762126924
Done Uploading C:\Temp\futur-AdobeCC_2018_2018.0.0-15_all.wapt
FATAL ERROR : HTTPError: 500 Server Error:  for url: https://futwapt/api/v3/upload_packages
Exit code:  3
>>> 

Could you please check the /var/log/syslog, /var/log/nginx/error.log, and /var/log/nginx/access.log files for the time you encountered the error? You could also try setting the log level to debug in your waptserver.ini file.

I saw in your first post that you're using Debian. Could you upgrade to Stretch? In any case, the Jessie version reaches its End of Life on June 6th.

Sincerely,

Denis