Page 1 of 1
[RESOLVED] Console 1.8.2
Published: June 12, 2020 - 11:22
by dsp
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 (98.87 KB) Viewed 6236 times
Sincerely
Re: Console 1.8.2
Published: June 12, 2020 - 12:17
by dcardon
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
Re: Console 1.8.2
Published: June 12, 2020 - 1:14 PM
by dsp
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
Re: Console 1.8.2
Published: June 12, 2020 - 2:14 PM
by dsp
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
Re: Console 1.8.2
Published: June 12, 2020 - 2:22 PM
by htouvet
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.).
Re: Console 1.8.2
Published: June 12, 2020 - 4:58 PM
by dcardon
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
Re: Console 1.8.2
Published: June 12, 2020 - 6:11 PM
by dsp
OK thanks
