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.
Group deletion impossible
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
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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.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.
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
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
