[SOLVED] Update problem with secondary repositories

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
Locked
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

March 15, 2024 - 1:32 PM

Good morning,
I have a problem with my secondary repositories; they are synchronized correctly, but the workstations are not seeing the updates.
I noticed the following in the logs:

Code: Select all

"CRITICAL Error merging Packages from wapt into db: None : None"
Any ideas?
Thanks in advance,
Sincerely,
Guillaume
Last edited by guigeek on March 20, 2024 - 3:07 PM, edited 2 times.
High
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

March 20, 2024 - 10:44

Hello,
does anyone have any ideas about this problem?
Thanks!
High
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

March 20, 2024 - 1:05 PM

I forgot to mention that the error appears in the logs of the wapt client in version 2.5.4.15342
High
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

March 20, 2024 - 3:06 PM

It's okay, it's resolved :P
High
User avatar
dcardon
WAPT Expert
Messages: 1930
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

March 20, 2024 - 3:22 PM

Hi Guillaume,

I hadn't followed up on the question because the problem didn't really ring a bell. Out of curiosity, what was the issue? :-)

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
High
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

March 20, 2024 - 3:47 PM

I had forgotten that I had set up firewall rules on each of the client machines... but I had forgotten to include the secondary repositories in my rules...
High
User avatar
dcardon
WAPT Expert
Messages: 1930
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

March 22, 2024 - 09:57

Thanks for the feedback. :-)

We could add the option to open firewall rules on remote Windows repositories to the package, though. -

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
High
Locked

Return to "WAPT Server"


  • To go further with WAPT