IBM QRadar

IBM QRadar

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

  • 1.  Unable to access QRadar UBA

    Posted Wed February 16, 2022 08:08 AM
    Hello experts,

    I can''t access UBA app, it returns the error message "message":"Internal Server Error: [http://<IP_address>>next-dashboard","status":
    500|http://%3c...%3enext-dashboard","status":500".

    I tried to apply a workaround using the below link, but I am unable to run the command "supervisorctl stop psql", I received the message command not found.

    https://www.ibm.com/support/pages/qradar-not-able-upgrade-latest-version-uba-app-%E2%80%9Cinternal-server-error-httpuserimportindex%E2%80%9D

    Kindly assist.

    ------------------------------
    benlinux
    ------------------------------


  • 2.  RE: Unable to access QRadar UBA

    Posted Wed February 16, 2022 08:36 AM
    One thing to check for is any non integer value for 'sense value'
    observed through Use Case Manager.


    Original Message


  • 3.  RE: Unable to access QRadar UBA

    Posted Wed February 16, 2022 08:42 AM
    Hello,

    Thank you for the feedback. How can i check for non integer value for sense value using the UCM.

    Again, is this the reason for the error message while accessing the UBA?

    Regards,

    ------------------------------
    benlinux
    ------------------------------

    Original Message


  • 4.  RE: Unable to access QRadar UBA

    Posted Wed February 16, 2022 09:00 AM
    Add 'sense value' field to the output using the gear icon in Use Case
    Manager app

    or run in PSQL:

    select rdk.key1, rde.data from reference_data rd, reference_data_key
    rdk, reference_data_element rde where rd.id = rdk.rd_id and rdk.id =
    rde.rdk_id and rd.name = 'UBA : Rule Data' and rdk.key2 =
    'defaultRisk';


    If you get any non integer output in the 'defaultRisk' field or in use
    case manager app 'sense value' , repairing that condition can fix the
    issue.. The above is a possible issue and not guaranteed to be the
    root cause based on the info i have.


    Original Message


Related Content