Decision Management & Intelligence (ODM, DI)

Decision Management & Intelligence (ODM, DI)

Connect with experts and peers to elevate technical expertise, solve problems and share insights

 View Only

  • 1.  DS Runtime is raising an exception in OpenShift

    Posted Tue November 02, 2021 03:04 PM
    Edited by Eduardo Izquierdo Lázaro Tue November 02, 2021 03:06 PM

    I deployed a Helm release on OCP cluster for some ODM 8.10.5 pods (DS runtime x 2 and DS console). I completed all the preparation and deployment steps of the documentation and the release was deployed successfully.

    After deploying a Decision Service, I cannot execute using the provided route.
    The exception in the runtime is this:
    [11/2/21 18:30:02:287 UTC] 00000024 execution I The ruleset /quick_test/1.0/hello_world/1.0 is missing in the cache.
[11/2/21 18:30:02:293 UTC] 00000071 execution E It was not possible to create the ruleset: /quick_test/1.0/hello_world/1.0.
com.ibm.rules.res.xu.cacache.internal.CACacheException: GBRXU0482E: The directory property of the cache of compiled ruleset archives is not defined.
at com.ibm.rules.res.xu.cacache.internal.SimpleCACacheImpl.initialize(SimpleCACacheImpl.java:52)
at com.ibm.rules.res.xu.ruleset.internal.XURulesetFactory.getCACache(XURulesetFactory.java:171)
at com.ibm.rules.res.xu.ruleset.internal.XURulesetFactory.createDERuleset(XURulesetFactory.java:214)
at com.ibm.rules.res.xu.ruleset.internal.XURulesetFactory.createRuleset(XURulesetFactory.java:116)
at com.ibm.rules.res.xu.ruleset.internal.RulesetParsingWork.run(RulesetParsingWork.java:88)
at com.ibm.rules.res.xu.work.internal.ManagedThread.run(ManagedThread.java:35)
​

    Apparently, the error refers to value of the property compiledArchivesCacheProperties in the xu configuration (ra.xml). I checked my on-premises ODM installation and, in fact, this property is no set by default and I never see this error before., ¿Why produces an exception when running on Kubernetes?

    Note that I deployed the 2 replicas of DS runtime in the same Helm release, so they should have exactly the same configuration, however I can appreciate some differences in DS console. But same exception is raised in the 2 runtime replicas.


    ¿My this be the cause fo the error?

    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------


  • 2.  RE: DS Runtime is raising an exception in OpenShift

    Posted Thu November 04, 2021 01:24 PM
    Hi Eduardo!

    We were able to reproduce your issue using your xu-configuration.properties file.
    As the error mentions: 
    The directory property of the cache of compiled ruleset archives is not defined.

    and indeed the compiledArchivesCacheProperties requires a path property to be set to a valid directory.

    Setting the path property fixed the issue.
     

    compiledArchivesCacheProperties=maxSize=10,path=./

    We will be fixing our documentation and xu-configuration.properties sample accordingly.


    As for the DS console UI inconsistency between the 2 servers configuration, we are still investigating but this does not appear to be related.


    Thanks for raising these issues!


    ------------------------------
    Julie Garrone
    ------------------------------

    Original Message


  • 3.  RE: DS Runtime is raising an exception in OpenShift

    Posted Thu November 04, 2021 02:33 PM
    Edited by Eduardo Izquierdo Lázaro Thu November 04, 2021 02:34 PM
    Thanks for the quick reaction, I will modify the default properties.

    Just in case you're interested, I found another problem deploying an ODM Helm release using the internal DB.
    As you know, the Helm chart creates a PostgreSQL dbserver pod as part of the Helm release. If you shutdown and re-start the OCP cluster, this pod cannot start giving this exception bellow. There is some documentation in internet about how to solve the issue, but I can't do it, because the pod is created and configured in the Helm Chart, should be fixed in there.

    However deploying my own PostgreSQL database and using the external DB option for ODM, it works well.

    Generating a RSA private key

....+++++

...................+++++

writing new private key to 'server.key'

-----

waiting for server to start....2021-11-02 08:15:11.108 UTC [23] FATAL:  private key file "/var/lib/pgsql/data/server.key" has group or world access

2021-11-02 08:15:11.108 UTC [23] DETAIL:  File must have permissions u=rw (0600) or less if owned by the database user, or permissions u=rw,g=r (0640) or less if owned by root.

2021-11-02 08:15:11.108 UTC [23] LOG:  database system is shut down

 stopped waiting

pg_ctl: could not start server

Examine the log output.​


    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------

    Original Message


  • 4.  RE: DS Runtime is raising an exception in OpenShift

    Posted Wed February 09, 2022 03:19 AM
    Thanks for solution. You are doing a nice job.

    ------------------------------
    Amanda Nunes
    ------------------------------

    Original Message


Related Content