Hello,
my server is up to date at version 1.7.4.6143. I updated the console on my machine and created the client update package for all my machines.
My waptupgrade package is not updating on my machines, which are still on version 1.7.4.6077.
On all my machines, I apply a package group named WAPT which contains my waptupgrade package and instructions to disable notifications. When upgrading from version 1.6 to 1.7 and then 1.7.4, as long as I created the new agent, the update was applied. This is no longer the case.
And when I force the package application, nothing happens.
I cleared the local cache and rebuilt the package. Any ideas?
Best regards,
David Villeneuve
The WaptUpgrade agent update failed
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
-
VILLENEUVE-01342
- Messages: 7
- Registration: Nov 20, 2018 - 07:53
- Contact :
Sincerely,
David Villeneuve
David Villeneuve
- dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Villeneuve-01342,
Sincerely,
Denis Cardon
What happens when you run `wapt-get -l debug upgrade` in an elevated command prompt? Does it see that there's a package to update, or not? Could there be a problem with the group or package version (a higher version already installed)?VILLENEUVE-01342 wrote: ↑July 18, 2019 - 4:22 PM My server is up to date with version 1.7.4.6143. I updated the console on my machine and created the client update package for all my machines.
My waptupgrade package is not updating on my machines, which are still on version 1.7.4.6077.
On all my machines, I apply a package group named WAPT which contains my waptupgrade package and an instruction to disable notifications. When upgrading from version 1.6 to 1.7 and then 1.7.4, as long as I created the new agent, the update was applied. This is no longer the case.
And when I force the application of the package, nothing happens.
I cleared the local cache and rebuilt the package. Any ideas?
Sincerely,
Denis Cardon
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
-
VILLENEUVE-01342
- Messages: 7
- Registration: Nov 20, 2018 - 07:53
- Contact :
Good morning,
I have another problem that occurred today. We use an "APPLI" group that we apply to our workstations. We update the versions of the applications in this group, and they were updating as we did so.
Today, all my workstations were showing an error with the "APPLI" group missing. Despite all my tests, nothing worked. I deleted the group (which was version 16) and recreated a new one with the same name (version 1), and then all my workstations updated and received the WAPT agent update immediately.
Do you have any ideas? Do you want server logs?
Here is the result of the command you requested:
I have another problem that occurred today. We use an "APPLI" group that we apply to our workstations. We update the versions of the applications in this group, and they were updating as we did so.
Today, all my workstations were showing an error with the "APPLI" group missing. Despite all my tests, nothing worked. I deleted the group (which was version 16) and recreated a new one with the same name (version 1), and then all my workstations updated and received the WAPT agent update immediately.
Do you have any ideas? Do you want server logs?
Here is the result of the command you requested:
Code: Select all
Current loglevel : DEBUG
2019-07-26 09:05:16,562 DEBUG Default encoding : ascii
2019-07-26 09:05:16,562 DEBUG Setting encoding for stdout and stderr to cp850
Using config file: c:\Program Files\wapt\wapt-get.ini2019-07-26 09:05:16,654 DEB
UG Python path ['c:\\Program Files\\wapt', 'c:\\Program Files\\wapt', 'c:\\Progr
am Files\\wapt\\python27.zip', 'c:\\Program Files\\wapt\\DLLs', 'c:\\Program Fil
es\\wapt\\lib', 'c:\\Program Files\\wapt\\lib\\plat-win', 'c:\\Program Files\\wa
pt\\lib\\lib-tk', 'c:\\Program Files\\wapt', 'c:\\Program Files\\wapt\\lib\\site
-packages', 'c:\\Program Files\\wapt\\lib\\site-packages\\pywin32-223-py2.7-win3
2.egg']
2019-07-26 09:05:16,654 INFO Using local waptservice configuration c:\Program Fi
les\wapt\wapt-get.ini
2019-07-26 09:05:16,654 DEBUG Config file: c:\Program Files\wapt\wapt-get.ini
2019-07-26 09:05:16,671 DEBUG Thread 6996 is connecting to wapt db
2019-07-26 09:05:17,029 DEBUG Using host certificate c:\Program Files\wapt\priva
te\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.pem for repo global auth
2019-07-26 09:05:17,200 DEBUG Thread 6996 is connecting to wapt db
2019-07-26 09:05:18,823 DEBUG DB Start transaction
2019-07-26 09:05:18,823 DEBUG Transaction took too much time : 1.62299990654
2019-07-26 09:05:18,823 DEBUG DB commit
2019-07-26 09:05:19,135 DEBUG Using host certificate c:\Program Files\wapt\priva
te\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.pem for repo wapt auth
2019-07-26 09:05:19,713 DEBUG Using host certificate c:\Program Files\wapt\priva
te\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.pem for repo wapt-host auth
2019-07-26 09:05:19,852 INFO User Groups:[]
2019-07-26 09:05:19,852 DEBUG WAPT base directory : c:\Program Files\wapt
2019-07-26 09:05:19,852 DEBUG Package cache dir : c:\Program Files\wapt\cache
2019-07-26 09:05:19,852 DEBUG WAPT DB Structure version;: 20190111
2019-07-26 09:05:19,852 DEBUG Checking if old install in progress
2019-07-26 09:05:19,930 DEBUG reset stalled install_status in database
2019-07-26 09:05:19,930 INFO Status : Upgrade system
2019-07-26 09:05:19,930 DEBUG DB Start transaction
2019-07-26 09:05:19,930 DEBUG DB commit
2019-07-26 09:05:20,243 DEBUG Checking availability of host packages "[PackageEn
try(u'BD5EFA65-BD98-11E6-8F00-B26CA10380EF',u'28' )]"
2019-07-26 09:05:20,243 DEBUG Checking if BD5EFA65-BD98-11E6-8F00-B26CA10380EF(=
28) is installed/outdated
2019-07-26 09:05:20,571 DEBUG upgrades : {'upgrade': [], 'additional': [], 'inst
all': [u'BD5EFA65-BD98-11E6-8F00-B26CA10380EF(=28)'], 'remove': []}
2019-07-26 09:05:20,571 INFO Status : Install additional packages
2019-07-26 09:05:20,571 DEBUG DB Start transaction
2019-07-26 09:05:20,571 DEBUG DB commit
2019-07-26 09:05:20,571 INFO Status : Install upgrade packages
2019-07-26 09:05:20,571 DEBUG DB Start transaction
2019-07-26 09:05:20,571 DEBUG DB commit
2019-07-26 09:05:20,586 INFO Status : Install install packages
2019-07-26 09:05:20,586 DEBUG DB Start transaction
2019-07-26 09:05:20,586 DEBUG DB commit
2019-07-26 09:05:20,710 DEBUG Loading ssl context with cert c:\Program Files\wap
t\private\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.crt and key c:\Program Files\wapt
\private\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.pem
Installing BD5EFA65-BD98-11E6-8F00-B26CA10380EF(=28)2019-07-26 09:05:20,710 DEBU
G Trying to get host package for BD5EFA65-BD98-11E6-8F00-B26CA10380EF at https:
//113801l059app.cpam-isere.cnamts.fr/wapt-host/BD5EFA65-BD98-11E6-8F00-B26CA1038
0EF.wapt
2019-07-26 09:05:20,710 DEBUG Starting new HTTPS connection (1): 113801l059app.c
pam-isere.cnamts.fr:443
2019-07-26 09:05:20,835 DEBUG https://113801l059app.cpam-isere.cnamts.fr:443 "GE
T /wapt-host/BD5EFA65-BD98-11E6-8F00-B26CA10380EF.wapt HTTP/1.1" 200 2949
2019-07-26 09:05:20,851 DEBUG Stores cert chain check in cache
2019-07-26 09:05:20,882 DEBUG Stores cert chain check in cache
2019-07-26 09:05:20,882 DEBUG Downloaded : {'downloaded': [u'c:\\Program Files\\
wapt\\cache\\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.wapt'], 'skipped': [], 'errors
': [], 'packages': [PackageEntry(u'BD5EFA65-BD98-11E6-8F00-B26CA10380EF',u'28' )
]}
2019-07-26 09:05:20,882 INFO Register start of install c:\Program Files\wapt\cac
he\BD5EFA65-BD98-11E6-8F00-B26CA10380EF.wapt as user VILLENEUVE-01342 to local D
B with params {}
2019-07-26 09:05:20,882 INFO Interactive user:VILLENEUVE-01342, usergroups []
2019-07-26 09:05:20,898 INFO Status : Installing package BD5EFA65-BD98-11E6-8F00
-B26CA10380EF version 28 ...
2019-07-26 09:05:20,898 DEBUG DB Start transaction
2019-07-26 09:05:20,898 DEBUG DB commit
2019-07-26 09:05:20,898 DEBUG DB Start transaction
2019-07-26 09:05:20,914 DEBUG DB commit
2019-07-26 09:05:20,930 DEBUG DB Start transaction
2019-07-26 09:05:20,930 DEBUG DB commit
2019-07-26 09:05:20,944 DEBUG DB Start transaction
FATAL ERROR : EWaptUnavailablePackage: Missing dependencies: PROGRES2019-07-26 0
9:05:20,944 DEBUG DB commit
2019-07-26 09:05:20,944 DEBUG DB Start transaction
Exception at 00442370: EPyException:
EWaptUnavailablePackage: Missing dependencies: PROGRES.
2019-07-26 09:05:20,960 DEBUG DB commit
2019-07-26 09:05:21,256 DEBUG Checking availability of host packages "[PackageEn
try(u'BD5EFA65-BD98-11E6-8F00-B26CA10380EF',u'28' )]"
2019-07-26 09:05:21,256 DEBUG Checking if BD5EFA65-BD98-11E6-8F00-B26CA10380EF(=
28) is installed/outdated
2019-07-26 09:05:21,367 DEBUG store status in DBSincerely,
David Villeneuve
David Villeneuve
