HTTPError: 500 Server Error: for url:

[TechHT]

WAPT version: 1.8.2
Server OS: Windows Server 2016
Administration machine OS: Windows Server 2016

Hello,

Since upgrading to version 1.8, I've been having trouble uploading packages (whether it's a package I created myself or one from the store). Regardless of the package, I can't integrate it into my WAPT console (File Import or Internet Import). I consistently encounter the following error:

HTTPError: 500 Server Error: for url: https://myservername/api/v3/upload_packages

When I check the repository, the package is indeed present, but it's not in my list of packages in the private repository.
Whether I import via the command line or the console, I encounter the same error, regardless of the source of the WAPT file.

Could you please help me?

Sincerely.

[TechHT]

Hello,

does anyone have a solution?

For your information, when I look in the WAPT repository, I can see my packages, but they all have an ID (a string of numbers and letters at the end, .wapt), but I can't see them in the console...

[TechHT]

I dug a little deeper into the logs to try and find where my problem lies, and I have the impression that it's a basic problem...

Here are the logs:

Code: Select all

2020-10-22 11:49:17,000 [waptserver     ] CRITICAL upload_packages failed ProgrammingError('ERREUR:  la colonne t1.valid_from n\'existe pas\nLINE 1: ...epends", "t1"."conflicts", "t1"."audit_schedule", "t1"."vali...\n                                                             ^\n',)

2020-10-22 11:50:04,723 [waptws         ] CRITICAL Socket IO : An error has occurred for sid 83653f00eb1e406cb4b0915754f11b13, uuid:39363436-3130-5A43-4A33-333430304852 : InterfaceError('connection already closed',)

2020-10-22 11:50:04,723 [waptws         ] CRITICAL Socket IO : An error has occurred for sid 62cee67b76ae4d6695838d3b92df5700, uuid:B6F9BF00-886C-5261-9048-ABA460CEB14F : InterfaceError('connection already closed',)

2020-10-22 11:50:04,723 [waptws         ] CRITICAL Socket IO : An error has occurred for sid 089d4f2b399f46e48364ad3d3fa447f8, uuid:7D1D4D80-3366-11E3-8F80-7446A0B2368E : InterfaceError('connection already closed',)

2020-10-22 11:50:04,770 [waptws         ] CRITICAL Socket IO : An error has occurred for sid 36bcdfcd768141fd89f5e4dd62102cc4, uuid:80685A66-037A-642A-E917-B4927212641E : OperationalError("FATAL:  le syst\xe8me de base de donn\xe9es s'arr\xeate\n",)

2020-10-22 11:50:04,786 [waptws         ] CRITICAL Socket IO : An error has occurred for sid b148b0f5de354f64b02100c5b297bec8, uuid:01243E93-3B34-6EF8-C9AA-4F8E8FC7FDAC : OperationalError('server closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n',)

2020-10-22 11:54:22,433 [waptserver     ] CRITICAL Error uploading package D:\wapt\waptserver\repository\wapt\client-ftv-agent-thunderbird_78.2.2-62_x86_PROD_de_e01cffd8e8ebec6b2743387262314c35.wapt: ERREUR:  la colonne t1.valid_from n'existe pas
LINE 1: ...epends", "t1"."conflicts", "t1"."audit_schedule", "t1"."vali...
                                                             ^

2020-10-22 11:54:22,438 [waptserver     ] CRITICAL upload_packages failed ProgrammingError('ERREUR:  la colonne t1.valid_from n\'existe pas\nLINE 1: ...epends", "t1"."conflicts", "t1"."audit_schedule", "t1"."vali...\n

[htouvet]

The database structure upgrade was not performed, or not performed correctly.

You can try running the following command in a command prompt with administrator rights and elevated privileges:

Code: Select all

waptpython -c "from waptserver.model import *;load_db_config();print(upgrade_db_structure());print(init_db())"

[TechHT]

Good morning,

Here is the response on the command line:

Code: Select all

C:\Windows\system32>waptpython -c "from waptserver.model import *;load_db_config();print(upgrade_db_structure());print(init_db())"
None
Unable to create tables, will try to upgrade step by step instead... : ProgrammingError("ERREUR:  la colonne \xc2\xab categories \xc2\xbb n'existe pas\n",)
1.8.2.0

In the meantime, I restored my server to version 1.7.
I restored to a test machine to redo the update but apparently I still have the same problem.

[dcardon]

Which version 1.7 did you upgrade from exactly, and which version 1.8 are you upgrading to?
Denis