Content Management and Capture

Content Management and Capture

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
Back to discussions
Expand all | Collapse all

unable to create FileNet P8 domain in a container-based deployment

  • 1.  unable to create FileNet P8 domain in a container-based deployment

    Posted Wed September 29, 2021 05:08 PM

    Hello, I'm trying to create a P8 5.5.7 Domain in a kubernetes 1.19.0 environment. Installation is fine, I get the pod running and see FileNet/Engine page. However when I try to login with CEAdmin account, login goes fine, however I get "FNRAC1008E Unable to get data from server". I have a DB2 database on another server (I have a net-tools pod running and I see that connectivity to DB is ok from my k8 cluster). There's no clue in the logs, as what they say is the same error message as above, and nothing more than that.

    Strange thing I see is in FileNet/Engine page, where the JDBC Driver description is empty. However I log into the pod and I see that the jar files are inside the configDropins/overrides path (db2jcc4.jar and db2jcc_license_cu.jar), where I guess they should be.

    Any help?

    Thanks a lot for your support.



    #FileNet
    #Support
    #SupportMigration


  • 2.  RE: unable to create FileNet P8 domain in a container-based deployment
    Best Answer

    Posted Thu September 30, 2021 07:00 AM

    Hi lmodeo,

    Not sure if you are running into the same thing I did with my recent cpe container installation. Basically I would get this error after signing in to ACCE:

    FNRAC1008E

    Unable to get data from server

    User response: Check the error details for more information and contact IBM Software Support if necessary.

    Exception details:

    TypeError: Cannot read properties of undefined (reading 'hasError')

    I found that if I use ssl protocol instead of regular http then it works for me. Not sure if this is your issue but thought I would share what I ran into in case it helps.



    #FileNet
    #Support
    #SupportMigration


  • 3.  RE: unable to create FileNet P8 domain in a container-based deployment
    Best Answer

    Posted Thu September 30, 2021 03:45 PM

    Hi Joseph, thanks a lot!

    I finally had the acce wizard to create P8 domain, following your hint. And by the way I beg you to please tell me if you worked it out with the help of any technote or instruction saying I had to go with https, cause I couldn't find any.

    However I couldn't get the P8 Domain done anyway yet because I had an LDAP issue when I finished with the wizard (final step):

    2021-09-30T15:32:38.097 00000083 LDAP FNRCE0000I - INFO Start resolving LDAP URL for host=[9.30.44.221], port=[389] 2021-09-30T15:32:38.097 00000083 LDAP FNRCE0000I - INFO Final LDAP URL for host [9.30.44.221] is: ldap://9.30.44.221:389, whose IP is: 9.30.44.221. 2021-09-30T15:32:38.101 00000083 LDAP FNRCE0000W - WARN Failed connecting to URL [ldap://9.30.44.221:389]. attempts=1. 2021-09-30T15:32:38.102 00000083 LDAP FNRCE0000I - INFO Start resolving LDAP URL for host=[9.30.44.221], port=[389] 2021-09-30T15:32:38.102 00000083 LDAP FNRCE0000I - INFO Final LDAP URL for host [9.30.44.221] is: ldap://9.30.44.221:389, whose IP is: 9.30.44.221. 2021-09-30T15:32:38.107 00000083 LDAP FNRCE0000W - WARN Failed connecting to URL [ldap://9.30.44.221:389]. attempts=2.

    So that's strange, because since I was able to logon, that's the proof that LDAP connection is ok. Moreover, I tcpdump-ed on the LDAP server and I see tcp 389 traffic flowing by.

    I set up an OpenLDAP directory.

    Any other clue on this?

    Thanks a lot again, regards.



    #FileNet
    #Support
    #SupportMigration


Related Content