[RESOLVED] Package update not installed on affected machines

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Soufiane
Messages: 3
Registration: June 17, 2022 - 09:18

June 17, 2022 - 09:44

Hello everyone! Formerly on Windows Server, I just switched to Linux! We're all very happy! 1: The agents are reporting correctly, the database is reporting correctly, and my packages/package groups are too. YES! My wapt-upgrade agent updates correctly and installs on the machines that need it.

But! I can't update my other packages, even though updates are available. The new version is present in my private repository, but the machines with the package don't recognize it, even after checking for updates. I've tried resigning my packages many times; in fact, if I add a new package as a dependency, it installs correctly. So, currently, I'm quite limited in my use of WAPT. :lol:

I haven't changed my console computer, nor my certificates or private key. The maturity level is fine, and I've verified my certificates using the tool in the console.

WAPT version: Discovery 2.2.1.11957; Server running Debian 11.
Console version 2.2.1.11957; Windows 11.

Thank you.
High
jc35
Messages: 9
Registration: Apr 15, 2020 - 4:17 p.m.

June 17, 2022 - 09:56

Hello,
which version of Linux are you deploying?
High
Soufiane
Messages: 3
Registration: June 17, 2022 - 09:18

June 17, 2022 - 10:01

Debian 11, and apt update && apt upgrade from yesterday (06/16/2022) So the latest version.
High
Soufiane
Messages: 3
Registration: June 17, 2022 - 09:18

June 17, 2022 - 12:01

My problem is solved, it was the two packages I had tested that didn't work : ) A pleasure.
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT