Threat Intelligence Exchange Server upgrade fails when a custom index is added to the database

Technical Articles ID: KB95263
Last Modified: 2023-03-27 09:30:02 Etc/GMT

Environment

Threat Intelligence Exchange (TIE) Server 3.0.x and earlier

Problem

An upgrade to TIE Server 3.0.3 fails, and you see the errors below in Tieserver 3.0.3.log (/var/log):

Attempting to do the transaction now
Error upgrading DB schema. Aborting overall upgrade
Error: %pre(tieserver-3.0.3-.mlos2.x86_64) scriptlet failed, exit status 255
error: install: %pre scriptlet failed (2), skipping tieserver-3.0.3-.mlos2
Done

You see the errors below in Postgresql.log (/var/McAfee/tieserver/logs):

WARNING {2022-01-18 11:54:19.472} [7-1] ERROR: relation "idx_file_sha256" already exists
WARNING {2022-01-18 11:54:19.472} [7-2] STATEMENT: create index IDX_FILE_SHA256 on file (sha256)

Cause

Custom index SHA256 is added to the TIE database. Adding an SHA256 index improves the performance of the bulk reputation import using the wizard within the TIE Reputations, File-override option.

In scenarios where you've added SHA256 to the file table, an upgrade conflict is caused while readding the parameters.

Solution

Technical Support is investigating this issue. As a temporary measure, implement the following workaround.

Workaround

Delete the index by following the steps below:

Type each of the commands below in the command window, and press Enter:

# service tieserver stop

# service tieserver pg_start

# /opt/McAfee/tieserver/postgresql/bin/psql -U mfetie -d tie

tie# DROP INDEX IDX_FILE_SHA256;

tie# \q

# service tieserver start
Rerun the upgrade task.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Threat Intelligence Exchange Server upgrade fails when a custom index is added to the database

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Threat Intelligence Exchange Server upgrade fails when a custom index is added to the database

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title