IBM Cloud Pak for Security

Cloud Pak for Security

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

There is no connection between isc-cases-postgres and isc-cases-activemq pods

  • 1.  There is no connection between isc-cases-postgres and isc-cases-activemq pods

    Posted Wed April 29, 2020 01:36 AM
    Hello all,
    Has anyone encountered a similar problem?
    I have successfully installed CP4S 1.2 on my bare metal OpenShift 4.3 cluster.
    I added a user from LDAP to the CP4S team with the administrator role, but I can't log into the CP4S console.
    I am constantly redirected to the login page of the IBM Cloud Platform.
    It is also seen that the isc-case-operator pod have the status "Running", but are constantly rebooting.
    I also found that there is no connection between isc-cases-postgres and isc-cases-activemq pods.
    Logs from isc-cases-postgres:
    < 2020-04-28 20:33:10.615 UTC > LOG: database system is ready to accept connections
    < 2020-04-28 20:48:27.033 UTC > ERROR: relation "activemq_msgs" already exists
    < 2020-04-28 20:48:27.033 UTC > STATEMENT: CREATE TABLE activemq_msgs(ID BIGINT NOT NULL, CONTAINER VARCHAR(250) NOT NULL, MSGID_PROD VARCHAR(250), MSGID_SEQ BIGINT, EXPIRATION BIGINT, MSG BYTEA, PRIMARY KEY ( ID ) )
    < 2020-04-28 20:48:27.065 UTC > ERROR: relation "activemq_msgs_midx" already exists
    < 2020-04-28 20:48:27.065 UTC > STATEMENT: CREATE INDEX activemq_msgs_MIDX ON activemq_msgs (MSGID_PROD,MSGID_SEQ)
    < 2020-04-28 20:48:27.074 UTC > ERROR: relation "activemq_msgs_cidx" already exists
    ...
    < 2020-04-28 20:48:27.414 UTC > DETAIL: Key (id)=(1) already exists.
    < 2020-04-28 20:48:27.414 UTC > STATEMENT: INSERT INTO activemq_lock(ID) VALUES (1)
    < 2020-04-28 20:48:37.147 UTC > LOG: could not receive data from client: Connection reset by peer
    Logs from isc-cases-activemq:
    05:16:43.032 [ActiveMQ BrokerService[detachedBroker] Task-1] ERROR v=unknown o.a.a.broker.TransportConnector - Could not accept connection from tcp://10.128.2.1:45632 : {}
    javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    ...
    Caused by: java.io.EOFException: SSL peer shut down incorrectly


    ------------------------------
    Valentyn Gostiev
    ------------------------------


  • 2.  RE: There is no connection between isc-cases-postgres and isc-cases-activemq pods

    Posted Tue May 17, 2022 12:22 PM

    Understand this issue is aged, but were you able to resolve this issue? Was it a certificate issue, or a authentication configuration issue?

    https://www.ibm.com/docs/en/cloud-paks/cp-security/1.9?topic=providers-configuring-ldap-authentication



    ------------------------------
    JOHN HANDROP
    ------------------------------