Splunk® User Behavior Analytics

Release Notes

This documentation does not apply to the most recent version of Splunk® User Behavior Analytics. For documentation on the most recent version, go to the latest release.

Known Issues in Splunk UBA

This version of Splunk UBA has the following known issues and workarounds.


Date filed Issue number Description
2022-04-14 UBA-15607, UBA-14237 Unable to create Anomaly Table filter or AAR specifying filter for Specific Devices when specifying over 20 CIDR/s
2021-05-04 UBA-14516 Health Monitor - An error occurred while retrieving data - Error from /uba/monitor Invalid Json response: Error in getting the response Parameters: {"queryStatus":true,"queryDataQualityStatus":true}

Workaround:
  1. Stop all Splunk UBA services on node 1: 
    /opt/caspida/bin/Caspida stop-all
  2. On each Splunk UBA node, edit the java.security file in - 
    /usr/lib/jvm/java-*/jre/lib/security/java.security
    and remove TLSv1 and TLSv1.1 from the following property 
     jdk.tls.disabledAlgorithms
  3. The folder in /usr/lib/jvm will be different on different environments. For example- The absolute path for java.security file in Ubuntu is, 
    /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/security/java.security
  4. Start all Splunk UBA services on node 1: 
    /opt/caspida/bin/Caspida start-all
  5. Verify there are no more errors in UI.

2020-06-29 UBA-14199, UBA-12111 Impala jdbc connections leak

Workaround:
  1. Create a file containing the following script on node 1 in your Splunk UBA deployment (node 2 on a 20-node Splunk UBA deployment). For example, copy and paste the script to a new file in /etc/caspida/local/conf/impala_status_check.sh: 
    #!/bin/bash
log_file=$1
if test -f "$log_file"; then
   tail -n 100 $log_file > /tmp/tmp_log_file.log
   mv /tmp/tmp_log_file.log $log_file
fi
connection_count=$(netstat -an | grep :21050 | grep ESTABLISHED | wc -l)
now=$(date)
if [ "$connection_count" -gt 500 ]; then
   echo "[$now] $connection_count impala connection(s), restarting impala"
   sudo service impala-server restart
   if [ $? -eq 0 ]; then
      echo "restart succeeded"
    else
      echo "restart failed. return code: $?"
   fi
else
   echo "[$now] $connection_count impala connection(s), status is good"
fi
  2. Make the script executable: 
    chmod +x /etc/caspida/local/conf/impala_status_check.sh
  3. Add the following line to cron using crontab -e: 
    0 8 * * * /etc/caspida/local/conf/impala_status_check.sh >> /var/log/impala/impala_status.log 2>&1

2020-06-27 UBA-14198 Anomaly actions rules with wildcards can cause syntax error and failure

Workaround:
Contact support to fix your sql query
2020-06-25 UBA-14197 SplunkDirect Cloud model errors with unsupported object_type fields

Workaround:
This issue is observed while ingesting SplunkDirect Cloud category data. Only the following values for the "object_type" field are supported: 
Collaboration, Cookie, File, FileSystem, Folder, Registry, SecretObject, ServiceObject, SamDomain, Computer, Share, SharePoint, Token, USB, User, Unknown

If there are any other values in your environment for "object_type" field, modify the SPL to evaluate unsupported values to "Unknown". For example: 

| eval object_type=case(object_type == "File", "File", object_type == "Folder", "Folder", object_type == "Web", "Unknown")
2020-06-03 UBA-14116, UBA-14212 HA/DR sync fails after multiple days with Postgres error
2020-06-02 UBA-14097 First attempt to create new AAR rules fails after standby failover
2020-05-11 UBA-13950 HA/DR after failover system does not restart until setup-containerization is run on standby system

Workaround:
After failover, run 
/opt/caspida/bin/Caspida stop
/opt/caspida/bin/Caspida setup-containerization
/opt/caspida/bin/Caspida start
2020-05-11 UBA-13948 HA/DR After failover, the scheduled datasources (hrdata and assets) are not running on schedule

Workaround:
On node1 of promoted system, run 
curl -X PUT -Ssk -v -H "Authorization: Bearer $(grep '^\s*jobmanager.restServer.auth.user.token=' /opt/caspida/conf/uba-default.properties | cut -d'=' -f2)" https://localhost:9002/datasources/moveDS?name=<Name of Datasouce>

Where <Name of Datasouce> is the data source name displayed on UI

2020-05-11 UBA-13942 HA/DR Standby failover failed when Postgres on Primary is down

Workaround:
On node hosting Postgres, run 
psql -d caspidadb -c 'ALTER SUBSCRIPTION subscription_caspida DISABLE'
psql -d caspidadb -c 'ALTER SUBSCRIPTION subscription_caspida SET (slot_name = NONE)'
psql -d caspidadb -c 'DROP SUBSCRIPTION IF EXISTS subscription_caspida'

On master node, run failover again 

touch /opt/caspida/conf/replication/properties/standby
/opt/caspida/bin/replication/failover
2020-05-06 UBA-13921 UBA Self-signed certificates no longer pass current browser checks
2020-05-01 UBA-13896 HA/DR CaspidaCleanup breaks for system in standby mode

Workaround:
Run the following commands on the Splunk UBA node hosting Postgres before cleanup: 
psql -d caspidadb -c 'BEGIN; SET transaction read write; ALTER DATABASE caspidadb SET default_transaction_read_only = off; COMMIT
psql -d caspidadb -c 'DROP PUBLICATION IF EXISTS publication_caspida'
psql -d caspidadb -c 'DROP SUBSCRIPTION IF EXISTS subscription_caspida'
2020-04-27 UBA-13856 Upgrade failed in Redhat/CentOS/OrclLinux without internet access or local proxy which does not include JVM updates.

Workaround:
Upgrading to Splunk UBA 5.0.3 on Linux systems requires downloading an installer package with the release number 5.0.3.1. See How to install or upgrade to this release of Splunk UBA at https://docs.splunk.com/Documentation/UBA/5.0.3/Install/InstallUpgradePath for instructions.
2020-04-22 UBA-13845 Backup/Restore and Replication logs not included in "Download Diagnostics"
2020-04-19 UBA-13824 HA/DR HDFS data transfer fails with ssh timeout

Workaround:
Edit /opt/caspida/conf/replication/ssh_config file on master node on both primary and standby clusters so it looks like this: 
Host *
    ControlMaster no
    ControlPath /var/vcap/sys/tmp/caspida/%r@%h-%p
    ControlPersist 3600
    StrictHostKeyChecking no
    ServerAliveInterval 30
    ServerAliveCountMax 10

Sync on both primary and standby cluster: 

/opt/caspida/bin/Caspida sync-cluster /opt/caspida/conf/replication

Then rerun setup with reset option on primary and standby systems, and kick off the first sync cycle.

2020-04-07 UBA-13804 Kubernetes certificates expire after one year

Workaround:
Run the following commands on the Splunk UBA master node: 
/opt/caspida/bin/Caspida remove-containerization
/opt/caspida/bin/Caspida setup-containerization
/opt/caspida/bin/Caspida stop-all
/opt/caspida/bin/Caspida start-all
2020-03-22 UBA-13731 User hrAccountType is not being updated in "Users Table"
2020-03-13 UBA-13707 Offline executor not running - shutting down and restarting itself. Added new configurable; rule.engine.process.timeout.min
2020-03-12 UBA-13704 Microbatch interval property splunk.live.micro.batching.interval.second it's not being honored
2019-11-17 UBA-13386 Fix homepage EPS
2019-08-06 UBA-12910 Splunk Direct - Cloud Storage does not expose src_ip field

Workaround:
When ingesting Office 365 Sharepoint/OneDrive logs through Splunk Direct - Cloud Storage, add an additional field mapping for src_ip in the final SPL to be mapped from ClientIP (| eval src_ip=ClientIP). Make sure to add src_ip in the final list of fields selected using the fields command. For example: 
| fields app,change_type,dest_user,file_hash,file_size,object,object_path,object_type,parent_category,parent_hash,sourcetype,src_user,tag,src_ip
Last modified on 11 July, 2023
Welcome to Splunk UBA 5.0.2   Fixed Issues in Splunk UBA

This documentation applies to the following versions of Splunk® User Behavior Analytics: 5.0.2

Acrobat logo Download manual
Acrobat logo Download this page

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters