Secondary Repository Status TO UPDATE
Published: February 28, 2025 - 11:11 AM
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
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