Hello,
I'm using Wapt Enterprise v1.8 on Windows Server 2016 (server) and Windows 10 (client).
I wanted to create a secondary repository on another Windows Server 2016 machine by assigning it the "remote-repo-ngninx" and "remote-repo-conf" packages (based on the documentation and your YouTube videos).
However, when I go to the "Repositories" tab, the synchronization status is "NO INDEX" with the following error: "You must first create the file index on the server."
What steps should I take?
Thank you for all the support you provide on this forum; it's great to get quick and efficient help.
[RESOLVED] Secondary repository: "creating file index" error
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
on the server, in the waptserver.ini file,
in the options section, you must add:
remote_repo_support = True.
Once this is done, you can restart the wapttasks and waptserver services (using services.msc).
You can then run "create file index" again; be aware that this will take some time the first time.
on the server, in the waptserver.ini file,
in the options section, you must add:
remote_repo_support = True.
Once this is done, you can restart the wapttasks and waptserver services (using services.msc).
You can then run "create file index" again; be aware that this will take some time the first time.
I've modified the waptserver configuration file in wapt/conf/ and restarted the services.
Now, in the Repositories tab, I have access to the "Sync selected", "Sync all", and "Update index" buttons. I've tried refreshing them all, but nothing happens...
Now, in the Repositories tab, I have access to the "Sync selected", "Sync all", and "Update index" buttons. I've tried refreshing them all, but nothing happens...
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Try restarting the remote agent's waptservice?
Can your secondary repository see the primary repository (via the firewall)? Is a WebSocket connection established between the two? What status does your secondary repository show in the console?
Vincent
Vincent
Vincent CARDON
Tranquil IT
Tranquil IT
Can your secondary repository see the primary repository (firewall)?
--> Yes, I was able to install the remote-repo packages remotely on the secondary repository without any problems (and I also performed a test installation locally using wapt-get update/upgrade). Just to be sure, I removed the firewall from the server, but it didn't change anything, even after restarting the machines.
Is a WebSocket connection established between the two?
Yes, I was able to deploy packages to the secondary repository, and the inventory is correctly uploaded to the server.
What status does your secondary repository show in the console?
Status: OK, Reachable: OK (for inventory)
Sync status: NO SYNC, Connection status: OK (for repositories)
--> Yes, I was able to install the remote-repo packages remotely on the secondary repository without any problems (and I also performed a test installation locally using wapt-get update/upgrade). Just to be sure, I removed the firewall from the server, but it didn't change anything, even after restarting the machines.
Is a WebSocket connection established between the two?
Yes, I was able to deploy packages to the secondary repository, and the inventory is correctly uploaded to the server.
What status does your secondary repository show in the console?
Status: OK, Reachable: OK (for inventory)
Sync status: NO SYNC, Connection status: OK (for repositories)
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello
, could you please contact us directly by phone?
Simon
, could you please contact us directly by phone?
Simon
Hello,
Problem solved: the agent in the secondary repository was still in the Community version! Thank you, Mr. Fonteneau!
Procedure:
1) On the secondary repository, go to "Programs and Features" to check the WAPT agent version (which is indeed Community).
2) On the WAPT server, click on the secondary repository > "Edit Machine".
3) Add the "waptupgrade" package as a dependency (this package updates the WAPT agent based on the last agent you generated, so you must have generated the Enterprise version agent beforehand).
4) Run the package installation. This takes a few minutes.
5) On the secondary repository, go to "Programs and Features": the WAPT agent should now be upgraded to Enterprise.
6) On the WAPT server, go to "Repositories" and click "Sync all". Wait a few minutes.
7) That's it!
Problem solved: the agent in the secondary repository was still in the Community version! Thank you, Mr. Fonteneau!
Procedure:
1) On the secondary repository, go to "Programs and Features" to check the WAPT agent version (which is indeed Community).
2) On the WAPT server, click on the secondary repository > "Edit Machine".
3) Add the "waptupgrade" package as a dependency (this package updates the WAPT agent based on the last agent you generated, so you must have generated the Enterprise version agent beforehand).
4) Run the package installation. This takes a few minutes.
5) On the secondary repository, go to "Programs and Features": the WAPT agent should now be upgraded to Enterprise.
6) On the WAPT server, go to "Repositories" and click "Sync all". Wait a few minutes.
7) That's it!
