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
    762
  • 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

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 

    Hi & Thanks for  the suggestion to take a deeper look into the log:

    I'm afraid I don't need to post those errors, they are related to clients that disconnect from network (while CDP is trying to send).

    I forgot about the big number of clients, so of course those errors will happen more often than usual.

    That's good news about the logged errors, I can ignore/delete those messages.... (so the topic is now just about ZMP satellite replication...)

    Too bad my problem about patches not reaching the satellites is still there

    And I don't have any good idea where to start, I don't even know who's responsible for making them available to the satellites.

    Any suggestions?

     

    Thanks, Dirk

Reply
  • 0 in reply to 

    Hi & Thanks for  the suggestion to take a deeper look into the log:

    I'm afraid I don't need to post those errors, they are related to clients that disconnect from network (while CDP is trying to send).

    I forgot about the big number of clients, so of course those errors will happen more often than usual.

    That's good news about the logged errors, I can ignore/delete those messages.... (so the topic is now just about ZMP satellite replication...)

    Too bad my problem about patches not reaching the satellites is still there

    And I don't have any good idea where to start, I don't even know who's responsible for making them available to the satellites.

    Any suggestions?

     

    Thanks, Dirk

Children
No Data

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.