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 Verified Answer
  • Replies replies
    4
  • Subscribers subscribers
    177
  • Views views
    327
  • Users 0 members are here
Related
Options

UCMDB 24.2 agent ciphers

chuchi

Hello:

After upgrade our UCMDB 2020.08 to 24.2 in out lab the probes don´t connect to the agents.

Even doing a simple check credentials against an agent the UI throws error "Failed to get results" (the same test using UCMDB 2020.08 PRODUCTION against the saem agent results OK)

In the probe-error.log:

2024-05-20 10:56:42,536  ERROR  [JobExecuterWorker-4:adhhocJob_uda_check_credential_10.21.50.244][] (ExecutionEngineImpl.java:391) - Discovery Error: Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "uda_check_credential", line 11, in DiscoveryMain
  File "check_credential", line 46, in connect
  File "check_credential", line 46, in connect
  File "fptools", line 159, in __call__
  File "check_credential", line 88, in _genericConnect
    at com.hp.ucmdb.discovery.library.clients.ddmagent.AgentSession.connectSession(AgentSession.java:498)
    at com.hp.ucmdb.discovery.library.clients.ddmagent.AgentSession.<init>(AgentSession.java:261)
    at com.hp.ucmdb.discovery.library.clients.ddmagent.AgentSession.<init>(AgentSession.java:165)
    at com.hp.ucmdb.discovery.library.clients.ddmagent.DDMClient.createWrapper(DDMClient.java:147)
    at com.hp.ucmdb.discovery.library.clients.BaseClient.initPrivate(BaseClient.java:222)
    at com.hp.ucmdb.discovery.library.clients.BaseClient.init(BaseClient.java:136)
    at com.hp.ucmdb.discovery.library.clients.BaseClient.<init>(BaseClient.java:110)
    at com.hp.ucmdb.discovery.library.clients.shell.ShellClient.<init>(ShellClient.java:50)
    at com.hp.ucmdb.discovery.library.clients.ddmagent.DDMClient.<init>(DDMClient.java:31)
    at sun.reflect.GeneratedConstructorAccessor165.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at com.hp.ucmdb.discovery.library.clients.ClientFactory.createClient(ClientFactory.java:156)
    at com.hp.ucmdb.discovery.library.clients.ClientsFrameworkImpl.createClient(ClientsFrameworkImpl.java:120)
    at com.hp.ucmdb.discovery.library.clients.ClientsFrameworkImpl.createClient(ClientsFrameworkImpl.java:84)
    at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)

java.lang.NoClassDefFoundError: java.lang.NoClassDefFoundError: org/apache/commons/httpclient/protocol/SSLProtocolSocketFactory

Any ideas?

  • 0  

    Hello there,

    The 24.2 probes have better security settings so most probably the upgraded probes can't connect to the older UDAs. You can do a simple view to get all the UDA versions. most probably you have a lot of those UDAs with versions older than 2020.08 and for sure there's the big bulk of your problems.

    The UDAs that came with CP 2020.08 should have the version 11.63. I think that the UDAs below 11.60 will fail to connect to the upgraded probes. A lot of older cypher and security related methods were blocked or disabled in the newer code.

    \Bogdan

  • 0 in reply to   

    All the UDA's in the Windows computers are 11.63.000.657 (2020.08). (We have not 11.60 version)

    This UDA's can´t connect to the 24.2 probes???

  • 0   in reply to 

    11.60 version should be able to connect to at least probes 2023.05. I never did an upgrade from 2020.08 to 24.2 because the leap is too big and such problems can happen.

  • Verified Answer

    +1 in reply to   

    The problem is solved.

    When the UCMDB was updated, the CP was not installed

    We try another upgrade, this time deploying the CP 24.2 and when the upgrade finished, the probes (with new versión) can contact the UDA's with no problem.

    I hope this can help other people.

    Thanks.

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.