Polarity Server 5.4.2

Prior to updating to any version of Polarity Server 5.4 please ensure that all of your integrations are running the latest version. Integrations that have not been updated may not be compatible with Polarity Server 5.4+.

When updating integrations please keep in mind that any custom types that were manually added to the integration will be lost. Prior to updating, be sure to have a copy of any custom type regular expressions so they can be re-added after the update.

Polarity 5.4+ allows adding these custom types directly through the Data Types page on the integration settings page. Once on Polarity 5.4+, future integration updates will not reset your custom types.

About Latest Version

If you have not yet updated to v5.4.x of Polarity Server please review the new features and updates available in v5.4 of the server as well as updates available in v5.4 of web.

Polarity Server 5.4.1 is a minor patch release that addresses several issues in v5.4.0. This is a recommended upgrade for all customers.

• Fix - Improve upgrade migration path from server versions prior to v5.4.0 to preserve whether data types are enabled or disabled when transitioning to new custom type implementation.

• Fix - Ensure proper typeflag on custom entity object values that are passed to Integrations.

• Fix - Fix loading of certain values for the new dataTypes setting within an Integration's config.json

Troubleshooting Upgrade to Latest 5.4 Version

Permission Issues

After upgrading to V5.4 and the server will not start you might see an error like the following :

:cacertfile either does not exist, or the application does not have permission to access it

This is due to a permission not getting set during the upgrade process. The fix is fairly straight forward as all you will need to do is run the following script to force set the permissions:

bin/polarity docker-set-permissions

Improperly Referenced `tls-ca-bundle.pem` file

If you notice the following error in your server logs then you may need to update your docker-compose.ymlfile to remove the POLARITY_TLS_CA_PATH environment variable:

Kernel pid terminated (application_controller) 
({application_start_failure,polarity,{{shutdown,{failed_to_start_child,'Elixir.PolarityWeb.Endpoint',
{#{'__exception__' => true,'__struct__' => 'Elixir.ArgumentError',message => 
<<"could not start Cowboy2 adapter, the file /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem required by SSL's :cacertfile either does not exist, 
or the application does not have permission to access it">>},

If you see the above error, open your docker-compose.ymlfile located at /app/docker-compose.ymland look for the following line within the appservice:

environment:
  - POLARITY_TLS_CA_PATH=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem

If you see this line, you should delete the environment and POLARITY_TLS_CA_PATH line and then restart your containers.

cd /app && ./down.sh && ./up.sh