Wapt 1.8 but database status is 1.7

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
jojo57
Messages: 16
Registration: June 28, 2016 - 10:46

April 27, 2020 - 12:41

Good morning,

Wapt server: Debian
Migration from 1.7 to 1.8
2020-04-27 12_31_39-WAPT - Apt-get for Windows.jpg
2020-04-27 12_31_39-WAPT - Apt-get for Windows.jpg (12.57 KB) Viewed 4514 times
I just updated Wapt from version 1.7 to version 1.8 without any problems; I'm now running Debian Buster and Wapt 1.8
Everything seems to be working fine (I haven't deployed any packages in Wapt 1.8 yet) but the database version is still in Wapt 1.7 (I did the update procedure to PostgreSQL 11 as in the documentation).
I successfully completed the postconf and restarted the server.

Is this normal/a problem? And if so, how do I update the database?
THANKS


PS: I should clarify that I updated Wapt to version 1.8 on the Debien Stretch server, and then upgraded from Stretch to Buster. I tried doing the opposite, migrating from Stretch to Buster first and then upgrading Wapt, but in that case, I lose the web server, which crashes every time
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

April 27, 2020 - 1:46 PM

No worries, that's normal; the latest version of the database on our end is 1.7.6.6
High
jojo57
Messages: 16
Registration: June 28, 2016 - 10:46

April 29, 2020 - 10:11

Okay, I'm relieved, thank you very much, and keep it up, Wapt is really great!
High
User avatar
vcardon
WAPT Expert
Messages: 278
Registration: Oct 06, 2017 - 10:55 p.m.
Location: Nantes, France

April 29, 2020 - 11:01

A fix is ​​coming in the next WAPT release to ensure the database version follows the server version, regardless of whether the database schemas have changed or not, as we have received your feedback several times.

Indeed, the database version was used to indicate the last time the PGSQL schemas were updated, but we've noticed this is causing confusion.

Sincerely,

Vincent
Vincent CARDON
Tranquil IT
High
jojo57
Messages: 16
Registration: June 28, 2016 - 10:46

April 29, 2020 - 12:49

Thank you for the reply; indeed, it can be confusing with a different version number.

Thank you.
High
Locked

Return to "WAPT Server"


  • To go further with WAPT