Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    12
  • Subscribers subscribers
    4
  • Views views
    761
  • Users 0 members are here
  • Locked Locked
Related
Options
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)

obiwan

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

  • 0 in reply to   

    Hi Craig,

    thx for all information and suggestions, it seems to work in general, some questions remaining:

    Just to be sure: The Patch System Bundles (from your pic) is the right selection for ZPM? Because I have to review the very (very, very) aggressive schedules. Right now I'm starting with default but adding some special for patch bundles seems to be very useful.

    Policy versions: I was always irritated about Versioning at ZPM policy page, as there's no "Delete older versions" like known from regular bundles/policies. However, I found the corresponding bundles in ZPM\Policy: Is it ok or even needed to clean them up there?: My guess would be the corresponding old patch bundles (replaced) couldn't get deleted (?).

     

    (BTW - "of course" I messed up the system yesterday, forgot about the disk space... so instead of replicating everything at once I started again, removing all replication of ZPM and adding them one-by-one after adjusting the disk space and changing the schedules...)

     

    Thx in advance

    Dirk

     

     

     

  • 0   in reply to 

    Normally, nothing is specified for patch.....All Content....Patch and otherwise...are treated the same unless otherwise defined.

    However, for this very reason admins may get themselves in a hole if they set Satellites to "Not Get New Content By Default" or start excluding bundle folders, etc.. etc....

    Then they may need to go back and remove those restrictions.

    If they have very conservative replication values because they don't care if a newer copy of a software install is on a remote satellite so it may take a day or two...However, they want any Windows patches to be there ASAP.

     

    #1 - Make sure Sats Receive all New Content by Default.

    #2 - If at some point that was never true, you may need to go back and explicitly set the ZPM folder to replicate to your Sats.

    #3 - If your Sats are pulling content from Primaries that are not the ZPM Server, when looking at your replication schedules be mindful that the content may on Non-ZPM primaries up to an hour later than the ZPM server itself....So if you have a simple daily schedule that runs around the same time as the patch download...you could be adding a delay.

    #4 - Careful about throttling settings, I've seen very low settings set causing replication to never be able to complete....

     

    --

    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

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.