Good morning,
Following the migration of our main server to Linux (previously on Windows), our secondary repositories, which are still on Windows, remain in a "TO UPDATE" synchronization status. Aside from this, everything seems to be working.
Our version of WAPT is 2.6.1.17787
Do you have any ideas on how to solve this problem?
THANKS
Secondary repository sync status
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
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Christophe,
great job on the Windows to Linux server migration!
What message do you get when you click "refresh index"? Is the sync.json file created (with a consistent timestamp) and with the correct permissions? Did you restart the postconf after the update?
Regards,
Denis
great job on the Windows to Linux server migration!
What message do you get when you click "refresh index"? Is the sync.json file created (with a consistent timestamp) and with the correct permissions? Did you restart the postconf after the update?
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Hi Denis,
So, indeed, we hadn't run the postconf, but that doesn't fix the problem.
Regarding the sync.json file, it's present with a consistent date and time (this morning), and when I select "update index," it says "update sync.json." No error.
Do you have any other ideas?
So, indeed, we hadn't run the postconf, but that doesn't fix the problem.
Regarding the sync.json file, it's present with a consistent date and time (this morning), and when I select "update index," it says "update sync.json." No error.
Do you have any other ideas?
- dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Christophe,
is it Red Hat or a derivative? If so, is SELinux enabled?
Denis
is it Red Hat or a derivative? If so, is SELinux enabled?
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Denis,
we're on Debian 13 and SELinux is not enabled.
we're on Debian 13 and SELinux is not enabled.
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Hello,
Without any intervention on my part, the status has returned to green since last Thursday!
The mysteries of computers have struck again
Thank you and have a good day,
Christophe
Without any intervention on my part, the status has returned to green since last Thursday!
The mysteries of computers have struck again
Thank you and have a good day,
Christophe
