Multi-repository operation for remote sites

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Patrice69
Messages: 6
Registration: March 22, 2018 - 7:22 PM

April 6, 2018 - 9:28 AM

Hello,

I updated my server to version 1.5.1.21 along with my three remote site repositories. Synchronization via Rsync works.
Everything seems to be working correctly except for the remote repositories.

The agent was deployed to all machines via a login script.

I then manually modified some remote site machines to use the local site repository configuration instead of the main site repository, based on the

wapt-get.ini file: adapting it to the local context:
[global]
repo_url=https://site1.mydomain.lan/wapt
waptserver=https://mainrepo.mydomain.lan

[wapt-host]
repo_url=https://mainrepo.mydomain.lan/wapt-host

When I assign a package to a remote machine via the console, it considers its configuration to be up-to-date. The same happens when I force a manual synchronization of the repositories, and also when I restart the remote machine.

What step do you think I missed?

Thank you in advance for your ideas...

Best regards,
Locked