Before you upgrade CentOS

The Rundoc-powered installation and upgrade script only supports:

  • Single machine installs.

  • Installations performed using the Intelligence Center (IC) install script.

If you are upgrading a distributed installation, you must perform the operation manually.

Before upgrading the Intelligence Center, we recommend that follow the instructions in this guide.


Disable rules

Disable all Intelligence Center rules:

  • Entity rules

  • Observable rules

  • Enrichment rules

  • Discovery rules

To disable rules:

  1. Go to Data configuration (images/download/attachments/82474542/robot.svg-x24.png ) > Rules.

  2. For each of the rule types (Entity, Observable, Enrichment, Discovery), select its corresponding tab to open a list of those rules.

  3. Select the checkbox to the left of the Rule name column to select all visible rules.

    If you have more items than arevisible on the screen, you must either:

    • Increase the number of visible items per page and then select them.

    • Select Next page (>) and then select the newly selected items to add them to the list of currently selected items.

  4. Select More (images/download/attachments/82474542/ellipsis-v.svg-x24.png ) > Disable from the list’s top-right corner to disable all selected rules.

To re-enable rules after finishing the upgrade:

  1. Follow the steps above.

  2. Instead of selecting More (images/download/attachments/82474542/ellipsis-v.svg-x24.png ) > Disable, select More (images/download/attachments/82474542/ellipsis-v.svg-x24.png ) > Enable.

Back up your data

Before proceeding to upgrade the platform or any of its third-party components, always back up your data.

Stop the Intelligence Center

Stop all backend services:

systemctl stop eclecticiq-platform-backend-services

Clear Celery queues

  1. Use the redis-cli command to check that Celery queues are empty:

    # Start redis-cli in interactive mode
    # Run these commands in the redis-cli shell
    llen enrichers
    llen integrations
    llen priority_enrichers
    llen priority_providers
    llen priority_utilities
    llen providers
    llen reindexing
    llen utilities
  2. If any of the queues are not empty, run the following commands to delete that queue:

    # Launch redis-cli
    $ redis-cli
    # Delete the entity ingestion queue
    $ > del "queue:ingestion:inbound"
    # Delete the graph ingestion queue
    $ > del "queue:graph:inbound"
    # Delete the search indexing queue
    $ > del "queue:search:inbound"
  3. Stop the remaining Celery workers:

    systemctl stop eclecticiq-platform-backend-worker*.service

Clean up PID files

Check that there are no leftover PID files

  1. Check for running IC processes:

    ps auxf | grep beat
  2. Run kill to stop any remaining IC processes.

  3. Manually remove any leftover PID files with the rm command.

    Usually, PID files are stored in /var/run.

Review configuration files

IC configuration files

The IC stores configuration files in /etc/eclecticiq/. Back up these files before performing an upgrade.

Release notes may instruct you to update these files for an upgrade.

Config file


Contains core platform settings such as:

  • Security keys

  • Authentication bearer token expiration time

  • URLs pointing to external components

  • Celery-managed tasks

  • LDAP or SAML configuration.


Contains OpenTAXII configuration parameters such as:

  • URL and port of the TAXII server

  • Inbound queue

  • Message broker.

Third party configuration files

After checking the platform configuration to make sure it correctly describes the upgraded environment, do the same with the configurations of third-party components and dependencies.

The IC stores IC-specific configuration files for third-party services in these locations:

  • /etc/eclecticiq-elasticsearch/

  • /etc/eclecticiq-kibana/

  • /etc/eclecticiq-neo4j/

  • /etc/eclecticiq-neo4jbatcher/

  • /etc/eclecticiq-nginx/

  • /etc/eclecticiq-postgres/

  • /etc/eclecticiq-redis/

About databases and network bindings

On a single machine installation, network interface bindings for services are set to by default, except for PostgreSQL which has a different configuration.

Instructions may have asked you to change this to a more permissive binding in multi-machine installations, or you may be using an older installation where defaults were set to

The table below shows a list of configuration files where network interface bindings are set for each service.

You may want to change these bindings to suit your environment.

Service name

File path(s)





For more information, see Elasticsearch’s documentation.



dbms.connectors.default_listen_address is left unset, and defaults to

For more information, see Configure connectors and dbms.connectors.default_listen_address.


local all postgres trust
host all all samenet md5
host all all password

For more information, see The pg_hba.conf File.



For more information, see Redis security and redis.conf.