Tranquil IT Forum

Hello,

version 1.7.4,
Debian 9
a Win10 client, and a 1.6.2.7 console.

Yesterday, I migrated from version 1.5 to 1.6 and then to 1.7.4. Everything went very smoothly, including the agent update.
This morning, everything was perfect. However, I'm having a small problem with a package group that I want to update, but it's not deploying to the workstations (I added some software).

To rule out any issues, I'm doing a fresh 1.7.4 installation, still on Debian 9, on a new server. There are no clients attached (yet).
As a result, as soon as I create a package group, I'm unable to delete it.
There are no errors; it's just still there after reloading.
As soon as I modify my group, it creates a second group with the new version. Since it continues to display the first version,
I end up with multiple versions of a package group

on the production server. I have a group in version 9, I added two silly things, so I'm now on version 11, but no machine is running version 11.
I then check the log of a client:

critical package BASE(=11) not installed due to errors: EWaptDOwnloadError: Package File BASE.wapt not downloaded properly.
And indeed, https://myserver/wapt/BASE.wapt => 404.

I check on the server, the file is no longer present (probably because I tried to delete it?).
If I restore an old backup, it's there.

So the question is: how do I regenerate this file and why are the destroyed groups still present in the console (even though no resources are affected)?

Thank you in advance

. Sincerely.

walibix wrote: ↑July 1, 2019 - 9:21 AM Hello,

Version 1.7.4
Debian 9
client Win10 / console 1.6.2.7.

I migrated my 1.5 to 1.6 and then to 1.7.4 yesterday. Everything went very smoothly, agent update behind the scenes, perfect
this morning. A small problem with a package group that I want to update and which isn't deploying to the machines (added software).

To eliminate any doubt, I'm installing a fresh 1.7.4, still Debian 9, on a new server, no clients attached (for now).
As a result, as soon as I create a group, I'm unable to delete it.
No error message, it's just still there after reloading.
As soon as I modify my group, it creates a second group with the new version, but continues to display the first version,
so I end up with multiple versions of a package group.

If your console is still on version 1.6.2.7, you need to update it from your WAPT server. There were bugs related to uppercase/lowercase in group package names, but this is fixed in version 1.7.4.

Sincerely,

Denis