Faced Keystore error in DMaaP setup

 
1
0
-1

Hi,

I faced an error when i try to setup dmaap through docker. Can anyone help with that? Thanks

The error details look like this:

------------ tail -100 error.log ---------------
2018-06-25 08:47:06,680||main|||DCAE||ERROR|||Exception java.io.IOException: Keystore was tampered with, or password was incorrect
2018-06-25 08:47:06,680||main|||DCAE||ERROR|||possibly unable to use keystore etc/keystore with passwords Perish the thought and Perishhe thought
2018-06-25 08:47:06,683||main|||DCAE||ERROR|||Unable to start Jetty etc/dmaapbc.properties
java.lang.IllegalStateException: !STOPPED
at org.eclipse.jetty.server.handler.HandlerWrapper.destroy(HandlerWrapper.java:134) ~[buscontroller.jar:na]
at org.onap.dmaap.dbcapi.server.JettyServer.<init>(JettyServer.java:157) ~[buscontroller.jar:na]
at org.onap.dmaap.dbcapi.server.Main.main(Main.java:107) [buscontroller.jar:na]
at org.onap.dmaap.dbcapi.server.Main.main(Main.java:52) [buscontroller.jar:na]
------------ tail -100 server.log ---------------

  1. Dominic Lunanuova

    can you clarify what you mean by "setup dmaap through docker".   Are you deploying via oom or heat method or some other means?

  2. Ruoyu Ying

    It means that I'm deploying via oom, Thanks.@Dominic Lunanuova

CommentAdd your comment...

2 answers

  1.  
    1
    0
    -1

    Ruoyu Ying i by passed this by removing the password value in dbcl_vm_init.sh, but i dont think this is the right method.  

    DMAAPBC_KSTOREPASS=""
    DMAAPBC_PVTKEYPASS=""

    root@onap-message-router:~# docker ps

    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
    e794810263f4 nexus3.onap.org:10001/onap/dmaap/buscontroller:1.0.12 "./bin/dmaapbc deploy" 33 seconds ago Up 32 seconds 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp dmaap-buscontroller


    * Trying 99.99.99.7...
    * Connected to dbc.api.simpledemo.onap.org (99.99.99.7) port 8080 (#0)
    > POST /webapi/dmaap HTTP/1.1
    > User-Agent: curl/7.35.0
    > Host: dbc.api.simpledemo.onap.org:8080
    > Accept: */*
    > Content-Type: application/json
    > Content-Length: 164
    >
    * upload completely sent off: 164 out of 164 bytes .....



    1. Dominic Lunanuova

      the SSL certificate in buscontroller:1.0.12 expired shortly after the image was released.  While I don't think that is necessarily the root cause of any issue,  I suggest at least eliminating that issue by using 1.0.13.

    2. Arvind Prabhakar

      Thank you for the response Dominic Lunanuova. I did update but i still get the same error, if i by pass by removing the pass phrases it proceeds and completes, but on the portal under "application on  boarding" DmaaP bus controller still says inactive. 

    3. Dominic Lunanuova

      Arvind Prabhakar, admittedly the naming is a bit confusing.  There are two components with similar names.  The buscontroller container is the service for the API.  There is also a buscontroller GUI for the portal which makes API requests.  The GUI was descoped in Beijing, so it is not deployed, which may explain the "inactive" status.

      If the buscontroller container is up, you should be able to use any http client (e.g. curl or postman) to make API requests.

    4. Arvind Prabhakar

      Dominic Lunanuova thank you! 

    CommentAdd your comment...
  2.  
    1
    0
    -1

    Hi even i am facing the same error! if found a solution please share. 

    I noticed this when DmaaP bus controller does not start. however all Robot test pass with respect to DCAE.

    Thank you! 

      CommentAdd your comment...