[RESOLVED] Waptupgrade_all package not found after upgrade 1.7

Questions about WAPT Server / Requests and help related to the WAPT server
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
Didier
Messages: 4
Registration: August 11, 2015 - 4:52 PM

September 4, 2019 - 3:48 PM

- WAPT version installed: 1.7
- Server OS (Linux / Windows): Stretch 9
- Administration/package creation machine OS: Windows 10


Good morning,
I just upgraded our server from 1.6.2 to 1.7.4. The upgrade went smoothly on the Linux side. I then updated the console and finally created the client package; so far, no problems.
I usually update my clients using the waptupgrade package. That's where I'm encountering a problem:
The client can see the new version of the package (1.6 => 1.7) but gets stuck during the download. The logs indicate that the package cannot be found. Indeed, the package being searched for ( ntic-waptupgrade_1.7.4.6165-25_all.wapt) does not exist.
I checked on the server, only the package ntic-waptupgrade_1.7.4.6165-25.wapt It exists. So I made a copy (directly under Linux) and renamed this package to ntic-_all.waptwaptupgrade_1.7.4.6165-25
The package was then installed on the client machines.

So no blocking problem, but a question: have I missed something?

Thanks in advance.

Code: Select all

raceback (most recent call last):
  File "c:\wapt\waptservice\service.py", line 1374, in run
    self.running_task.run()
  File "c:\wapt\waptservice\waptservice_common.py", line 515, in run
    self._run()
  File "c:\wapt\waptservice\waptservice_common.py", line 960, in _run
    self.result.get('errors',[])))
Exception: Erreur lors de l'installation de [u'ntic-waptupgrade']: erreurs dans les paquets [[(u'https://wapt.lepuy.local/wapt/ntic-waptupgrade_1.7.4.6165-25_all.wapt', '404 Client Error: Not Found for url: https://wapt.lepuy.local/wapt/ntic-waptupgrade_1.7.4.6165-25_all.wapt'), None], [u'ntic-waptupgrade', PackageEntry(u'ntic-waptupgrade',u'1.7.4.6165-25') , u'Traceback (most recent call last):\n  File "c:\\wapt\\common.py", line 4367, in install\n    raise EWaptDownloadError(\'Package file %s not downloaded properly.\' % p.filename)\nEWaptDownloadError: Package file ntic-waptupgrade_1.7.4.6165-25_all.wapt not downloaded properly.\n']]

Exception: Erreur lors de l'installation de [u'ntic-waptupgrade']: erreurs dans les paquets [[(u'https://wapt.lepuy.local/wapt/ntic-waptupgrade_1.7.4.6165-25_all.wapt', '404 Client Error: Not Found for url: https://wapt.lepuy.local/wapt/ntic-waptupgrade_1.7.4.6165-25_all.wapt'), None], [u'ntic-waptupgrade', PackageEntry(u'ntic-waptupgrade',u'1.7.4.6165-25') , u'Traceback (most recent call last):\n  File "c:\\wapt\\common.py", line 4367, in install\n    raise EWaptDownloadError(\'Package file %s not downloaded properly.\' % p.filename)\nEWaptDownloadError: Package file ntic-waptupgrade_1.7.4.6165-25_all.wapt not downloaded properly.\n']]
Traceback (most recent call last):
  File "c:\wapt\waptservice\service.py", line 1374, in run
    self.running_task.run()
  File "c:\wapt\waptservice\waptservice_common.py", line 515, in run
    self._run()
  File "c:\wapt\waptservice\waptservice_common.py", line 960, in _run
    self.result.get('errors',[])))
Exception: Erreur lors de l'installation de [u'ntic-waptupgrade']: erreurs dans les paquets [[(u'https://wapt.lepuy.local/wapt/ntic-waptupgrade_1.7.4.6165-25_all.wapt', '404 Client Error: Not Found for url: https://wapt.lepuy.local/wapt/ntic-waptupgrade_1.7.4.6165-25_all.wapt'), None], [u'ntic-waptupgrade', PackageEntry(u'ntic-waptupgrade',u'1.7.4.6165-25') , u'Traceback (most recent call last):\n  File "c:\\wapt\\common.py", line 4367, in install\n    raise EWaptDownloadError(\'Package file %s not downloaded properly.\' % p.filename)\nEWaptDownloadError: Package file ntic-waptupgrade_1.7.4.6165-25_all.wapt not downloaded properly.\n']]
Last edited by Didier on 05 Sep 2019 - 11:19, edited 1 time.
High
Yoann
Messages: 51
Registration: July 24, 2019 - 09:39

September 5, 2019 - 11:14

Hello,

This issue has been addressed in this thread.

During the update and execution of the postconf.sh, the packages in the repository are renamed.
In version 1.6, the packages are in the form xxx-xxxxx_xxxx_all.wapt, while in version 1.7, they are in the form xxx-xxxxx_xxxx.wapt.

WAPT agents in version 1.6 cannot find and download the new package generated in version 1.7 (xxx-waptupgrade_xxxx.wapt). A symbolic link or a copy of the package resolves this issue (or deploying the agent via GPO).

Regards.
WAPT Community 1.8
High
Didier
Messages: 4
Registration: August 11, 2015 - 4:52 PM

September 5, 2019 - 11:18

Ah, I didn't see this post, sorry.
Thank you for taking the time to reply.
High
Locked

Return to "WAPT Server"


  • To go further with WAPT