ERROR building package

Mathieu · May 23, 2018 - 09:17

/var/log/nginx/error.log:

2018/05/23 08:48:31 [error] 7137#0: *11683 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.200.68, server: _, request: "POST /api/v3/upload_packages HTTP/1.1", upstream: "http://127.0.0.1:8080/api/v3/upload_packages", host: "wapt"

I have no errors in the others

I'm getting an error message, but the package is indeed present in the repository

I'm going to discuss switching to Debian 9

and I would need to switch back to the normal version of Wapt because I'm still in nightly mode

May 23, 2018 - 10:51

Hello Mathieu,

Mathieu wrote: ↑May 23, 2018 - 09:17 /var/log/nginx/error.log:
Code: Select all
2018/05/23 08:48:31 [error] 7137#0: *11683 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.200.68, server: _, request: "POST /api/v3/upload_packages HTTP/1.1", upstream: "http://127.0.0.1:8080/api/v3/upload_packages", host: "wapt"
I have no errors in the others

I'm getting an error message, but the package is indeed present in the repository

The message says that Nginx didn't receive a response from the WAPT Python server (nginx is acting as a reverse proxy). Could you check if there's a Python error message at the same time?

Code: Select all

cat /var/log/syslog | grep python

Mathieu wrote: ↑May 23, 2018 - 09:17 I'm going to discuss switching to Debian 9

, and I'd have to revert to the regular version of Wapt because I'm still on the nightly build.

If you're on a nightly build of 1.5.1, there shouldn't be any problem upgrading both the distribution and the WAPT server. I just want to make sure it's not an issue related to an older version of Debian or WAPT.

Sincerely,

Denis

Mathieu · May 23, 2018 - 12:01

I don't have any Python errors during the build

I'm on nightly wapt-1.6.0.4

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

June 11, 2018 - 5:59 PM

Could you try replacing the custom_zip.py file in Program Files (x86)\Wapt with this one:

https://raw.githubusercontent.com/tranq ... tom_zip.py

Mathieu · June 14, 2018 - 09:40

I just tried the procedure:

htouvet wrote: Could you try replacing the custom_zip.py file in Program Files (x86)\wapt with this one:

https://raw.githubusercontent.com/tranq ... tom_zip.py

Unfortunately, I still get the same error message:

Code: Select all

Done Uploading C:\waptdev\futur-AdobeCC_2018_2018.0.0-34_x64_PROD.wapt
FATAL ERROR : HTTPError: 500 Server Error:  for url: https://futwapt/api/v3/upload_packages
Exit code:  3

I've noticed that after this error message, my package may appear in my console after a while; this happens about once every three times

We are currently in the testing phase of Enterprise version 1.6.1.0

June 14, 2018 - 09:53

The HTTP 500 error should have logged a more explicit message on the server side.

Can you check /var/log/daemon.log on the server?
There should be a Python traceback.

Mathieu · June 14, 2018 - 10:20

There are no Python traceback entries in the file.

I did receive the message

Code: Select all

Done Uploading C:\waptdev\futur-AdobeCC_2018_2018.0.0-35_x64_PROD.wapt
FATAL ERROR : HTTPError: 504 Server Error: Gateway Time-out for url: https://futwapt/api/v3/upload_packages
Exit code:  3

and the package is indeed present in the console.

In my previous test, there was indeed a Python traceback entry, but it was a disk space issue on my VM