[RESOLVED] Console 1.8.2

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
dsp
Messages: 9
Registration: February 27, 2018 - 09:15

June 12, 2020 - 11:22

Good morning,
Since I updated to version 1.8.2 of Wapt, the console no longer displays installed packages with an "OK" status in the general tab
wapt182.jpg
wapt182.jpg (98.87 KB) Viewed 6239 times
Sincerely
WAPT version: 1.8.2
Server OS: Debian 10
Administration/package creation machine OS: Windows 10 1909
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 12, 2020 - 12:17

Hello dsp,

That's rather odd. Is this a fresh install? If not, have you upgraded? From which version? I see you're on the Enterprise edition; could you call support to take a quick look early this afternoon? It shouldn't be anything serious, probably related to the upgrade of the core Postgres structure, but still, it's quite strange... See

you soon,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
dsp
Messages: 9
Registration: February 27, 2018 - 09:15

June 12, 2020 - 1:14 PM

Hello,
this is an update from 1.8.1 to 1.8.2.
This server wasn't yet in production. I'm going to test with a fresh install to see if I have the same problem.

Regards
WAPT version: 1.8.2
Server OS: Debian 10
Administration/package creation machine OS: Windows 10 1909
dsp
Messages: 9
Registration: February 27, 2018 - 09:15

June 12, 2020 - 2:14 PM

Indeed, with a fresh install I don't have this problem.
I've left my other server as is. Would you still like me to call to see what might have happened?
I should add that on the server with the problem, this line was added to my waptserver.ini file:

`wapt_huey_db = /opt/wapt/db/waptservertasks.sqlite`.

I don't know if this is related.

Regards
WAPT version: 1.8.2
Server OS: Debian 10
Administration/package creation machine OS: Windows 10 1909
User avatar
htouvet
WAPT Expert
Messages: 436
Registration: March 16, 2015 - 10:48
Contact :

June 12, 2020 - 2:22 PM

Hello,
I suspect a problem with updating the server database tables (an extra field that wasn't added during the upgrade).
This issue can be detected by checking /var/log/daemon.log while simultaneously running `wapt-get update-status` on the client PC.
If you have a few minutes, you can give us a call.
The line `wapt_huey_db = /opt/wapt/db/waptservertasks.sqlite` is "normal."

This small SQLite database manages the server's asynchronous tasks (downloading Windows updates, synchronizing repositories, etc.).
Tranquil IT
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 12, 2020 - 4:58 PM

Hello dsp,

We found the problem. It's indeed a database schema upgrade issue in PostgreSQL if you were on version 1.8.1-6742 before upgrading to 1.8.2. To force the update, you can revert to an earlier schema version in the database and restart the server. As root or sudoer, you can run:

Code: Select all

sudo -u postgres psql wapt -c "update serverattribs set value=to_json('1.8.0.0'::TEXT) where key='db_version'"
systemctl restart waptserver
We'll look into handling this directly in the upgrade script. Thanks for reporting the bug

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
dsp
Messages: 9
Registration: February 27, 2018 - 09:15

June 12, 2020 - 6:11 PM

OK thanks :D
WAPT version: 1.8.2
Server OS: Debian 10
Administration/package creation machine OS: Windows 10 1909
Locked