This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Satellite Replication Problem (XML length problem)

Hi,

we are running ZCM/ZPM 17.4.1: The satellite content replication is working fine in general, however right now I encountered a problem with a single patch:

APSB20-48 Adobe Acrobat Reader DC (Continuous) 2020.012.20041 (20.12.20041.1044) for Windows (See Notes)-634109278

Maybe there are more, but this one I have to take care of:

The corresponding satellite is external (finally we made it:)) and is showing up replication errors once in a while - Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. (CDP.UnexpectedError).

Now, while checking the content I found the mentioned ZPM-Bundle seems to be the cause, somehow the XML header length seems to be too long (max 255).

As a workaround I tried to include the bundle into satellite replication manually (using the context page of the server) and got a similar message about a problem. However it was downloading after zac cvc. Right now it is working fine... much more bandwidth will be saved now (Cumulative OS Patches don't have the issue, but this one has more than 230MB too)

Hopefully it won't break anything else: I'll check other (internal) satellites.

 

Any ideas about where I could check for the reason(s) ?

 

Thanks in advance

Dirk

Parents
  • 0

    Could you post more of the zmd-messages.log(in debug) from the satellite server? (taking out anything that's perhaps sensitive and should be kept internal, IPs, hostnames)

    Depending on where/when it's failing, sometimes there's a file attempting to be download unsuccessfully and if so, you can grab the URL from the log, and plug into a browser and sometimes that will give more information (Firewall/Security issue or give a 404/403 error, etc) 

  • 0 in reply to 

    It's me again:

    As said before - there's a general problem with replication of ZPM content to satellites (other bundle replications work well):

     

    I do not have any idea where to start because of some general questions:

    What processes are responsible for that kind of distribution? When does it happen?

    Regarding ZPM content the satellites contents looks somewhat "random"

     

    Thx again & Best Regards

    Dirk

  • 0   in reply to 

    For Starters...

    If you are getting this...

    "Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. (CDP.UnexpectedError).", then you are most likely experiencing lower level OS network connection issues.  

    Maybe networking, Maybe your primary server is running out of HTTP connections, other...But the Sat was trying to pull down content and its network connection was closed.  So that is less about scheduling....

    For Scheduling.....One KEY fact to keep in mind, that new content may be downloaded daily based upon your ZPM patch server scheduling.  So depending on your Content Replication Schedule, there will be Windows were it is on your Primary but not yet on your satellites.

    ZCC->Configuration->Bundle, Policy, Content->Content Replication 

    ZCC->Configuration->Bundle, Policy, Content->Satellite Server Replication

    are two places for generic settings for replication settings.

    https://www.novell.com/documentation/zenworks-2020-update-1/zen_sys_servers/data/bmk8phb.html

    Shows where you can specify content replication schedules for Sat Servers on the sat server itself, even down to the type of content.

     

     

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0   in reply to   

    And the timing for Patch Content can be tricky if your Sat Server is only configured to download from One Primary and that primary is not the ZPM Server.  Primary to Primary replication is hourly by default.

    Let's say your ZPM Server1 downloads Content at 2:00AM.   Sat2 Tries to replicate the content for a new patch bundle at 2:30AM, but only points to Server2 for it's content.  It will get a download error, since the content may not be there until 3:00AM.  When the Sat Tries again at 3:30AM it will come down.  If your sats are set to only replicate once a day at 2:30AM, this normal condition could cause issues and setting the schedule to perhaps 3:30AM would be wiser......or allowing a Sat to pull content from the ZPM server directly.

     

     

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Reply
  • 0   in reply to   

    And the timing for Patch Content can be tricky if your Sat Server is only configured to download from One Primary and that primary is not the ZPM Server.  Primary to Primary replication is hourly by default.

    Let's say your ZPM Server1 downloads Content at 2:00AM.   Sat2 Tries to replicate the content for a new patch bundle at 2:30AM, but only points to Server2 for it's content.  It will get a download error, since the content may not be there until 3:00AM.  When the Sat Tries again at 3:30AM it will come down.  If your sats are set to only replicate once a day at 2:30AM, this normal condition could cause issues and setting the schedule to perhaps 3:30AM would be wiser......or allowing a Sat to pull content from the ZPM server directly.

     

     

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Children
  • 0   in reply to   

    In the Pic below, my Satellite will replicate all content (Excluding Patch) every 2 hrs with unlimited throttling.

    Patch Content, replicates the 31st of Every Month (Will Skip Months with less than 31 days).  The job will run for 1 minute with a very low throttle rate.  

    Note: While the Patch example would not quite best practice.....It does show you could do the opposite and make patch replication settings different than everything else if you need more aggressive replication settings.

    content.PNG

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0 in reply to   

    Thx Craig,

    (even for the "for starters" , I don't have major replication problems - sometimes errors may raise because of large packages but in general it works fine and corrects itself ;))

    About the replication schedules: They may be still some kind of aggressive , I didn't touch them for a long time... (and just "Default" is used)

    Anyways there seems to be a general problem with "cache to satellites" right now (BTW if I forgot, running 2017U4), only a few patches are visible at satellites:

    IMO I should be successful using zac cdp (even cvc before) to get a satellite updated... ??

    Right now I'm going to visit your new post...