Secondary Repository Status TO UPDATE

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
Answer
Vercingetorix
Messages: 36
Registration: Sep 19, 2024 - 09:09

February 28, 2025 - 11:11

Good morning,
Wapt 2.6.0.16881 we migrated from 2.5 to 2.6.
We can synchronize the wapt packages, but not the drivers for wads, not waptwua.
The connection status is OK
The sync status remains at: to Update

The "force the sync" has no effect.
No trace in the logs.

How can we force synchronization from the server via the command line?
We can clearly see on the secondary server that the directory C:\Program Files (x86)\wapt\repository\wapt\wads\drivers is not full, missing files for example.


wapt-get.ini

Code: Select all

[global]
use_hostpackages=1
repo_url=https://xxx-xxx-xxx/wapt
wapt_server=https://xxx-xxx-xxx
verify_cert=0
max_gpo_script_wait=180
pre_shutdown_timeout=180
hiberboot_enabled=0
use_repo_rules=1
allow_remote_reboot=1
allow_remote_shutdown=1
send_usage_report=1
use_kerberos=0
peercache_enable=0
use_ad_groups=1


[wapthttpserver]
root_dir=C:\Program Files (x86)\wapt\repository
http_port=80
https_port=443
cert_file=C:\Program Files (x86)\wapt\wapthttpserver\ssl\cert.pem
private_key_file=C:\Program Files (x86)\wapt\wapthttpserver\ssl\key.pem
enable_logging=1


[repo-sync]
enable_remote_repo = True
local_repo_path = C:\Program Files (x86)\wapt\repository\wapt
local_repo_time_for_sync_start = 20:00
local_repo_time_for_sync_end = 05:30
local_repo_sync_task_period = 25
local_repo_limit_bandwidth = 4
remote_repo_dirs = wapt,waptwua,wads,wapt-host
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 3, 2025 - 09:48

Hello,

on the secondary repository you can delete the sync.json file which is usually located in /var/www or /opt/wapt/repositories (depending on your configuration).

Then restart the waptservice. The service will then perform a full scan of the locally stored files and re-download any missing files.

This may take a while, but it resets the repository.
Vercingetorix
Messages: 36
Registration: Sep 19, 2024 - 09:09

March 3, 2025 - 3:07 PM

Hello,
indeed, deleting the sync.json file restarts the file resynchronization.
It seems to me that everything is present.
However, the synchronization status remains orange at: TO UPDTAE.
And the status is SYNC_FINISHED.

How can I change the synchronization status?
Thank you in advance.
Vercingetorix
Messages: 36
Registration: Sep 19, 2024 - 09:09

March 7, 2025 - 08:16

Hello,
we have upgraded Wapt from version 2.6.0.16881 to Wapt 2.6.0.16937. The synchronization status is now OK.
We can now mark the ticket status as resolved.

Have a good day.
Answer